From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>, grant.likely@linaro.org
Cc: ben.dooks@codethink.co.uk, linux-kernel@lists.codethink.co.uk,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] of_mdio: fix phy interrupt passing
Date: Wed, 19 Feb 2014 13:27:39 +0000 [thread overview]
Message-ID: <5304B14B.2070402@cogentembedded.com> (raw)
In-Reply-To: <20140218.181317.1712776234149210938.davem@davemloft.net>
Hello.
On 19-02-2014 3:13, David Miller wrote:
>>> The of_mdiobus_register_phy() is not setting phy->irq thus causing
>>> some drivers to incorrectly assume that the PHY does not have an
>>> IRQ associated with it. Not only do some drivers report no IRQ
>>> they do not install an interrupt handler for the PHY.
>>> Simplify the code setting irq and set the phy->irq at the same
>>> time so that we cover the following issues, which should cover
>>> all the cases the code will find:
>>> - Set phy->irq if node has irq property and mdio->irq is NULL
>>> - Set phy->irq if node has no irq and mdio->irq is not NULL
>>> - Leave phy->irq as PHY_POLL default if none of the above
>>> 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>
>> Looks okay to me
>> Reviewed-by: Grant Likely <grant.likely@linaro.org>
> Applied, thanks.
So, you decided to ignore my comment about unneeded *else* branch?
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: David Miller <davem@davemloft.net>, grant.likely@linaro.org
Cc: ben.dooks@codethink.co.uk, linux-kernel@lists.codethink.co.uk,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] of_mdio: fix phy interrupt passing
Date: Wed, 19 Feb 2014 17:27:39 +0400 [thread overview]
Message-ID: <5304B14B.2070402@cogentembedded.com> (raw)
In-Reply-To: <20140218.181317.1712776234149210938.davem@davemloft.net>
Hello.
On 19-02-2014 3:13, David Miller wrote:
>>> The of_mdiobus_register_phy() is not setting phy->irq thus causing
>>> some drivers to incorrectly assume that the PHY does not have an
>>> IRQ associated with it. Not only do some drivers report no IRQ
>>> they do not install an interrupt handler for the PHY.
>>> Simplify the code setting irq and set the phy->irq at the same
>>> time so that we cover the following issues, which should cover
>>> all the cases the code will find:
>>> - Set phy->irq if node has irq property and mdio->irq is NULL
>>> - Set phy->irq if node has no irq and mdio->irq is not NULL
>>> - Leave phy->irq as PHY_POLL default if none of the above
>>> 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>
>> Looks okay to me
>> Reviewed-by: Grant Likely <grant.likely@linaro.org>
> Applied, thanks.
So, you decided to ignore my comment about unneeded *else* branch?
WBR, Sergei
next prev parent reply other threads:[~2014-02-19 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 12:16 [PATCH v2] of_mdio: fix phy interrupt passing Ben Dooks
2014-02-18 12:16 ` Ben Dooks
2014-02-18 14:48 ` Sergei Shtylyov
2014-02-18 14:48 ` Sergei Shtylyov
2014-02-18 16:15 ` Grant Likely
2014-02-18 16:15 ` Grant Likely
2014-02-18 16:15 ` Grant Likely
2014-02-18 23:13 ` David Miller
2014-02-18 23:13 ` David Miller
2014-02-19 13:27 ` Sergei Shtylyov [this message]
2014-02-19 13:27 ` Sergei Shtylyov
2014-02-19 17:54 ` David Miller
2014-02-19 17:54 ` David Miller
2014-02-18 19:29 ` Sergei Shtylyov
2014-02-18 20:29 ` 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=5304B14B.2070402@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=ben.dooks@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.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 \
/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.