diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2023-08-03 05:11:08 +0300 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2023-08-03 05:11:09 +0300 |
| commit | b23ec2bd7b847aa8e453d8bb5f62d31176b535f3 (patch) | |
| tree | 50922037e9cae3202cbc702a297f0d2bc2ad12f3 /arch | |
| parent | 72c1a28473fb132f08a2a447dd1425a472696cd9 (diff) | |
| parent | fd770e856e226f80fe6e1dc9d1861bcb135cdf0b (diff) | |
| download | linux-b23ec2bd7b847aa8e453d8bb5f62d31176b535f3.tar.xz | |
Merge branch 'introduce-ndo_hwtstamp_get-and-ndo_hwtstamp_set'
Vladimir Oltean says:
====================
Introduce ndo_hwtstamp_get() and ndo_hwtstamp_set()
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-v9
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.
====================
Link: https://lore.kernel.org/r/20230801142824.1772134-1-vladimir.oltean@nxp.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions