From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "Andrew Lunn" <andrew@lunn.ch>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Maxim Georgiev" <glipus@gmail.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Richard Cochran" <richardcochran@gmail.com>,
"Vadim Fedorenko" <vadim.fedorenko@linux.dev>,
"Gerhard Engleder" <gerhard@engleder-embedded.com>,
"Hangbin Liu" <liuhangbin@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Jacob Keller" <jacob.e.keller@intel.com>,
"Jay Vosburgh" <j.vosburgh@gmail.com>,
"Andy Gospodarek" <andy@greyhouse.net>,
"Wei Fang" <wei.fang@nxp.com>,
"Shenwei Wang" <shenwei.wang@nxp.com>,
"Clark Wang" <xiaoning.wang@nxp.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
UNGLinuxDriver@microchip.com,
"Lars Povlsen" <lars.povlsen@microchip.com>,
"Steen Hegelund" <Steen.Hegelund@microchip.com>,
"Daniel Machon" <daniel.machon@microchip.com>,
"Simon Horman" <simon.horman@corigine.com>,
"Casper Andersson" <casper.casan@gmail.com>,
"Sergey Organov" <sorganov@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 net-next 00/10] Introduce ndo_hwtstamp_get() and ndo_hwtstamp_set()
Date: Fri, 14 Jul 2023 10:00:59 +0200 [thread overview]
Message-ID: <20230714080059.vig72wh34d7x5t7n@soft-dev3-1> (raw)
In-Reply-To: <20230713121907.3249291-1-vladimir.oltean@nxp.com>
The 07/13/2023 15:18, Vladimir Oltean wrote:
Hi Vladimir,
>
> Based on previous RFCs from Maxim Georgiev:
> https://lore.kernel.org/netdev/20230502043150.17097-1-glipus@gmail.com/
>
> this series attempts to introduce new API for the hardware timestamping
> control path (SIOCGHWTSTAMP and SIOCSHWTSTAMP handling).
>
> I don't have any board with phylib hardware timestamping, so I would
> appreciate testing (especially on lan966x, the most intricate
> conversion). I was, however, able to test netdev level timestamping,
> because I also have some more unsubmitted conversions in progress:
>
> https://github.com/vladimiroltean/linux/commits/ndo-hwtstamp-v7
I have tested this patch series on lan966x. In both cases, when there is
a PHY that supports HW timestamping and when the isn't a PHY that
supports HW timestamping. In both cases it behaves as expected. Thanks!
Tested-by: Horatiu Vultur <horatiu.vultur@microchip.com>
>
> I hope that the concerns expressed in the comments of previous series
> were addressed, and that Köry Maincent's series:
> https://lore.kernel.org/netdev/20230406173308.401924-1-kory.maincent@bootlin.com/
> can make progress in parallel with the conversion of the rest of drivers.
>
> Maxim Georgiev (5):
> net: add NDOs for configuring hardware timestamping
> net: add hwtstamping helpers for stackable net devices
> net: vlan: convert to ndo_hwtstamp_get() / ndo_hwtstamp_set()
> net: macvlan: convert to ndo_hwtstamp_get() / ndo_hwtstamp_set()
> net: bonding: convert to ndo_hwtstamp_get() / ndo_hwtstamp_set()
>
> Vladimir Oltean (5):
> net: fec: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
> net: fec: delete fec_ptp_disable_hwts()
> net: sparx5: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
> net: lan966x: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set()
> net: remove phy_has_hwtstamp() -> phy_mii_ioctl() decision from
> converted drivers
>
> drivers/net/bonding/bond_main.c | 105 ++++++----
> drivers/net/ethernet/freescale/fec.h | 6 +-
> drivers/net/ethernet/freescale/fec_main.c | 41 ++--
> drivers/net/ethernet/freescale/fec_ptp.c | 43 ++--
> .../ethernet/microchip/lan966x/lan966x_main.c | 61 ++++--
> .../ethernet/microchip/lan966x/lan966x_main.h | 12 +-
> .../ethernet/microchip/lan966x/lan966x_ptp.c | 34 ++--
> .../ethernet/microchip/sparx5/sparx5_main.h | 9 +-
> .../ethernet/microchip/sparx5/sparx5_netdev.c | 35 +++-
> .../ethernet/microchip/sparx5/sparx5_ptp.c | 24 ++-
> drivers/net/macvlan.c | 34 ++--
> include/linux/net_tstamp.h | 28 +++
> include/linux/netdevice.h | 25 +++
> net/8021q/vlan_dev.c | 27 ++-
> net/core/dev_ioctl.c | 183 +++++++++++++++++-
> 15 files changed, 480 insertions(+), 187 deletions(-)
>
> --
> 2.34.1
>
--
/Horatiu
next prev parent reply other threads:[~2023-07-14 8:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 12:18 [PATCH v7 net-next 00/10] Introduce ndo_hwtstamp_get() and ndo_hwtstamp_set() Vladimir Oltean
2023-07-13 12:18 ` [PATCH v7 net-next 01/10] net: add NDOs for configuring hardware timestamping Vladimir Oltean
2023-07-13 12:18 ` [PATCH v7 net-next 02/10] net: add hwtstamping helpers for stackable net devices Vladimir Oltean
2023-07-13 12:19 ` [PATCH v7 net-next 03/10] net: vlan: convert to ndo_hwtstamp_get() / ndo_hwtstamp_set() Vladimir Oltean
2023-07-13 12:19 ` [PATCH v7 net-next 04/10] net: macvlan: " Vladimir Oltean
2023-07-13 12:19 ` [PATCH v7 net-next 05/10] net: bonding: " Vladimir Oltean
2023-07-13 12:19 ` [PATCH v7 net-next 06/10] net: fec: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set() Vladimir Oltean
2023-07-14 3:05 ` Wei Fang
2023-07-14 8:47 ` Russell King (Oracle)
2023-07-14 9:08 ` Wei Fang
2023-07-13 12:19 ` [PATCH v7 net-next 07/10] net: fec: delete fec_ptp_disable_hwts() Vladimir Oltean
2023-07-14 3:06 ` Wei Fang
2023-07-13 12:19 ` [PATCH v7 net-next 08/10] net: sparx5: convert to ndo_hwtstamp_get() and ndo_hwtstamp_set() Vladimir Oltean
2023-07-13 12:19 ` [PATCH v7 net-next 09/10] net: lan966x: " Vladimir Oltean
2023-07-13 12:19 ` [PATCH v7 net-next 10/10] net: remove phy_has_hwtstamp() -> phy_mii_ioctl() decision from converted drivers Vladimir Oltean
2023-07-14 2:50 ` Jakub Kicinski
2023-07-13 21:50 ` [PATCH v7 net-next 00/10] Introduce ndo_hwtstamp_get() and ndo_hwtstamp_set() Jacob Keller
2023-07-13 22:33 ` Vladimir Oltean
2023-07-13 22:36 ` Jacob Keller
2023-07-14 8:00 ` Horatiu Vultur [this message]
2023-07-17 11:29 ` Vladimir Oltean
2023-07-17 1:22 ` Max Georgiev
2023-07-17 11:25 ` Vladimir Oltean
2023-07-17 20:23 ` Jacob Keller
2023-07-18 3:28 ` Richard Cochran
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=20230714080059.vig72wh34d7x5t7n@soft-dev3-1 \
--to=horatiu.vultur@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=andy@greyhouse.net \
--cc=casper.casan@gmail.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gerhard@engleder-embedded.com \
--cc=glipus@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=liuhangbin@gmail.com \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shenwei.wang@nxp.com \
--cc=simon.horman@corigine.com \
--cc=sorganov@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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).