I’m trying to implement a custom driver feature that needs access in the devicetree. We have the driver reporting the Parent node /xhci@3530000 but I’m not sure how to call in the devicetree the specific node for usb bus/device.
Below is the device
travis@ubuntu:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/3p, 5000M
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 5: Dev 4, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ **Port 3: Dev 5, If 0, Class=Vendor Specific Class, Driver=lrdmwl_usb, 480M**
travis@ubuntu:~$ lsusb
Bus 002 Device 002: ID 0424:5744 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
**Bus 001 Device 005: ID 1286:204e Marvell Semiconductor, Inc.**
Bus 001 Device 004: ID 0424:2740 Standard Microsystems Corp.
Bus 001 Device 002: ID 0424:2744 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
You should not add property to our driver. You should add it to the device driver’s node. This is not what I can answer.
This depends on your device driver vendor to answer.
And It is unlikely to configure “bus1-port3-device5”. Just take a most common scenario as example, what if another device occupied this device and your device becomes “bus-1-port-3-device7”? You would need to configure device tree again just because the usb enumeration order is different? Such case is not correct.
I am not using Intel or Realtek but Marvell chipset by NXP.
For us this is pretty standard implementation with a reset gpio tied to wifi module. With PCIe the reset is in the PCI standard, for SDIO we use mmc-pwrseq binding in devicetree, and for USB we have used this binding without issue on atmel processor. But seems for Nvidia it does not work. I’m asking for help on this binding, not recommendation for different wifi chipset.