From: Andrew Lunn <andrew@lunn.ch>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, vivien.didelot@savoirfairelinux.com,
gregory.clement@free-electrons.com
Subject: Re: [PATCH 0/2] mv88e6xxx: Poll when no interrupt defined
Date: Mon, 26 Feb 2018 17:50:11 +0100 [thread overview]
Message-ID: <20180226165011.GF3775@lunn.ch> (raw)
In-Reply-To: <20180226.112958.1782855391937389110.davem@davemloft.net>
On Mon, Feb 26, 2018 at 11:29:58AM -0500, David Miller wrote:
> From: Andrew Lunn <andrew@lunn.ch>
> Date: Thu, 22 Feb 2018 22:58:31 +0100
>
> > 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?
>
> Still no response from Gregory after 4+ days, so I'm applying this
> to net-next.
Hi David
I pinged Gregory earlier today. He said he was on vacation last week,
and you get to it later today or tomorrow.
Andrew
next prev parent reply other threads:[~2018-02-26 16:50 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 [this message]
2018-02-27 10:24 ` Gregory CLEMENT
2018-02-27 14:07 ` Andrew Lunn
2018-02-27 15:42 ` Gregory CLEMENT
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=20180226165011.GF3775@lunn.ch \
--to=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).