Some of this is probably very specific to that camera, and I know nothing about it. I did see it has downloads which in part includes firmware. If the firmware and any kind of driver are not both present, then the camera won’t function. As to whether a camera without firmware will be detected and marked as failed versus not detected at all I don’t know.
To be sure you need the arm64 package, plus a firmware package is likely needed. Note that in their Downloads area there is an area under this for Firmware. Firmware is not specific to arm64 the way the driver is, but must be the right version to match the driver…probably the most recent firmware plus most recent arm64 in combination are what you want.
Some drivers already exist as a standardized item, e.g., USB hard drives can use built in mass storage device drivers. Some cameras may also use custom or generic drivers. User space software which actually makes end user use of the device typically needs to be custom if the driver is custom. Many devices are actually hybrids with more than one device over a single cable, e.g., it may be a camera uses a custom interface for functions like focus and zoom, while the video or camera output might be using a standard class available everywhere…in which case you’d see the camera, but not be able to control it unless you had the custom software. I mention this because your task might be to get different parts working, or it might be a single setup to get it all working. Firmware is probably required for all parts, other software is perhaps required for individual parts.
One tool you have is to monitor dmesg as you run software which might go out over the ethernet (I think this camera is ethernet…if not, perhaps it is USB…then mention that) and see what the kernel says (try “dmesg --follow” prior to attempting something which would talk to the camera).
EDIT: I see you are looking at the old usb_port_owner_info…so this must be USB. You don’t need to look at that on the most recent R28.1 L4T release, it is already USB3.
Do look at what shows up in “lsusb”. The camera will have an ID, e.g., it’ll look something like “0955:7c18”. Then limit the lsusb to just this device and show verbose…I’ll use 0955:7c18 as an example, adjust to your camera:
sudo lsusb -d 0955:7c18 -vvv
Use the previously mentioned “dmesg --follow” and see what changes as you plug in the camera.