-----Original Message----- From: Aya Levin <a...@nvidia.com> Sent: Wednesday, June 22, 2022 3:42 PM > >On 6/21/2022 6:25 PM, Kubalewski, Arkadiusz wrote: >> -----Original Message----- >> From: Aya Levin <a...@nvidia.com> >> Sent: Sunday, June 19, 2022 6:35 PM >>> >>> Hi, >>> >>> Please elaborate regarding kernel API. I understood from the submission >>> that you plan to start off with some vendor specific sysfs declared in >>> the config file. >>> But I believe this is not the final goal, correct? >>> Do you have kernel patches for review? >>> >>> Thanks, >>> Aya >> >> Hi, >> >> SyncE standard needs two abilities from the Network Interface Card: >> - check the status of frequency loop, if it is locked/holdover/etc >> - select one of the PHY ports as a signal source. >What about set status - when SyncE state machine needs to move to holdover?
Sorry, I missed this question. Yes, definitely we need it both, ability to enable and disable clock recovery on a net-device PHY port. Thanks, Arkadiusz >> >> Currently in sync4l both of those abilities are provided in form of shell >> commands, so it can be used with any user-space tool. >> >> For the future, the plan is to have generic netlink based interface/subsystem >> in the kernel. Designed for all devices capable of syntonizing its clock to >> an >> external source (I am working on it right now), probably also equipped with >> generic sysfs for manual control. >> >> Thank you, >> Arkadiusz > _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
