From: Antoine Tenart <antoine.tenart@bootlin.com>
To: davem@davemloft.net, richardcochran@gmail.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
ralf@linux-mips.org, paul.burton@mips.com, jhogan@kernel.org
Cc: Antoine Tenart <antoine.tenart@bootlin.com>,
netdev@vger.kernel.org, linux-mips@vger.kernel.org,
thomas.petazzoni@bootlin.com, allan.nielsen@microchip.com
Subject: Re: [PATCH net-next v3 4/8] MIPS: dts: mscc: describe the PTP ready interrupt
Date: Thu, 22 Aug 2019 09:56:40 +0200 [thread overview]
Message-ID: <20190822075640.GB3006@kwain> (raw)
In-Reply-To: <20190724081715.29159-5-antoine.tenart@bootlin.com>
Hello,
On Wed, Jul 24, 2019 at 10:17:11AM +0200, Antoine Tenart wrote:
> This patch adds a description of the PTP ready interrupt, which can be
> triggered when a PTP timestamp is available on an hardware FIFO.
>
> Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
> Acked-by: Paul Burton <paul.burton@mips.com>
The net patches of this series were applied into the net-next tree.
However the two dts patches were not and should go through the MIPS
tree. Gentle ping about this :)
Thanks,
Antoine
> ---
> arch/mips/boot/dts/mscc/ocelot.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/boot/dts/mscc/ocelot.dtsi b/arch/mips/boot/dts/mscc/ocelot.dtsi
> index 1e55a778def5..797d336db54d 100644
> --- a/arch/mips/boot/dts/mscc/ocelot.dtsi
> +++ b/arch/mips/boot/dts/mscc/ocelot.dtsi
> @@ -139,8 +139,8 @@
> "port2", "port3", "port4", "port5", "port6",
> "port7", "port8", "port9", "port10", "qsys",
> "ana", "s2";
> - interrupts = <21 22>;
> - interrupt-names = "xtr", "inj";
> + interrupts = <18 21 22>;
> + interrupt-names = "ptp_rdy", "xtr", "inj";
>
> ethernet-ports {
> #address-cells = <1>;
> --
> 2.21.0
>
--
Antoine Ténart, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-22 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 8:17 [PATCH net-next v3 0/8] net: mscc: PTP Hardware Clock (PHC) support Antoine Tenart
2019-07-24 8:17 ` [PATCH net-next v3 1/8] Documentation/bindings: net: ocelot: document the PTP bank Antoine Tenart
2019-07-24 8:17 ` [PATCH net-next v3 2/8] MIPS: dts: mscc: describe the PTP register range Antoine Tenart
2019-08-24 14:18 ` Paul Burton
2019-07-24 8:17 ` [PATCH net-next v3 3/8] Documentation/bindings: net: ocelot: document the PTP ready IRQ Antoine Tenart
2019-07-24 8:17 ` [PATCH net-next v3 4/8] MIPS: dts: mscc: describe the PTP ready interrupt Antoine Tenart
2019-08-22 7:56 ` Antoine Tenart [this message]
2019-08-24 14:18 ` Paul Burton
2019-07-24 8:17 ` [PATCH net-next v3 5/8] net: mscc: describe the PTP register range Antoine Tenart
2019-07-24 8:17 ` [PATCH net-next v3 6/8] net: mscc: improve the frame header parsing readability Antoine Tenart
2019-07-24 8:17 ` [PATCH net-next v3 7/8] net: mscc: remove the frame_info cpuq member Antoine Tenart
2019-07-24 8:17 ` [PATCH net-next v3 8/8] net: mscc: PTP Hardware Clock (PHC) support Antoine Tenart
2019-07-24 13:53 ` Richard Cochran
2019-07-24 18:52 ` David Miller
2019-07-25 7:24 ` Antoine Tenart
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=20190822075640.GB3006@kwain \
--to=antoine.tenart@bootlin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=davem@davemloft.net \
--cc=jhogan@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.org \
--cc=richardcochran@gmail.com \
--cc=thomas.petazzoni@bootlin.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).