On Mon, 6 Sep 2021 19:01:54 +0000 Machnikowski, Maciej wrote: > > > Hmm. Main reason for netlink is that linuxptp already supports it, > > > and it was suggested by Richard. > > > Having an NDO would also make it easier to add a SyncE-related > > > files to the sysfs for easier operation (following the ideas from the ptp > > > pins subsystem). > > > But I'm open for suggestions. > > > > I think linuxptp will need support for ethtool netlink sockets sooner > > rather than later. Moving this to ethtool makes sense to me since it's > > very much a Ethernet-oriented API at this point. > > Ethtool also makes a lot of sense, but will it be possible to still make sysfs, > and it makes sense to add it for some deployments (more on that below) It should not make much difference whether ndo or ethtool op is used. > > > This bit has a different meaning. If it's set the port in question > > > is a frequency source for the multiport device, if it's cleared - some other > > > source is used as a source. This is needed to prevent setting invalid > > > configurations in the PHY (like setting the frequency source as a Master > > > in AN) or sending invalid messages. If the port is a frequency source > > > it must always send back QL-DNU messages to prevent synchronization > > > loops. > > > > Ah! I see. Is being the "source" negotiated somehow? Don't we need to > > give the user / linuxptp to select the source based on whatever info > > it has about topology? > > The frequency source can be either pre-set statically, negotiated using > ESMC QL-levels (if working in QL-Enabled mode), or follow automatic > fallback inside the device. This flag gives feedback about the validity > of recovered clock coming from a given port and is useful when you > enable multiple recovered clocks on more than one port in > active-passive model. In that case the "driving" port may change > dynamically, so it's a good idea to have some interface to reflect that. The ESMC messages are handled by Linux or some form of firmware? I don't see how you can implement any selection policy with a read-only API. In general it would be more natural to place a "source id" at the DPLL/clock, the "source" flag seems to mark the wrong end of the relationship. If there ever are multiple consumers we won't be able to tell which "target" the "source" is referring to. Hard to judge how much of a problem that could be by looking at a small slice of the system. > That's where sysfs file be useful. When I add the implementation for > recovered clock configuration, the sysfs may be used as standalone > interface for configuring them when no dynamic change is needed. I didn't get that. Do you mean using a sysfs file to configure the parameters of the DPLL? If the DPLL has its own set of concerns we should go ahead and create explicit object / configuration channel for it. Somehow I got it into my head that you care mostly about transmitting the clock, IOW recovering it from one port and using on another but that's probably not even a strong use case for you or NICs in general :S > > > Addressed all other comments - and thanks for giving a lot of helpful > > > suggestions! > > > > Thanks, BTW I think I forgot to ask for documentation, dumping info > > about the API and context under Documentation/ would be great! > > Could you suggest where to add that? Grepping for ndo_ don't give much. > I can add a new synce.rst file if it makes sense. New networking/synce.rst file makes perfect sense to me. And perhaps link to it from driver-api/ptp.rst.
