From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: mkubecek@suse.cz, Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH ethtool-next] netlink: tsconfig: add HW time stamping configuration
Date: Mon, 6 Oct 2025 13:55:24 +0100 [thread overview]
Message-ID: <ea0c839e-d0a7-450d-abd7-0a787804b415@linux.dev> (raw)
In-Reply-To: <20251006144512.003d4d13@kmaincent-XPS-13-7390>
On 06/10/2025 13:45, Kory Maincent wrote:
> On Sat, 4 Oct 2025 20:27:15 +0000
> Vadim Fedorenko <vadim.fedorenko@linux.dev> wrote:
>
>> The kernel supports configuring HW time stamping modes via netlink
>> messages, but previous implementation added support for HW time stamping
>> source configuration. Add support to configure TX/RX time stamping.
>
> For the information, I didn't add this support because it kind of conflict with
> ptp4l which is already configuring this. So if you set it with ethtool, running
> ptp4l will change it. I am not really a PTP user so maybe I missed cases where
> we need these hwtstamp config change without using ptp4l.
Well, it's more about ability to configure HW time stamping by users.
Running software will potentially change the configuration anyways, but
it maybe helpful to test different HW configurations without changing
the software itself.
next prev parent reply other threads:[~2025-10-06 12:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 20:27 [PATCH ethtool-next] netlink: tsconfig: add HW time stamping configuration Vadim Fedorenko
2025-10-06 12:45 ` Kory Maincent
2025-10-06 12:55 ` Vadim Fedorenko [this message]
2025-10-06 17:55 ` Jakub Kicinski
2025-10-26 16:57 ` Michal Kubecek
2025-10-28 9:40 ` Kory Maincent
2025-10-28 21:48 ` Vadim Fedorenko
2025-10-29 16:26 ` Michal Kubecek
2025-10-29 18:53 ` Vadim Fedorenko
2025-10-29 22:38 ` Jakub Kicinski
2025-10-30 14:37 ` Kory Maincent
2025-10-30 15:14 ` Jakub Kicinski
2025-10-30 16:43 ` Kory Maincent
2025-10-30 18:23 ` Michal Kubecek
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=ea0c839e-d0a7-450d-abd7-0a787804b415@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
/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).