From: Roger Quadros <rogerq@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, Kishon Vijay Abraham I <kishon@ti.com>
Cc: tj@kernel.org, sergei.shtylyov@cogentembedded.com,
b.zolnierkie@samsung.com, hdegoede@redhat.com,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Balaji T K <balajitk@ti.com>
Subject: Re: [PATCH v3 2/3] ata: ahci_platform: Manage SATA PHY
Date: Wed, 8 Jan 2014 17:03:08 +0530 [thread overview]
Message-ID: <52CD3774.3060701@ti.com> (raw)
In-Reply-To: <52CD364F.4060104@ti.com>
On 01/08/2014 04:58 PM, Roger Quadros wrote:
> On 01/08/2014 03:35 PM, Arnd Bergmann wrote:
>> On Wednesday 08 January 2014 15:29:18 Kishon Vijay Abraham I wrote:
>>>> + hpriv->phy = devm_phy_get(dev, "sata-phy");
>>>> + if (IS_ERR(hpriv->phy)) {
>>>> + dev_dbg(dev, "can't get sata-phy\n");
>>>> + /* return only if -EPROBE_DEFER */
>>>> + if (PTR_ERR(hpriv->phy) == -EPROBE_DEFER) {
>>>> + rc = -EPROBE_DEFER;
>>>> + goto disable_unprepare_clk;
>>>> + }
>>>> + }
>>
>> This should probably check for all errors except "not present"
>> rather than checking for -EPROBE_DEFER. We want to abort the
>> probe function for deferred probe as well as the case where we
>> a PHY was listed but isn't working properly.
>
> OK.
>
>>
>>>> + if (!IS_ERR(hpriv->phy)) {
>>>> + phy_init(hpriv->phy);
>>>
>>> Don't we have to check the return values of phy_init and phy_power_on? Is it
>>> not needed because it is an optional phy?
>>
>> Right. I think we should set hpriv->phy to NULL if it's not there and
>> then call the functions only if it's actually present but bail out on
>> an error.
>
> OK. How does this look?
>
> hpriv->phy = devm_phy_get(dev, "sata-phy");
> if (IS_ERR(hpriv->phy)) {
> if (PTR_ERR(hpriv->phy) == -ENODEV)
> goto continue;
yikes :P
goto phyinit;
>
> dev_err(dev, "couldn't get sata-phy\n");
> rc = PTR_ERR(hpriv->phy);
> goto disable_unprepare_clk;
> }
>
> continue:
phyinit:
>
> if (!IS_ERR(hpriv->phy)) {
> rc = phy_init(hpriv->phy);
> if (rc)
> goto disable_unprepare_clk;
>
> rc = phy_power_on(hpriv->phy);
> if (rc) {
> phy_exit(hpriv->phy);
> goto disable_unprepare_clk;
> }
> }
>
> cheers,
> -roger
>
next prev parent reply other threads:[~2014-01-08 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 9:47 [PATCH v3 0/3] ata: ahci_platform: Add PHY support and OMAP support Roger Quadros
2014-01-08 9:47 ` [PATCH v3 1/3] ata: ahci_platform: Update DT compatible list Roger Quadros
2014-01-08 9:47 ` [PATCH v3 2/3] ata: ahci_platform: Manage SATA PHY Roger Quadros
[not found] ` <1389174428-31414-3-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2014-01-08 9:59 ` Kishon Vijay Abraham I
[not found] ` <52CD2176.6050102-l0cyMroinI0@public.gmane.org>
2014-01-08 10:05 ` Arnd Bergmann
2014-01-08 11:28 ` Roger Quadros
2014-01-08 11:33 ` Roger Quadros [this message]
2014-01-08 11:46 ` Arnd Bergmann
2014-01-09 6:26 ` Roger Quadros
2014-01-09 10:05 ` Arnd Bergmann
2014-01-08 13:14 ` Hans de Goede
[not found] ` <52CD4F2A.9080301-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-01-08 15:55 ` Hans de Goede
2014-01-08 9:47 ` [PATCH v3 3/3] ata: ahci_platform: runtime resume the device before use Roger Quadros
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=52CD3774.3060701@ti.com \
--to=rogerq@ti.com \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=balajitk@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=kishon@ti.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).