From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Gregory Clement <gregory.clement@free-electrons.com>
Subject: Re: [PATCH 0/2] mv88e6xxx: Poll when no interrupt defined
Date: Tue, 27 Feb 2018 16:42:20 +0100 [thread overview]
Message-ID: <87r2p6jv6r.fsf@bootlin.com> (raw)
In-Reply-To: <20180227140707.GA31805@lunn.ch> (Andrew Lunn's message of "Tue, 27 Feb 2018 15:07:07 +0100")
Hi Andrew,
On mar., févr. 27 2018, Andrew Lunn <andrew@lunn.ch> wrote:
> On Tue, Feb 27, 2018 at 11:24:02AM +0100, Gregory CLEMENT wrote:
>> Hi Andrew,
>>
>> On jeu., févr. 22 2018, Andrew Lunn <andrew@lunn.ch> wrote:
>>
>> > Not all boards using the mv88e6xxx switches have the interrupt output
>> > connected to a GPIO. On these boards phylib has to poll the PHYs,
>> > rather than use interrupts. Have the driver poll the interrupt status
>> > register, which is more efficient than having phylib do it. And it
>> > enables other switch interrupts to be services.
>> >
>> > The Armada 370RD is such a board without a interrupt GPIO. Now that
>> > interrupts work, wire up the PHYs to make use if them.
>> >
>> > Gregory: Are you O.K. for the second patch to go through netdev?
>>
>> Why do you need that the second patch to go through netdev. Is there any
>> dependency between the 2 patches?
>>
>> If it is the case does it means that an new kernel won't work with an
>> old device tree?
>
> Hi Gregory
>
> There is a runtime dependency between the two. A new device tree blob
> will not run on an old kernel. So if you take the second patch alone
> via mvebu, the PHYs will stop working, no link up reported.
>
> But an old blob will run on a new kernel. Backwards compatibility is
> maintained.
Ok so you wanted to keep the kernel bisctable.
So I'm fine with having this patch in netdev (and I think it is alrdeay
the case).
Gregory
>
> Andrew
--
Gregory Clement, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-27 15:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 21:58 [PATCH 0/2] mv88e6xxx: Poll when no interrupt defined Andrew Lunn
2018-02-22 21:58 ` [PATCH 1/2] net: dsa: " Andrew Lunn
2018-02-22 21:58 ` [PATCH 2/2] arm: mvebu: 370-rd: Enable PHY interrupt handling Andrew Lunn
2018-02-23 17:32 ` [PATCH 0/2] mv88e6xxx: Poll when no interrupt defined David Miller
2018-02-26 16:29 ` David Miller
2018-02-26 16:50 ` Andrew Lunn
2018-02-27 10:24 ` Gregory CLEMENT
2018-02-27 14:07 ` Andrew Lunn
2018-02-27 15:42 ` Gregory CLEMENT [this message]
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=87r2p6jv6r.fsf@bootlin.com \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gregory.clement@free-electrons.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).