On Thu, 4 Nov 2021 09:12:31 +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 can recover synchronization > +from the synchronization inputs - either traffic interfaces or external > +frequency sources. > +The EEC can synchronize its frequency (syntonize) to any of those sources. > +It is also able to select a synchronization source through priority tables > +and synchronization status messaging. It also provides necessary > +filtering and holdover capabilities. > + > +The following interface can be applicable to diffferent packet network types > +following ITU-T G.8261/G.8262 recommendations. Can we get a diagram in here in terms of how the port feeds its recovered Rx freq into EEC and that feeds freq of Tx on other ports? I'm still struggling to understand your reasoning around not making EEC its own object. "We can do this later" seems like trading relatively little effort now for extra work for driver and application developers for ever. Also patch 3 still has a kdoc warning.
