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-10 14:14:30
Also in: intel-wired-lan, linux-kselftest

On Thu, Sep 09, 2021 at 08:18:10AM +0000, Machnikowski, Maciej wrote:
Controlling the clock that actually drives any components (PHY/MAC) in
runtime can be a good way to brick the part.
I didn't say that.
I feel that, while the reuse 
of structures may be a good idea, the userspace API for clocks is not. 
They are usually set up once at the board init level and stay like that "forever".

The outputs we need to control are only a subset of all of them and they
rather fall in the PTP pins level of details, rather than clock ones.
clk-gate.c
clk-mux.c

Making that available for user space to twiddle is a better way that
tacking on to the PTP stuff.

You can model your device as having a multiplexer in front of it.

Thanks,
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