From: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
To: Klaus Kudielka <klaus.kudielka@gmail.com>,
Mathias Nyman <mathias.nyman@intel.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: RE: [PATCH v1] usb: xhci: plat: Add USB 3.0 phy support
Date: Wed, 10 May 2023 06:25:22 +0000 [thread overview]
Message-ID: <2ad6cffea4034cbb83d8d7e4e36f57fc@realtek.com> (raw)
In-Reply-To: <f8aa160b-83dc-59cc-03dc-d9e8edbd497f@gmail.com>
> >>
> >> I'm booting 6.4-rc1 on a Turris Omnia
> >> (arm/boot/dts/armada-385-turris-omnia.dts)
> >> and get those error messages:
> >> [ 0.231609] xhci-hcd f10f0000.usb3: xhci_plat_probe get usb3phy fail
> >> (ret=-6)
> >> [ 0.239716] xhci-hcd f10f8000.usb3: xhci_plat_probe get usb3phy fail
> >> (ret=-6)
> >>
> >> It looks like a cosmetic issue with error codes, but maybe it can be fixed?
> >>
> > 1. I checked arm/boot/dts/armada-385-turris-omnia.dts.
> > The xhci node doesn't seem to have usb-phy.
> > In this case it should get error code -ENODEV (-19).
> > I'm not sure why the error code is -ENXIO (-6).
> > Can you provide more details?
>
> I have CONFIG_USB_PHY disabled. In that case,
> devm_usb_get_phy_by_phandle is declared static inline and returns -ENXIO.
> See include/linux/usb/phy.h.
>
> > 2. This error message will be printed only when getting the usb3 phy fails.
> > And usb_phy set to NULL, It does not affect the original behavior.
> > Maybe I'm missing checking -ENXIO or some other error code.
> > I can delete this log according to usb2 phy situation.
>
> Checking for -ENXIO in addition to -ENODEV would cover
> the !CONFIG_USB_PHY case, I guess. Whether there are other "false alarm"
> cases, I don't know.
>
Okay, I will remove this log message.
I think using the log in drivers/usb/phy/phy.c can easy to debug error case.
Thanks,
Stanley
prev parent reply other threads:[~2023-05-10 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 6:07 [PATCH v1] usb: xhci: plat: Add USB 3.0 phy support Stanley Chang
2023-05-09 17:33 ` Klaus Kudielka
2023-05-10 3:16 ` Stanley Chang[昌育德]
2023-05-10 6:11 ` Klaus Kudielka
2023-05-10 6:25 ` Stanley Chang[昌育德] [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ad6cffea4034cbb83d8d7e4e36f57fc@realtek.com \
--to=stanley_chang@realtek.com \
--cc=klaus.kudielka@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox