[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250828153157.6b0a975f@kernel.org>
Date: Thu, 28 Aug 2025 15:31:57 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
Cc: anthony.l.nguyen@...el.com, przemyslaw.kitszel@...el.com,
andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, horms@...nel.org, sdf@...ichev.me,
almasrymina@...gle.com, asml.silence@...il.com, leitao@...ian.org,
kuniyu@...gle.com, jiri@...nulli.us, aleksandr.loktionov@...el.com,
ivecera@...hat.com, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org
Subject: Re: [RFC PATCH v2] net: add net-device TX clock source selection
framework
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?
Powered by blists - more mailing lists