From: Florian Fainelli <f.fainelli@gmail.com>
To: Antoine Tenart <antoine.tenart@bootlin.com>,
davem@davemloft.net, alexandre.belloni@bootlin.com,
UNGLinuxDriver@microchip.com, ralf@linux-mips.org,
paul.burton@mips.com, jhogan@kernel.org
Cc: netdev@vger.kernel.org, linux-mips@vger.kernel.org,
thomas.petazzoni@bootlin.com, quentin.schulz@bootlin.com,
allan.nielsen@microchip.com
Subject: Re: [PATCH net-next 0/8] net: mscc: PTP offloading support
Date: Thu, 17 Jan 2019 21:07:05 -0800 [thread overview]
Message-ID: <d6ed760a-a236-189f-b3e9-8a668fdf371f@gmail.com> (raw)
In-Reply-To: <20190117100212.2336-1-antoine.tenart@bootlin.com>
On 1/17/2019 2:02 AM, Antoine Tenart wrote:
> Hi all,
>
> This series adds support for the PTP offloading support in the Mscc
> Ocelot Ethernet switch driver. Both PTP 1-step and 2-step modes are
> supported.
>
> In order to make use of the PTP offloading support, two new register
> banks were described in the Ocelot device tree. The use of those
> registers by the Mscc Ocelot Ethernet switch driver is made optional for
> dt compatibility reasons. For the same reason a new interrupt is
> described, and its use is also made optinal for compatibility reasons.
> All of this is done ine patches 1-5.
>
> The PTP offloading support itself is added in patch 8.
>
> While doing this support, a few reworks were done in the Ocelot switch
> driver, in patches 6-7.
>
> Patches 2 and 4 should probably go through the MIPS tree.
Looks like you missed copying netdev on this patch series, do you mind
re-sending there as well?
>
> Thanks!
> Antoine
>
> Antoine Tenart (8):
> Documentation/bindings: net: ocelot: document the VCAP and PTP banks
> MIPS: dts: mscc: describe VCAP and PTP register ranges
> Documentation/bindings: net: ocelot: document the PTP ready IRQ
> MIPS: dts: mscc: describe the PTP ready interrupt
> net: mscc: describe the VCAP and PTP register ranges
> net: mscc: improve the frame header parsing readability
> net: mscc: remove the frame_info cpuq member
> net: mscc: PTP offloading support
>
> .../devicetree/bindings/net/mscc-ocelot.txt | 22 +-
> arch/mips/boot/dts/mscc/ocelot.dtsi | 14 +-
> drivers/net/ethernet/mscc/ocelot.c | 509 +++++++++++++++++-
> drivers/net/ethernet/mscc/ocelot.h | 55 +-
> drivers/net/ethernet/mscc/ocelot_board.c | 150 +++++-
> drivers/net/ethernet/mscc/ocelot_ptp.h | 41 ++
> drivers/net/ethernet/mscc/ocelot_regs.c | 22 +
> drivers/net/ethernet/mscc/ocelot_vcap.h | 104 ++++
> 8 files changed, 877 insertions(+), 40 deletions(-)
> create mode 100644 drivers/net/ethernet/mscc/ocelot_ptp.h
> create mode 100644 drivers/net/ethernet/mscc/ocelot_vcap.h
>
--
Florian
next prev parent reply other threads:[~2019-01-18 5:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 10:02 [PATCH net-next 0/8] net: mscc: PTP offloading support Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 1/8] Documentation/bindings: net: ocelot: document the VCAP and PTP banks Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 2/8] MIPS: dts: mscc: describe VCAP and PTP register ranges Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 3/8] Documentation/bindings: net: ocelot: document the PTP ready IRQ Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 4/8] MIPS: dts: mscc: describe the PTP ready interrupt Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 5/8] net: mscc: describe the VCAP and PTP register ranges Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 6/8] net: mscc: improve the frame header parsing readability Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 7/8] net: mscc: remove the frame_info cpuq member Antoine Tenart
2019-01-17 10:02 ` [PATCH net-next 8/8] net: mscc: PTP offloading support Antoine Tenart
2019-01-18 2:23 ` Richard Cochran
2019-01-18 9:08 ` Antoine Tenart
2019-01-18 2:13 ` [PATCH net-next 0/8] " Richard Cochran
2019-01-18 9:09 ` Antoine Tenart
2019-01-18 5:07 ` Florian Fainelli [this message]
2019-01-18 8:58 ` Antoine Tenart
2019-01-18 18:16 ` Florian Fainelli
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=d6ed760a-a236-189f-b3e9-8a668fdf371f@gmail.com \
--to=f.fainelli@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=antoine.tenart@bootlin.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=quentin.schulz@bootlin.com \
--cc=ralf@linux-mips.org \
--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).