All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@linuxfoundation.org, balbi@ti.com, holler@ahsoftware.de,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-kernel@vger.kernel.org, "ABRAHAM,
	KISHON VIJAY" <kishon@ti.com>
Subject: Re: [PATCH 2/2] USB: ehci-omap: Improve PHY error handling
Date: Wed, 17 Apr 2013 11:12:43 +0300	[thread overview]
Message-ID: <516E597B.9010100@ti.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1304161130590.1391-100000@iolanthe.rowland.org>

On 04/16/2013 06:32 PM, Alan Stern wrote:
> On Mon, 15 Apr 2013, Roger Quadros wrote:
> 
>> As the USB PHY layer never returns NULL we don't need
>> to check for that condition.
>>
>> If we fail to get the PHY device it could be due
>> to missing USB PHY drivers. Give this hint to the user
>> in the error message.
>>
>> CC: Alan Stern <stern@rowland.harvard.edu>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> ---
>>  drivers/usb/host/ehci-omap.c |    6 +++---
>>  1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/usb/host/ehci-omap.c b/drivers/usb/host/ehci-omap.c
>> index 5de3e43..2e34ddd 100644
>> --- a/drivers/usb/host/ehci-omap.c
>> +++ b/drivers/usb/host/ehci-omap.c
>> @@ -175,13 +175,13 @@ static int ehci_hcd_omap_probe(struct platform_device *pdev)
>>  			phy = devm_usb_get_phy_by_phandle(dev, "phys", i);
>>  		else
>>  			phy = devm_usb_get_phy_dev(dev, i);
>> -		if (IS_ERR(phy) || !phy) {
>> +		if (IS_ERR(phy)) {
>>  			/* Don't bail out if PHY is not absolutely necessary */
>>  			if (pdata->port_mode[i] != OMAP_EHCI_PORT_MODE_PHY)
>>  				continue;
>>  
>> -			ret = IS_ERR(phy) ? PTR_ERR(phy) : -ENODEV;
>> -			dev_err(dev, "Can't get PHY device for port %d: %d\n",
>> +			ret = PTR_ERR(phy);
>> +			dev_err(dev, "Can't get PHY device for port %d: %d. Is USB_PHY driver enabled?\n",
>>  					i, ret);
>>  			goto err_phy;
>>  		}
> 
> Getting rid of the !phy test is good.  But I'm doubtful about the 
> change to the error message.  Are you going to make a similar change to 
> every platform driver?  There doesn't seem to be any reason to do this 
> for ehci-omap but not the others.

I'm not very sure about that. If using the PHY API while USB_PHY is disabled
is to be treated as a universal failure, then the print might as well come from
the dummy stub for xx_usb_get_phy_xx().

For this patch, I'll just undo the print message change and resend. That could be
done in a separate patch instead.

cheers,
-roger

WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: <gregkh@linuxfoundation.org>, <balbi@ti.com>,
	<holler@ahsoftware.de>, <linux-usb@vger.kernel.org>,
	<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"ABRAHAM, KISHON VIJAY" <kishon@ti.com>
Subject: Re: [PATCH 2/2] USB: ehci-omap: Improve PHY error handling
Date: Wed, 17 Apr 2013 11:12:43 +0300	[thread overview]
Message-ID: <516E597B.9010100@ti.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1304161130590.1391-100000@iolanthe.rowland.org>

On 04/16/2013 06:32 PM, Alan Stern wrote:
> On Mon, 15 Apr 2013, Roger Quadros wrote:
> 
>> As the USB PHY layer never returns NULL we don't need
>> to check for that condition.
>>
>> If we fail to get the PHY device it could be due
>> to missing USB PHY drivers. Give this hint to the user
>> in the error message.
>>
>> CC: Alan Stern <stern@rowland.harvard.edu>
>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> ---
>>  drivers/usb/host/ehci-omap.c |    6 +++---
>>  1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/usb/host/ehci-omap.c b/drivers/usb/host/ehci-omap.c
>> index 5de3e43..2e34ddd 100644
>> --- a/drivers/usb/host/ehci-omap.c
>> +++ b/drivers/usb/host/ehci-omap.c
>> @@ -175,13 +175,13 @@ static int ehci_hcd_omap_probe(struct platform_device *pdev)
>>  			phy = devm_usb_get_phy_by_phandle(dev, "phys", i);
>>  		else
>>  			phy = devm_usb_get_phy_dev(dev, i);
>> -		if (IS_ERR(phy) || !phy) {
>> +		if (IS_ERR(phy)) {
>>  			/* Don't bail out if PHY is not absolutely necessary */
>>  			if (pdata->port_mode[i] != OMAP_EHCI_PORT_MODE_PHY)
>>  				continue;
>>  
>> -			ret = IS_ERR(phy) ? PTR_ERR(phy) : -ENODEV;
>> -			dev_err(dev, "Can't get PHY device for port %d: %d\n",
>> +			ret = PTR_ERR(phy);
>> +			dev_err(dev, "Can't get PHY device for port %d: %d. Is USB_PHY driver enabled?\n",
>>  					i, ret);
>>  			goto err_phy;
>>  		}
> 
> Getting rid of the !phy test is good.  But I'm doubtful about the 
> change to the error message.  Are you going to make a similar change to 
> every platform driver?  There doesn't seem to be any reason to do this 
> for ehci-omap but not the others.

I'm not very sure about that. If using the PHY API while USB_PHY is disabled
is to be treated as a universal failure, then the print might as well come from
the dummy stub for xx_usb_get_phy_xx().

For this patch, I'll just undo the print message change and resend. That could be
done in a separate patch instead.

cheers,
-roger

  reply	other threads:[~2013-04-17  8:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 11:50 [PATCH 1/2] USB: ehci-omap: Don't select any PHY driver Roger Quadros
2013-04-15 11:50 ` Roger Quadros
2013-04-15 11:50 ` [PATCH 2/2] USB: ehci-omap: Improve PHY error handling Roger Quadros
2013-04-15 11:50   ` Roger Quadros
2013-04-16 15:32   ` Alan Stern
2013-04-16 15:32     ` Alan Stern
2013-04-17  8:12     ` Roger Quadros [this message]
2013-04-17  8:12       ` Roger Quadros
     [not found]   ` <1366026636-29198-2-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2013-04-17  8:24     ` [PATCH v2 " Roger Quadros
2013-04-17  8:24       ` Roger Quadros
2013-04-17 14:15       ` Alan Stern
2013-04-17 14:15         ` Alan Stern
2013-04-16 15:30 ` [PATCH 1/2] USB: ehci-omap: Don't select any PHY driver Alan Stern
2013-04-16 15:30   ` Alan Stern

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=516E597B.9010100@ti.com \
    --to=rogerq@ti.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=holler@ahsoftware.de \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.