Thread (40 messages) flat view 40 messages, 7 authors, 2021-09-22

Re: [PATCH net-next 1/2] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status

From: Richard Cochran <richardcochran@gmail.com>
Date: 2021-09-09 02:09:23
Also in: intel-wired-lan, linux-kselftest

On Thu, Sep 09, 2021 at 12:59:27AM +0200, Andrew Lunn wrote:
On Wed, Sep 08, 2021 at 03:20:27PM -0700, Jakub Kicinski wrote:
quoted
On Wed, 8 Sep 2021 21:34:37 +0200 Andrew Lunn wrote:
quoted
Since we are talking about clocks and dividers, and multiplexors,
should all this be using the common clock framework, which already
supports most of this? Do we actually need something new?
Does the common clock framework expose any user space API?
Ah, good point. No, i don't think it does, apart from debugfs, which
is not really a user space API, and it contains read only descriptions
of the clock tree, current status, mux settings, dividers etc.
Wouldn't it make sense to develop some kind of user land API to
manipulate the common clock framework at run time?

Just dreaming...

Richard
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help