Your microphone is a “device”. Your device needs to connect to a “host”. The port which is used for flash is only a device, and only works on another computer’s host. You can ignore that port. You are interested in all of the other ports for the microphone since all of those other ports are hosts which understand your microphone device. There is no ability to use that flash port as a host, it cannot happen.
USB is itself just a data pipe, along with some plug-n-play ability. When you plug that device into your host port, all of those ports (except for the device port used in flashing) will work for the data pipe. What happens when you plug in a USB device to a host is that the host will query the device, and the device will provide details regarding what the device is. USB will then announce the presence of the device description, and if there is a driver which can handle that device, then the driver will be paired to that device. The driver is not part of USB and is a separate question as that driver must be present for it to bind to the device.
It is true that there is a large selection of “standard” devices. There are drivers which come with any USB host for the standard devices. Despite shipping with the USB, and despite those “standard” drivers seemingly being part of USB, this is just a convenience, and technically even those drivers are not part of the USB. If your microphone uses one of those standard drivers, then if your Jetson has the software to use this microphone, then the microphone will “just work”. Consider though that there sound setup options, there are sound programs to integrate into a GUI desktop, and there is in general a lot of audio software (e.g., mixers) needed to actually get a microphone output to where it needs to go. If your USB has paired to a driver, then your audio software should be able to see and use that microphone. If your audio software is set up incorrectly, then with the driver in place it means fixing the audio setup would fix the sound from the microphone. There is no way to know what that chain of audio is that you want this microphone’s driver to feed, but that software can work when set up and a driver is paired to the microphone.
One thing anyone with a USB device should do if they have issues with it is to monitor “dmesg --follow”, and then insert the device. The first part of the log which is created due to the insert will tell you what USB saw as a result of the hot plug event. The next part of the log, if it exists, will tell you if a driver was paired to the device. Possibly some user space software will then show something as a result of seeing that device, but it might be in a different log (e.g., the X11 GUI software will have a log of an audio device being connected to the GUI…that’s the user space software).
One can say that the USB connectors, except for the one used in flashing, will work with your device. If that device requires a custom driver, then we can guarantee that the device will fail unless the custom driver is added. If the driver is one of the “standard” devices, then we can say that the driver is already present, and that both USB and the driver will work and make the microphone available. Whether or not the rest of the software which deals with the microphone will work we cannot say. You’d have to try it or talk to the people who support that particular software; at this point it is no longer a “Jetson” (nor “driver”) question. Actually, all of that USB setup, with one exception, is completely unrelated to Jetsons and is just a Linux question; that one exception is the fact that Jetsons have a USB port for flashing, and the flash port cannot behave as a host; all other USB ports will act just like any other Linux PC.