From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Jamie Iles <jamie@jamieiles.com>
Cc: netdev@vger.kernel.org, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] at91_ether: use gpio_is_valid for phy IRQ line
Date: Fri, 25 Nov 2011 14:56:01 +0100 [thread overview]
Message-ID: <4ECF9E71.2050305@atmel.com> (raw)
In-Reply-To: <20111125134708.GM15531@game.jcrosoft.org>
On 11/25/2011 02:47 PM, Jean-Christophe PLAGNIOL-VILLARD :
> On 22:28 Thu 24 Nov , Jamie Iles wrote:
>> Hi Nicolas,
>>
>> On Thu, Nov 24, 2011 at 10:21:14PM +0100, Nicolas Ferre wrote:
>>> Use the generic gpiolib gpio_is_valid() function to test
>>> if the phy IRQ line GPIO is actually provided.
>>>
>>> For non-connected or non-existing phy IRQ lines, -EINVAL
>>> value is used for phy_irq_pin field of struct at91_eth_data.
>>>
>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>> ---
>>> drivers/net/ethernet/cadence/at91_ether.c | 23 +++++++++++++----------
>>> 1 files changed, 13 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/drivers/net/ethernet/cadence/at91_ether.c b/drivers/net/ethernet/cadence/at91_ether.c
>>> index 56624d3..a1c4143 100644
>>> --- a/drivers/net/ethernet/cadence/at91_ether.c
>>> +++ b/drivers/net/ethernet/cadence/at91_ether.c
>>> @@ -255,8 +255,7 @@ static void enable_phyirq(struct net_device *dev)
>>> unsigned int dsintr, irq_number;
>>> int status;
>>>
>>> - irq_number = lp->board_data.phy_irq_pin;
>>> - if (!irq_number) {
>>> + if (!gpio_is_valid(lp->board_data.phy_irq_pin)) {
>>> /*
>>> * PHY doesn't have an IRQ pin (RTL8201, DP83847, AC101L),
>>> * or board does not have it connected.
>>> @@ -265,6 +264,7 @@ static void enable_phyirq(struct net_device *dev)
>>> return;
>>> }
>>>
>>> + irq_number = lp->board_data.phy_irq_pin;
>>
>> Does this need to be:
>>
>> irq_number = gpio_to_irq(lp->board_data.phy_irq_pin);
>>
>> and the same for the other occurrences? Otherwise this looks like the
>> right thing to me.
> yes
True but I prefered to separate changes. As it was not addressed like
this in the code I clung to it. I will post an additional patch on top
of this one to add the gpio_to_irq() call.
> Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Best regards,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] at91_ether: use gpio_is_valid for phy IRQ line
Date: Fri, 25 Nov 2011 14:56:01 +0100 [thread overview]
Message-ID: <4ECF9E71.2050305@atmel.com> (raw)
In-Reply-To: <20111125134708.GM15531@game.jcrosoft.org>
On 11/25/2011 02:47 PM, Jean-Christophe PLAGNIOL-VILLARD :
> On 22:28 Thu 24 Nov , Jamie Iles wrote:
>> Hi Nicolas,
>>
>> On Thu, Nov 24, 2011 at 10:21:14PM +0100, Nicolas Ferre wrote:
>>> Use the generic gpiolib gpio_is_valid() function to test
>>> if the phy IRQ line GPIO is actually provided.
>>>
>>> For non-connected or non-existing phy IRQ lines, -EINVAL
>>> value is used for phy_irq_pin field of struct at91_eth_data.
>>>
>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>> ---
>>> drivers/net/ethernet/cadence/at91_ether.c | 23 +++++++++++++----------
>>> 1 files changed, 13 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/drivers/net/ethernet/cadence/at91_ether.c b/drivers/net/ethernet/cadence/at91_ether.c
>>> index 56624d3..a1c4143 100644
>>> --- a/drivers/net/ethernet/cadence/at91_ether.c
>>> +++ b/drivers/net/ethernet/cadence/at91_ether.c
>>> @@ -255,8 +255,7 @@ static void enable_phyirq(struct net_device *dev)
>>> unsigned int dsintr, irq_number;
>>> int status;
>>>
>>> - irq_number = lp->board_data.phy_irq_pin;
>>> - if (!irq_number) {
>>> + if (!gpio_is_valid(lp->board_data.phy_irq_pin)) {
>>> /*
>>> * PHY doesn't have an IRQ pin (RTL8201, DP83847, AC101L),
>>> * or board does not have it connected.
>>> @@ -265,6 +264,7 @@ static void enable_phyirq(struct net_device *dev)
>>> return;
>>> }
>>>
>>> + irq_number = lp->board_data.phy_irq_pin;
>>
>> Does this need to be:
>>
>> irq_number = gpio_to_irq(lp->board_data.phy_irq_pin);
>>
>> and the same for the other occurrences? Otherwise this looks like the
>> right thing to me.
> yes
True but I prefered to separate changes. As it was not addressed like
this in the code I clung to it. I will post an additional patch on top
of this one to add the gpio_to_irq() call.
> Acked-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2011-11-25 13:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 9:48 [PATCH] macb: convert platform data phy_irq_pin to an int Jamie Iles
2011-11-24 10:47 ` Nicolas Ferre
2011-11-24 21:21 ` [PATCH] at91_ether: use gpio_is_valid for phy IRQ line Nicolas Ferre
2011-11-24 21:21 ` Nicolas Ferre
2011-11-24 22:28 ` Jamie Iles
2011-11-24 22:28 ` Jamie Iles
2011-11-25 13:47 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 13:47 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 13:56 ` Nicolas Ferre [this message]
2011-11-25 13:56 ` Nicolas Ferre
2011-11-29 23:53 ` David Miller
2011-11-29 23:53 ` David Miller
2011-11-30 4:44 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-30 4:44 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-30 5:40 ` David Miller
2011-11-30 5:40 ` David Miller
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=4ECF9E71.2050305@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=sfr@canb.auug.org.au \
/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.