From: Ido Schimmel <idosch@idosch.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v2 net-next 2/6] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status
Date: Sun, 7 Nov 2021 15:44:52 +0200 [thread overview]
Message-ID: <YYfYVA9j6Dk2rkDD@shredder> (raw)
In-Reply-To: <20211105205331.2024623-3-maciej.machnikowski@intel.com>
On Fri, Nov 05, 2021 at 09:53:27PM +0100, Maciej Machnikowski wrote:
> +/* SyncE section */
> +
> +enum if_eec_state {
> + IF_EEC_STATE_INVALID = 0, /* state is not valid */
> + IF_EEC_STATE_FREERUN, /* clock is free-running */
> + IF_EEC_STATE_LOCKED, /* clock is locked to the reference,
> + * but the holdover memory is not valid
> + */
> + IF_EEC_STATE_LOCKED_HO_ACQ, /* clock is locked to the reference
> + * and holdover memory is valid
> + */
> + IF_EEC_STATE_HOLDOVER, /* clock is in holdover mode */
> +};
> +
> +#define EEC_SRC_PORT (1 << 0) /* recovered clock from the port is
> + * currently the source for the EEC
> + */
Where is this used?
Note that the merge window is open and that net-next is closed:
http://vger.kernel.org/~davem/net-next.html
> +
> +struct if_eec_state_msg {
> + __u32 ifindex;
> +};
> +
> +enum {
> + IFLA_EEC_UNSPEC,
> + IFLA_EEC_STATE,
> + IFLA_EEC_SRC_IDX,
> + __IFLA_EEC_MAX,
> +};
> +
> +#define IFLA_EEC_MAX (__IFLA_EEC_MAX - 1)
WARNING: multiple messages have this Message-ID (diff)
From: Ido Schimmel <idosch@idosch.org>
To: Maciej Machnikowski <maciej.machnikowski@intel.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
richardcochran@gmail.com, abyagowi@fb.com,
anthony.l.nguyen@intel.com, davem@davemloft.net, kuba@kernel.org,
linux-kselftest@vger.kernel.org, mkubecek@suse.cz,
saeed@kernel.org, michael.chan@broadcom.com
Subject: Re: [PATCH v2 net-next 2/6] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status
Date: Sun, 7 Nov 2021 15:44:52 +0200 [thread overview]
Message-ID: <YYfYVA9j6Dk2rkDD@shredder> (raw)
In-Reply-To: <20211105205331.2024623-3-maciej.machnikowski@intel.com>
On Fri, Nov 05, 2021 at 09:53:27PM +0100, Maciej Machnikowski wrote:
> +/* SyncE section */
> +
> +enum if_eec_state {
> + IF_EEC_STATE_INVALID = 0, /* state is not valid */
> + IF_EEC_STATE_FREERUN, /* clock is free-running */
> + IF_EEC_STATE_LOCKED, /* clock is locked to the reference,
> + * but the holdover memory is not valid
> + */
> + IF_EEC_STATE_LOCKED_HO_ACQ, /* clock is locked to the reference
> + * and holdover memory is valid
> + */
> + IF_EEC_STATE_HOLDOVER, /* clock is in holdover mode */
> +};
> +
> +#define EEC_SRC_PORT (1 << 0) /* recovered clock from the port is
> + * currently the source for the EEC
> + */
Where is this used?
Note that the merge window is open and that net-next is closed:
http://vger.kernel.org/~davem/net-next.html
> +
> +struct if_eec_state_msg {
> + __u32 ifindex;
> +};
> +
> +enum {
> + IFLA_EEC_UNSPEC,
> + IFLA_EEC_STATE,
> + IFLA_EEC_SRC_IDX,
> + __IFLA_EEC_MAX,
> +};
> +
> +#define IFLA_EEC_MAX (__IFLA_EEC_MAX - 1)
next prev parent reply other threads:[~2021-11-07 13:44 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 20:53 [Intel-wired-lan] [PATCH v2 net-next 0/6] Add RTNL interface for SyncE Maciej Machnikowski
2021-11-05 20:53 ` Maciej Machnikowski
2021-11-05 20:53 ` [Intel-wired-lan] [PATCH v2 net-next 1/6] ice: add support detecting features based on netlist Maciej Machnikowski
2021-11-05 20:53 ` Maciej Machnikowski
2021-11-05 20:53 ` [Intel-wired-lan] [PATCH v2 net-next 2/6] rtnetlink: Add new RTM_GETEECSTATE message to get SyncE status Maciej Machnikowski
2021-11-05 20:53 ` Maciej Machnikowski
2021-11-07 13:44 ` Ido Schimmel [this message]
2021-11-07 13:44 ` Ido Schimmel
2021-11-05 20:53 ` [Intel-wired-lan] [PATCH v2 net-next 3/6] ice: add support for reading SyncE DPLL state Maciej Machnikowski
2021-11-05 20:53 ` Maciej Machnikowski
2021-11-05 20:53 ` [Intel-wired-lan] [PATCH v2 net-next 4/6] rtnetlink: Add support for SyncE recovered clock configuration Maciej Machnikowski
2021-11-05 20:53 ` Maciej Machnikowski
2021-11-05 20:53 ` [Intel-wired-lan] [PATCH v2 net-next 5/6] ice: add support for SyncE recovered clocks Maciej Machnikowski
2021-11-05 20:53 ` Maciej Machnikowski
2021-11-05 20:53 ` [Intel-wired-lan] [PATCH v2 net-next 6/6] docs: net: Add description of SyncE interfaces Maciej Machnikowski
2021-11-05 20:53 ` Maciej Machnikowski
2021-11-07 14:08 ` [Intel-wired-lan] " Ido Schimmel
2021-11-07 14:08 ` Ido Schimmel
2021-11-08 8:35 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-08 8:35 ` Machnikowski, Maciej
2021-11-08 16:29 ` [Intel-wired-lan] " Ido Schimmel
2021-11-08 16:29 ` Ido Schimmel
2021-11-08 17:03 ` [Intel-wired-lan] " Jakub Kicinski
2021-11-08 17:03 ` Jakub Kicinski
2021-11-09 10:50 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-09 10:50 ` Machnikowski, Maciej
2021-11-09 10:32 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-09 10:32 ` Machnikowski, Maciej
2021-11-08 18:00 ` [Intel-wired-lan] " Petr Machata
2021-11-08 18:00 ` Petr Machata
2021-11-09 10:43 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-09 10:43 ` Machnikowski, Maciej
2021-11-09 14:52 ` [Intel-wired-lan] " Petr Machata
2021-11-09 14:52 ` Petr Machata
2021-11-09 18:19 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-09 18:19 ` Machnikowski, Maciej
2021-11-10 10:27 ` [Intel-wired-lan] " Petr Machata
2021-11-10 10:27 ` Petr Machata
2021-11-10 11:19 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-10 11:19 ` Machnikowski, Maciej
2021-11-10 15:15 ` [Intel-wired-lan] " Petr Machata
2021-11-10 15:15 ` Petr Machata
2021-11-10 15:50 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-10 15:50 ` Machnikowski, Maciej
2021-11-10 21:05 ` [Intel-wired-lan] " Petr Machata
2021-11-10 21:05 ` Petr Machata
2021-11-15 10:12 ` [Intel-wired-lan] " Machnikowski, Maciej
2021-11-15 10:12 ` Machnikowski, Maciej
2021-11-15 21:42 ` [Intel-wired-lan] " Jakub Kicinski
2021-11-15 21:42 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YYfYVA9j6Dk2rkDD@shredder \
--to=idosch@idosch.org \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.