From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Date: Fri, 3 Sep 2021 09:18:57 -0700 Subject: [Intel-wired-lan] [PATCH net-next 1/2] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status In-Reply-To: <20210903151436.529478-2-maciej.machnikowski@intel.com> References: <20210903151436.529478-1-maciej.machnikowski@intel.com> <20210903151436.529478-2-maciej.machnikowski@intel.com> Message-ID: <20210903091857.70bdf57a@hermes.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: On Fri, 3 Sep 2021 17:14:35 +0200 Maciej Machnikowski wrote: > This patch series introduces basic interface for reading the Ethernet > Equipment Clock (EEC) state on a SyncE capable device. This state gives > information about the state of EEC. This interface is required to > implement Synchronization Status Messaging on upper layers. > > Initial implementation returns SyncE EEC state and flags attributes. > The only flag currently implemented is the EEC_SRC_PORT. When it's set > the EEC is synchronized to the recovered clock recovered from the > current port. > > SyncE EEC state read needs to be implemented as a ndo_get_eec_state > function. > > Signed-off-by: Maciej Machnikowski Is there a simpler way to do this? Seems like you are adding a lot for a use case specific to a small class of devices. For example adding a new network device operation adds small amount of bloat to every other network device in the kernel.