>On 15.12.2021 12:14, Kubalewski, Arkadiusz wrote: >>> -----Original Message----- >>> From: Machnikowski, Maciej <maciej.machnikowski@xxxxxxxxx> >>> Sent: poniedziałek, 13 grudnia 2021 09:54 >>> To: Jakub Kicinski <kuba@xxxxxxxxxx> >>> Cc: netdev@xxxxxxxxxxxxxxx; intel-wired-lan@xxxxxxxxxxxxxxxx; Kubalewski, Arkadiusz <arkadiusz.kubalewski@xxxxxxxxx>; richardcochran@xxxxxxxxx; Byagowi, Ahmad <abyagowi@xxxxxx>; Nguyen, Anthony L <anthony.l.nguyen@xxxxxxxxx>; davem@xxxxxxxxxxxxx; linux-kselftest@xxxxxxxxxxxxxxx; idosch@xxxxxxxxxx; mkubecek@xxxxxxx; saeed@xxxxxxxxxx; michael.chan@xxxxxxxxxxxx; petrm@xxxxxxxxxx; Vadim Fedorenko <vfedorenko@xxxxxxxx> >>> Subject: RE: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks >>> >>>> -----Original Message----- >>>> From: Jakub Kicinski <kuba@xxxxxxxxxx> >>>> Sent: Friday, December 10, 2021 5:17 PM >>>> To: Machnikowski, Maciej <maciej.machnikowski@xxxxxxxxx> >>>> Cc: netdev@xxxxxxxxxxxxxxx; intel-wired-lan@xxxxxxxxxxxxxxxx; >>>> Kubalewski, Arkadiusz <arkadiusz.kubalewski@xxxxxxxxx>; >>>> richardcochran@xxxxxxxxx; Byagowi, Ahmad <abyagowi@xxxxxx>; Nguyen, >>>> Anthony L <anthony.l.nguyen@xxxxxxxxx>; davem@xxxxxxxxxxxxx; linux- >>>> kselftest@xxxxxxxxxxxxxxx; idosch@xxxxxxxxxx; mkubecek@xxxxxxx; >>>> saeed@xxxxxxxxxx; michael.chan@xxxxxxxxxxxx; petrm@xxxxxxxxxx; Vadim >>>> Fedorenko <vfedorenko@xxxxxxxx> >>>> Subject: Re: [PATCH v5 net-next 0/4] Add ethtool interface for RClocks >>>> >>>> On Fri, 10 Dec 2021 14:45:46 +0100 Maciej Machnikowski wrote: >>>>> Synchronous Ethernet networks use a physical layer clock to >>>>> syntonize the frequency across different network elements. >>>>> >>>>> Basic SyncE node defined in the ITU-T G.8264 consist of an Ethernet >>>>> Equipment Clock (EEC) and have the ability to synchronize to >>>>> reference frequency sources. >>>>> >>>>> This patch series is a prerequisite for EEC object and adds ability >>>>> to enable recovered clocks in the physical layer of the netdev object. >>>>> Recovered clocks can be used as one of the reference signal by the EEC. >>>>> >>>>> Further work is required to add the DPLL subsystem, link it to the >>>>> netdev object and create API to read the EEC DPLL state. >>>> >>>> You missed CCing Vadim. I guess Ccing the right people may be right up >>>> there with naming things as the hardest things in SW development.. >>>> >>>> Anyway, Vadim - do you have an ETA on the first chunk of the PLL work? >>> >>> Sounds about right :) thanks for adding Vadim! >>> >> >> Good day Vadim, >> >> Can we help on the new PLL interfaces? >> I can start some works related to that, although would need a guidance >> from the expert. >> Where to place it? >> What in-kernel interfaces to use? >> Any other high level tips that could be useful? >> Or if you already started some work, could you please share some >> information? >> >Hi! > >I'm going to publish RFC till the end of the week and we will be able to >continue discussion via this mailing list. I think that netlink is a good >option for in-kernel interface and is easy to implement. > Oh, that sounds great! Thank you!
