From: Jakub Kicinski <kuba@kernel.org>
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<woojung.huh@microchip.com>, <UNGLinuxDriver@microchip.com>,
<andrew@lunn.ch>, <vivien.didelot@gmail.com>,
<f.fainelli@gmail.com>, <olteanv@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<linux@armlinux.org.uk>, <Tristram.Ha@microchip.com>,
<richardcochran@gmail.com>, <ceggers@arri.de>
Subject: Re: [Patch net-next v4 00/13] net: dsa: microchip: add PTP support for KSZ9563/KSZ8563 and LAN937x
Date: Mon, 12 Dec 2022 15:47:23 -0800 [thread overview]
Message-ID: <20221212154723.4a7cebcf@kernel.org> (raw)
In-Reply-To: <20221212102639.24415-1-arun.ramadoss@microchip.com>
On Mon, 12 Dec 2022 15:56:26 +0530 Arun Ramadoss wrote:
> KSZ9563/KSZ8563 and LAN937x switch are capable for supporting IEEE 1588 PTP
> protocol. LAN937x has the same PTP register set similar to KSZ9563, hence the
> implementation has been made common for the KSZ switches. KSZ9563 does not
> support two step timestamping but LAN937x supports both. Tested the 1step &
> 2step p2p timestamping in LAN937x and p2p1step timestamping in KSZ9563.
>
> This patch series is based on the Christian Eggers PTP support for KSZ9563.
> Applied the Christian patch and updated as per the latest refactoring of KSZ
> series code. The features added on top are PTP packet Interrupt
> implementation based on nested handler, LAN937x two step timestamping and
> programmable per_out pins.
The merge window has now begun, this set is rather large and Linus said
that he will be particularly strict about applying patches late:
https://lore.kernel.org/all/CAHk-=wj_HcgFZNyZHTLJ7qC2613zphKDtLh6ndciwopZRfH0aQ@mail.gmail.com/
So let's defer this for after 6.2-rc1 is cut. Feed free to switch to
RFC postings if you want to keep revising the set and make review
progress during the merge window.
prev parent reply other threads:[~2022-12-12 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 10:26 [Patch net-next v4 00/13] net: dsa: microchip: add PTP support for KSZ9563/KSZ8563 and LAN937x Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 01/13] net: dsa: microchip: ptp: add the posix clock support Arun Ramadoss
2022-12-19 22:08 ` Jacob Keller
2022-12-12 10:26 ` [Patch net-next v4 02/13] net: dsa: microchip: ptp: Initial hardware time stamping support Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 03/13] net: dsa: microchip: ptp: add 4 bytes in tail tag when ptp enabled Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 04/13] net: dsa: microchip: ptp: manipulating absolute time using ptp hw clock Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 05/13] net: dsa: microchip: ptp: enable interrupt for timestamping Arun Ramadoss
2022-12-19 12:38 ` Vladimir Oltean
2022-12-12 10:26 ` [Patch net-next v4 06/13] net: ptp: add helper for one-step P2P clocks Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 07/13] net: dsa: microchip: ptp: add packet reception timestamping Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 08/13] net: dsa: microchip: ptp: add packet transmission timestamping Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 09/13] net: dsa: microchip: ptp: move pdelay_rsp correction field to tail tag Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 10/13] net: dsa: microchip: ptp: add periodic output signal Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 11/13] net: dsa: microchip: ptp: add support for perout programmable pins Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 12/13] net: dsa: microchip: ptp: lan937x: add 2 step timestamping Arun Ramadoss
2022-12-12 10:26 ` [Patch net-next v4 13/13] net: dsa: microchip: ptp: lan937x: Enable periodic output in LED pins Arun Ramadoss
2022-12-12 15:48 ` [Patch net-next v4 00/13] net: dsa: microchip: add PTP support for KSZ9563/KSZ8563 and LAN937x Christian Eggers
2022-12-12 23:47 ` Jakub Kicinski [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=20221212154723.4a7cebcf@kernel.org \
--to=kuba@kernel.org \
--cc=Tristram.Ha@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=ceggers@arri.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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).