[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6b8281b3-a438-4b3e-a8e7-d5043416d421@redhat.com>
Date: Wed, 30 Jul 2025 16:45:18 +0200
From: Ivan Vecera <ivecera@...hat.com>
To: Jiri Pirko <jiri@...nulli.us>,
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,
kuba@...nel.org, pabeni@...hat.com, horms@...nel.org, sdf@...ichev.me,
almasrymina@...gle.com, asml.silence@...il.com, leitao@...ian.org,
kuniyu@...gle.com, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org
Subject: Re: [Intel-wired-lan] [RFC PATCH] net: add net-device TX clock source
selection framework
On 30. 07. 25 2:26 odp., Jiri Pirko wrote:
> Tue, Jul 29, 2025 at 12:45:28PM +0200, arkadiusz.kubalewski@...el.com wrote:
>
> [...]
>
>> User interface:
>> - Read /sys/class/net/<device>/tx_clk/<clock_name> to get status (0/1)
>> - Write "1" to switch to that clock source
>
> I wonder, if someone invented a time machine and sent me back to 2005...
>
> [...]
>
+1
why do we have netlink based interfaces for configuration...?
Wouldn't be better to implement such thing to be configurable via ip
link or ethtool??
E.g.
ip link set eth0 tx-clk <clock_name>
--or--
ethtool --set-tx-clk/--show-tx-clk eth0 <clock_name>
Ivan
Powered by blists - more mailing lists