Can't parse '' property of node

Embedded Linux Discussions
1

Here is result of command dmesg | grep -i “usb”.

[ 0.219684] usbcore: registered new interface driver usbfs
[ 0.219804] usbcore: registered new interface driver hub
[ 0.219911] usbcore: registered new device driver usb
[ 1.514651] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 1.514894] usbcore: registered new interface driver usb-storage
[ 1.787125] am335x-phy-driver 47401300.usb-phy: GPIO lookup for consumer reset
[ 1.787198] am335x-phy-driver 47401300.usb-phy: using device tree for GPIO lookup
[ 1.787250] of_get_named_gpiod_flags: can’t parse ‘reset-gpios’ property of node ‘/ocp/target-module@47400000/usb-phy@1300[0]’
[ 1.787324] of_get_named_gpiod_flags: can’t parse ‘reset-gpio’ property of node ‘/ocp/target-module@47400000/usb-phy@1300[0]’
[ 1.787382] am335x-phy-driver 47401300.usb-phy: using lookup tables for GPIO lookup
[ 1.787410] am335x-phy-driver 47401300.usb-phy: No GPIO consumer reset found
[ 1.787438] am335x-phy-driver 47401300.usb-phy: GPIO lookup for consumer vbus-detect
[ 1.787462] am335x-phy-driver 47401300.usb-phy: using device tree for GPIO lookup
[ 1.787498] of_get_named_gpiod_flags: can’t parse ‘vbus-detect-gpios’ property of node ‘/ocp/target-module@47400000/usb-phy@1300[0]’
[ 1.787557] of_get_named_gpiod_flags: can’t parse ‘vbus-detect-gpio’ property of node ‘/ocp/target-module@47400000/usb-phy@1300[0]’
[ 1.787609] am335x-phy-driver 47401300.usb-phy: using lookup tables for GPIO lookup
[ 1.787634] am335x-phy-driver 47401300.usb-phy: No GPIO consumer vbus-detect found
[ 1.787761] am335x-phy-driver 47401300.usb-phy: supply vcc not found, using dummy regulator

The kernel 5.11.10 am33xx.dtsi file has a usb0_phy: usb-phy@1300 {} section but there is no reset-gpios, reset-gpio, vbus-detect-gpios or vbus-detect-gpio entries.

I think the errors are coming from the NOP_USB_XCEIV kernel configuration setting but I don’t know how to fix.
How do I fix the ‘can’t parse ‘’ property of node’ errors?

Thank you,

2

Correct, phy-am335x.c shouldn’t need any gpio access:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/phy/phy-am335x.c#n38

How did you configure the usb?

CONFIG_USB_PHY=y
CONFIG_NOP_USB_XCEIV=y
CONFIG_AM335X_CONTROL_USB=y
CONFIG_AM335X_PHY_USB=y
CONFIG_USB_GPIO_VBUS=y

is what i recommend in that section…

Otherwise, post your config.

Regards,

3

Robert,
I have the # USB Physical Layer drivers section configured same as your suggestion. I have attached my custom.config-5.11.10 file.
custom.config-5.11.10 (174.9 KB)

Also here is my project’s custom DT files, zcpu-main.dts and zcpu-common.dtsi DT copied from linux5.11.10/arch/arm/boot/dts folder.
zcpu-common.dtsi (17.6 KB) zcpu-main.dts (978 Bytes)
My custom DT includes the am33xx.dtsi file. I have made no changes to the am33xx.dtsi file.

Can you attach a copy of your kernel .config for my reference?

Thank you,

4

Robert,
I found this answer in a 7-year old post on the e2e forum.

This parsing failure message is harmless debug message and can be ignored. The MUSB PHY on AM335x does not use PGIO for reset, but the PHY driver framework requires one, so the dts node parsing failed in the PHY driver, but it does not affect any USB functionality on AM335x.

and this from another post on e2e,

To disable these messages unselect CONFIG_DEBUG_GPIO from the kernel configuration.

I unselected the setting and no more ‘can’t parse’ messages during kernel boot. Now I can concentrate on what is really broken.

Did you have the setting turned off in your kernel .config?

Thank you,

5

Glad you found it!

Yeah, i have that disabled:

# CONFIG_DEBUG_GPIO is not set

Regards,