From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, sdf@fomichev.me,
almasrymina@google.com, asml.silence@gmail.com,
leitao@debian.org, kuniyu@google.com, jiri@resnulli.us,
aleksandr.loktionov@intel.com, ivecera@redhat.com,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [RFC PATCH v2] net: add net-device TX clock source selection framework
Date: Thu, 28 Aug 2025 15:31:57 -0700 [thread overview]
Message-ID: <20250828153157.6b0a975f@kernel.org> (raw)
In-Reply-To: <20250828164345.116097-1-arkadiusz.kubalewski@intel.com>
On Thu, 28 Aug 2025 18:43:45 +0200 Arkadiusz Kubalewski wrote:
> Add support for user-space control over network device transmit clock
> sources through a new extended netdevice netlink interface.
> A network device may support multiple TX clock sources (OCXO, SyncE
> reference, external reference clocks) which are critical for
> time-sensitive networking applications and synchronization protocols.
how does this relate to the dpll pin in rtnetlink then?
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, sdf@fomichev.me,
almasrymina@google.com, asml.silence@gmail.com,
leitao@debian.org, kuniyu@google.com, jiri@resnulli.us,
aleksandr.loktionov@intel.com, ivecera@redhat.com,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org
Subject: Re: [RFC PATCH v2] net: add net-device TX clock source selection framework
Date: Thu, 28 Aug 2025 15:31:57 -0700 [thread overview]
Message-ID: <20250828153157.6b0a975f@kernel.org> (raw)
In-Reply-To: <20250828164345.116097-1-arkadiusz.kubalewski@intel.com>
On Thu, 28 Aug 2025 18:43:45 +0200 Arkadiusz Kubalewski wrote:
> Add support for user-space control over network device transmit clock
> sources through a new extended netdevice netlink interface.
> A network device may support multiple TX clock sources (OCXO, SyncE
> reference, external reference clocks) which are critical for
> time-sensitive networking applications and synchronization protocols.
how does this relate to the dpll pin in rtnetlink then?
next prev parent reply other threads:[~2025-08-28 22:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 16:43 [Intel-wired-lan] [RFC PATCH v2] net: add net-device TX clock source selection framework Arkadiusz Kubalewski
2025-08-28 16:43 ` Arkadiusz Kubalewski
2025-08-28 16:57 ` [Intel-wired-lan] " Mina Almasry
2025-08-28 16:57 ` Mina Almasry
2025-08-29 7:05 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2025-08-29 7:05 ` Kubalewski, Arkadiusz
2025-09-16 12:04 ` [Intel-wired-lan] " Jiri Pirko
2025-09-16 12:04 ` Jiri Pirko
2025-08-28 17:06 ` [Intel-wired-lan] " Andrew Lunn
2025-08-28 17:06 ` Andrew Lunn
2025-08-29 7:05 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2025-08-29 7:05 ` Kubalewski, Arkadiusz
2025-08-28 22:31 ` Jakub Kicinski [this message]
2025-08-28 22:31 ` Jakub Kicinski
2025-08-29 7:49 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2025-08-29 7:49 ` Kubalewski, Arkadiusz
2025-08-30 0:34 ` [Intel-wired-lan] " Jakub Kicinski
2025-08-30 0:34 ` Jakub Kicinski
2025-09-05 11:14 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2025-09-05 11:14 ` Kubalewski, Arkadiusz
2025-09-05 14:09 ` [Intel-wired-lan] " Ivan Vecera
2025-09-05 14:09 ` Ivan Vecera
2025-09-16 12:13 ` [Intel-wired-lan] " Jiri Pirko
2025-09-16 12:13 ` Jiri Pirko
2025-09-05 23:03 ` [Intel-wired-lan] " Jakub Kicinski
2025-09-05 23:03 ` Jakub Kicinski
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=20250828153157.6b0a975f@kernel.org \
--to=kuba@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=asml.silence@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuniyu@google.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=sdf@fomichev.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.