[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210831190235.00fa780b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Tue, 31 Aug 2021 19:02:35 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Machnikowski, Maciej" <maciej.machnikowski@...el.com>
Cc: Richard Cochran <richardcochran@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"abyagowi@...com" <abyagowi@...com>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
"bsd@...com" <bsd@...com>,
Jonathan Lemon <jonathan.lemon@...il.com>
Subject: Re: [RFC v2 net-next 1/2] rtnetlink: Add new RTM_GETSYNCESTATE
message to get SyncE status
On Tue, 31 Aug 2021 22:09:18 +0000 Machnikowski, Maciej wrote:
> OK I can strip down the RTNL EEC state interface to only report
> the state without any extras, like pin. Next step would be to add
> the control over recovered clock also to the netdev subsystem.
>
> The EEC state read is needed for recovered/source clock validation
> and that's why I think it belongs to the RTNL part as it gates the QL
> for each port.
If you mean just reporting state and have a syncE on/off without any
option for other sources that's fine by me.
Powered by blists - more mailing lists