From: Grant Likely <grant.likely@linaro.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-kernel@lists.codethink.co.uk, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-sh@vger.kernel.org, sergei.shtylyov@cogentembedded.com
Subject: Re: [PATCH] of_mdio: fix phy interrupt passing
Date: Tue, 18 Feb 2014 17:02:02 +0000 [thread overview]
Message-ID: <20140218170202.424D7C40517@trevor.secretlab.ca> (raw)
In-Reply-To: <53032A97.8050201@codethink.co.uk>
On Tue, 18 Feb 2014 09:40:39 +0000, Ben Dooks <ben.dooks@codethink.co.uk> wrote:
> On 18/02/14 09:30, Grant Likely wrote:
> > On Mon, 17 Feb 2014 16:29:40 +0000, Ben Dooks <ben.dooks@codethink.co.uk> wrote:
> >> The of_mdiobus_register_phy() is not setting phy->irq this causing
> >> some drivers to incorrectly assume that the PHY does not have an
> >> IRQ associated with it or install an interrupt handler for the
> >> PHY.
> >>
> >> Simplify the code setting irq and set the phy->irq at the same
> >> time so that the case if mdio->irq is not NULL is easier to read.
> >>
> >> This fixes the issue:
> >> net eth0: attached PHY 1 (IRQ -1) to driver Micrel KSZ8041RNLI
> >>
> >> to the correct:
> >> net eth0: attached PHY 1 (IRQ 416) to driver Micrel KSZ8041RNLI
> >>
> >> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> >> ---
> >> drivers/of/of_mdio.c | 12 ++++++------
> >> 1 file changed, 6 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/drivers/of/of_mdio.c b/drivers/of/of_mdio.c
> >> index 875b7b6..7b3e7b0 100644
> >> --- a/drivers/of/of_mdio.c
> >> +++ b/drivers/of/of_mdio.c
> >> @@ -44,7 +44,7 @@ static int of_mdiobus_register_phy(struct mii_bus *mdio, struct device_node *chi
> >> {
> >> struct phy_device *phy;
> >> bool is_c45;
> >> - int rc, prev_irq;
> >> + int rc;
> >> u32 max_speed = 0;
> >>
> >> is_c45 = of_device_is_compatible(child,
> >> @@ -55,11 +55,11 @@ static int of_mdiobus_register_phy(struct mii_bus *mdio, struct device_node *chi
> >> return 1;
> >>
> >> if (mdio->irq) {
> >> - prev_irq = mdio->irq[addr];
> >> - mdio->irq[addr] =
> >> - irq_of_parse_and_map(child, 0);
> >> - if (!mdio->irq[addr])
> >> - mdio->irq[addr] = prev_irq;
> >
> > I cannot for the life for me remeber why the code was structured that
> > way. Your change is better.
> >
> >> + rc = irq_of_parse_and_map(child, 0);
> >> + if (rc > 0) {
> >> + mdio->irq[addr] = rc;
> >> + phy->irq = rc;
> >> + }
> >> }
> >
> > The outer if is merely protecting against no irq array being allocated
> > for the bus. Would not the following be better:
> >
> > rc = irq_of_parse_and_map(child, 0);
> > if (rc > 0) {
> > phy->irq = rc;
> > if (mdio->irq)
> > mdio->irq[addr] = rc;
> > }
>
> Thanks, that makes sense, although we've both failed to work
> out if mdio->irq is set, and rc <= 0 case, so:
>
> rc = irq_of_parse_and_map(child, 0);
> if (rc > 0) {
> phy->irq = rc;
> if (mdio->irq)
> mdio->irq[addr] = rc;
> } else {
> if (mdio->irq)
> phy->irq = mdio->irq[addr];
> }
Is this actually a valid thing to do? I think the only time mdio->irq[]
is non-zero is when it is set to PHY_POLL. Is it valid to set phy->irq
to PHY_POLL? I didn't think it was.
g.
>
> I think that covers all cases. This does rely on mdio->irq
> being initialised to PHY_POLL if allocated.
>
> Once this is in, it may be easier then to not allocate
> mdio->irq for the OF case by default unless the driver
> registering the PHY knows it has the interrupt number(s)
> for the PHY already.
>
> --
> Ben Dooks http://www.codethink.co.uk/
> Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-02-18 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 16:29 Ben Dooks
[not found] ` < 20140218093024.D0E94C403C8@trevor.secretlab.ca>
2014-02-17 17:26 ` Florian Fainelli
2014-02-17 17:42 ` Ben Dooks
2014-02-17 17:48 ` Florian Fainelli
2014-02-17 17:58 ` Ben Dooks
2014-02-19 20:18 ` Sergei Shtylyov
2014-02-17 17:56 ` Ben Dooks
2014-02-18 9:30 ` Grant Likely
2014-02-18 9:40 ` Ben Dooks
2014-02-18 17:02 ` Grant Likely [this message]
2014-02-18 18:06 ` Sergei Shtylyov
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=20140218170202.424D7C40517@trevor.secretlab.ca \
--to=grant.likely@linaro.org \
--cc=ben.dooks@codethink.co.uk \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@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
all inboxes | Powered by JetHome®