From: Tejun Heo <tj@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Jason Cooper <jason@lakedaemon.net>,
devicetree@vger.kernel.org, linux-ide@vger.kernel.org,
Gregory Clement <gregory.clement@free-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 3/4] SATA: MV: Add support for the optional PHYs
Date: Thu, 19 Dec 2013 14:42:37 -0500 [thread overview]
Message-ID: <20131219194237.GC22725@htj.dyndns.org> (raw)
In-Reply-To: <20131219191027.GI4143@lunn.ch>
Hello,
On Thu, Dec 19, 2013 at 08:10:27PM +0100, Andrew Lunn wrote:
> > Shouldn't it distinguish between failures and at least produce
> > warning? ie. phy not available and phy init failed due to memory
> > pressure or whatnot shouldn't be handled the same.
>
> Phy not available is not an error, since not all variants of the SATA
^
always
> IP block have the ability to control the phy. I can however add a
> warning for real errors.
Yes, please.
> > > > @@ -4132,6 +4148,8 @@ err:
> > > > clk_disable_unprepare(hpriv->port_clks[port]);
> > > > clk_put(hpriv->port_clks[port]);
> > > > }
> > > > + if (!IS_ERR(hpriv->port_phys[port]))
> > > > + phy_power_off(hpriv->port_phys[port]);
> >
> > And I'd much prefer the array holds either NULL or valid pointer.
>
> I was trying to keep the code similar to the clk handling. However now
> that it is diverging more and more from how clk is handled, i can add
> yet more divergence and overwrite the error with a NULL.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-12-19 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 20:21 [PATCH 1/4] Phy: DT binding documentation for Marvell MVEBU SATA phy Andrew Lunn
2013-12-17 20:21 ` [PATCH 2/4] Phy: Add a PHY driver for Marvell MVEBU SATA PHY Andrew Lunn
2013-12-19 10:40 ` Kishon Vijay Abraham I
2013-12-17 20:21 ` [PATCH 3/4] SATA: MV: Add support for the optional PHYs Andrew Lunn
2013-12-18 6:30 ` Kishon Vijay Abraham I
2013-12-18 12:13 ` Tejun Heo
2013-12-19 19:10 ` Andrew Lunn
2013-12-19 19:42 ` Tejun Heo [this message]
2013-12-26 17:25 ` [PATCH v4 0/4] PHY Driver for Marvell SATA Andrew Lunn
2013-12-26 17:25 ` [PATCH v4 1/4] Phy: DT binding documentation for Marvell MVEBU SATA phy Andrew Lunn
2013-12-26 17:25 ` [PATCH v4 2/4] Phy: Add a PHY driver for Marvell MVEBU SATA PHY Andrew Lunn
2013-12-27 16:33 ` Kishon Vijay Abraham I
2014-01-10 19:31 ` Jason Cooper
2014-01-11 11:12 ` Kishon Vijay Abraham I
2013-12-26 17:25 ` [PATCH v4 3/4] SATA: MV: Add support for the optional PHYs Andrew Lunn
2014-01-20 12:47 ` Tejun Heo
2013-12-26 17:25 ` [PATCH v4 4/4] Phy: Add DT nodes on kirkwood and Dove for the SATA PHY Andrew Lunn
[not found] ` <52B140F2.8070900-l0cyMroinI0@public.gmane.org>
2013-12-19 19:03 ` [PATCH 3/4] SATA: MV: Add support for the optional PHYs Andrew Lunn
2013-12-20 3:25 ` Jason Cooper
2013-12-17 20:21 ` [PATCH 4/4] Phy: Add DT nodes on kirkwood and Dove for the SATA PHY Andrew Lunn
2013-12-18 6:32 ` Kishon Vijay Abraham I
2013-12-22 17:21 ` Jason Cooper
2013-12-17 20:27 ` [PATCH 1/4] Phy: DT binding documentation for Marvell MVEBU SATA phy Andrew Lunn
2013-12-20 3:21 ` Jason Cooper
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=20131219194237.GC22725@htj.dyndns.org \
--to=tj@kernel.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=sebastian.hesselbarth@googlemail.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;
as well as URLs for NNTP newsgroup(s).