Thread (25 messages) flat view 25 messages, 4 authors, 2021-11-15

Re: [PATCH v2 net-next 6/6] docs: net: Add description of SyncE interfaces

From: Jakub Kicinski <kuba@kernel.org>
Date: 2021-11-15 21:45:01
Also in: intel-wired-lan, linux-kselftest

On Mon, 15 Nov 2021 10:12:25 +0000 Machnikowski, Maciej wrote:
quoted
quoted
Netdev owns the PHY, so it needs to enable/disable clock from a given
port/lane - other than that it's EECs task. Technically - those subsystems
are separate.  
So why is the UAPI conflating the two?  
Because EEC can be a separate external device, but also can be integrated
inside the netdev. In the second case it makes more sense to just return
the state from a netdev 
I mentioned that we are in a need of such API to Vadim who, among other
things, works on the OCP Timecard. He indicated interest in developing
the separate netlink interface for "DPLLs" (the timecard is just an
atomic clock + GPS, no netdev to hang from). Let's wait for Vadim's work
to materialize and build on top of that.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help