From: Florian Fainelli <f.fainelli@gmail.com>
To: "Måns Rullgård" <mans@mansr.com>, Mason <slash.tmp@free.fr>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: phy: at803x: support interrupt on 8030 and 8035
Date: Thu, 12 Nov 2015 11:14:56 -0800 [thread overview]
Message-ID: <5644E530.7010101@gmail.com> (raw)
In-Reply-To: <E36D31CC-04BA-4BE5-83C5-DE3264B617D4@mansr.com>
On 12/11/15 11:09, Måns Rullgård wrote:
> On 12 November 2015 19:06:23 GMT+00:00, Mason <slash.tmp@free.fr> wrote:
>> On 12/11/2015 18:40, Mans Rullgard wrote:
>>> Commit 77a993942 "phy/at8031: enable at8031 to work on interrupt
>> mode"
>>> added interrupt support for the 8031 PHY but left out the other two
>>> chips supported by this driver.
>>>
>>> This patch sets the .ack_interrupt and .config_intr functions for the
>>> 8030 and 8035 drivers as well.
>>>
>>> Signed-off-by: Mans Rullgard <mans@mansr.com>
>>> ---
>>> I have only tested this with an 8035. I can't find a datasheet for
>>> the 8030, but since 8031, 8032, and 8035 all have the same register
>>> layout, there's a good chance 8030 does as well.
>>> ---
>>> drivers/net/phy/at803x.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/net/phy/at803x.c b/drivers/net/phy/at803x.c
>>> index fabf11d..2d020a3 100644
>>> --- a/drivers/net/phy/at803x.c
>>> +++ b/drivers/net/phy/at803x.c
>>> @@ -308,6 +308,8 @@ static struct phy_driver at803x_driver[] = {
>>> .flags = PHY_HAS_INTERRUPT,
>>> .config_aneg = genphy_config_aneg,
>>> .read_status = genphy_read_status,
>>> + .ack_interrupt = at803x_ack_interrupt,
>>> + .config_intr = at803x_config_intr,
>>> .driver = {
>>> .owner = THIS_MODULE,
>>> },
>>> @@ -327,6 +329,8 @@ static struct phy_driver at803x_driver[] = {
>>> .flags = PHY_HAS_INTERRUPT,
>>> .config_aneg = genphy_config_aneg,
>>> .read_status = genphy_read_status,
>>> + .ack_interrupt = at803x_ack_interrupt,
>>> + .config_intr = at803x_config_intr,
>>> .driver = {
>>> .owner = THIS_MODULE,
>>> },
>>
>> Shouldn't we take the opportunity to clean up the duplicated register
>> definitions? (I'll send an informal patch to spur discussion.)
>>
>> Regards.
>
> That can be done independently. Feel free to send a patch.
Agreed, that deserve a separate patch.
--
Florian
next prev parent reply other threads:[~2015-11-12 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 17:40 [PATCH] net: phy: at803x: support interrupt on 8030 and 8035 Mans Rullgard
2015-11-12 19:06 ` Mason
2015-11-12 19:09 ` Måns Rullgård
2015-11-12 19:14 ` Florian Fainelli [this message]
2015-11-12 22:14 ` Mason
2015-11-12 22:28 ` Måns Rullgård
2015-11-12 19:15 ` Florian Fainelli
2015-11-16 19:19 ` 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=5644E530.7010101@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=slash.tmp@free.fr \
/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.