> On R-Car Gen2, you do get an external abort when accessing hardware > registers while the module's clock is turned off. Has anyone tested > usbhs on R-Car Gen2 recently? > Yes I tested this with the patch applied, https://gist.github.com/prabhakarlad/3d1bbb6f745d8d867c8e6e009ab93f8d 1] For R-Car Gen3 looking at the r8a77951.dtsi we have the below: hsusb: usb@e6590000 { compatible = "renesas,usbhs-r8a7795", ... clocks = <&cpg CPG_MOD 703>, <&cpg CPG_MOD 704>; .... }; The same clocks are used for ehci0/ohci0/phy0 in r8a77951.dtsi, probably by the time we reach probing the usbhs driver these clocks may have been already enabled hence register reads were sensible. 2] For the R-Car Gen2, looking at the RZ/G1H USBHS node we have the below: hsusb: usb@e6590000 { .... clocks = <&cpg CPG_MOD 704>; .... }; Same clock is for USBPHY, even in this case the PHY driver is probed first due to which the clock is ON and then we probe usbhs driver.. Cheers, Prabhakar