Add USB hooks into NanoBone DTS file
PATCH 1/1 Add USB hooks into NanoBone DTS file
Add USB hooks into NanoBone DTS file
Signed-off-by Mark Jackson <[email protected]>
--- arch/arm/boot/dts/am335x-nano.dts | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
arch/arm/boot/dts/am335x-nano.dts +17 -0
@@ -375,6 +375,23 @@ wp-gpios = <&gpio3 18 0>; }; +&usb { + status = "okay"; +}; + +&usb_ctrl_mod { + status = "okay"; +}; + +&usb0_phy { + status = "okay"; +}; + +&usb0 { + status = "okay"; + dr_mode = "host"; +}; + #include "tps65217.dtsi" &tps {
Signature · 1 line
1.9.1
Quoted 1 line · Mark Jackson
Add USB hooks into NanoBone DTS file
Hmm looking at things, we really should not set status = "disabled" for any of the internal devices. Setting "disabled" makes the kernel completely ignore the device and we're better off from PM point of view to probe and idle the device. The devices are there for sure, and typically just the pins are not configured for them.
How about just remove the status = "disabled" from am33xx.dtsi instead?
Regards,
Tony
Quoted 36 lines
Signed-off-by Mark Jackson <[email protected]>--- arch/arm/boot/dts/am335x-nano.dts | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)arch/arm/boot/dts/am335x-nano.dts +17
-0@@ -375,6 +375,23 @@ wp-gpios = <&gpio3 18 0>; }; +&usb { + status = "okay"; +}; + +&usb_ctrl_mod { + status = "okay"; +}; + +&usb0_phy { + status = "okay"; +}; + +&usb0 { + status = "okay"; + dr_mode = "host"; +}; + #include "tps65217.dtsi" &tps {Signature · 1 line
1.9.1