From: Felipe Balbi <balbi@ti.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
<valentine.barshak@cogentembedded.com>
Subject: Re: [PATCH] usb: phy: Quiet unable to find transceiver message
Date: Mon, 27 Jan 2014 09:30:38 -0600 [thread overview]
Message-ID: <20140127153038.GA13268@saruman.home> (raw)
In-Reply-To: <CA+5PVA7iFPHXz1Mn+Ri07Ajr1FYpm1ubVoq-twrFC1Rbu=p_HA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
On Sat, Jan 25, 2014 at 03:24:55PM -0500, Josh Boyer wrote:
> On Sat, Jan 25, 2014 at 10:37 AM, Alan Stern <stern@rowland.harvard.edu> wrote:
> > On Sat, 25 Jan 2014, Josh Boyer wrote:
> >
> >> commit 1ae5799ef6317 ("usb: hcd: Initialize USB phy if needed") allows
> >> the USB layer to initialize external PHYs if needed. However, a PHY is
> >> not needed in all cases. The usb_get_phy_device function will print
> >> an error message, "unable to find transceiver" but everything still
> >> functions normally.
> >>
> >> Drop the severity of this message to pr_debug.
> >>
> >> Signed-off-by: Josh Boyer <jwboyer@fedoraproject.org>
> >> ---
> >> drivers/usb/phy/phy.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/drivers/usb/phy/phy.c b/drivers/usb/phy/phy.c
> >> index e6f61e4..c7fe880 100644
> >> --- a/drivers/usb/phy/phy.c
> >> +++ b/drivers/usb/phy/phy.c
> >> @@ -228,7 +228,7 @@ struct usb_phy *usb_get_phy_dev(struct device *dev, u8 index)
> >>
> >> phy = __usb_find_phy_dev(dev, &phy_bind_list, index);
> >> if (IS_ERR(phy) || !try_module_get(phy->dev->driver->owner)) {
> >> - pr_err("unable to find transceiver\n");
> >> + pr_debug("unable to find transceiver\n");
> >> goto err0;
> >> }
> >
> > Wouldn't it make more sense to change this to dev_debug? As it stands,
> > the user has no idea which device is lacking a transceiver.
>
> Quite possibly, yes. I'm not overly familiar with the subsystem and
> was just writing up what Felipe suggested.
>
> > (The same is probably true for other log messages in this source file.)
>
> I don't disagree, but I'd rather someone with more experience in the
> USB subsystem do that kind of broader audit/change. I'd be happy to
> test.
yeah, I just sent a patch where I forgot to switch over to dev_dbg(), if
you can do that for both messages and remove the out of memory message,
I'd be glad to take your patch instead of mine.
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-01-27 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 15:05 [PATCH] usb: phy: Quiet unable to find transceiver message Josh Boyer
2014-01-25 15:37 ` Alan Stern
2014-01-25 20:24 ` Josh Boyer
2014-01-27 15:30 ` Felipe Balbi [this message]
2014-02-03 15:29 ` Paul Bolle
2014-02-03 16:04 ` Alan Stern
2014-02-03 18:37 ` Paul Bolle
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=20140127153038.GA13268@saruman.home \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=valentine.barshak@cogentembedded.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