[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67365b739f70c_3379ce29452@willemb.c.googlers.com.notmuch>
Date: Thu, 14 Nov 2024 15:20:03 -0500
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Milena Olech <milena.olech@...el.com>,
intel-wired-lan@...ts.osuosl.org
Cc: netdev@...r.kernel.org,
anthony.l.nguyen@...el.com,
przemyslaw.kitszel@...el.com,
Milena Olech <milena.olech@...el.com>,
Alexander Lobakin <aleksander.lobakin@...el.com>
Subject: Re: [PATCH iwl-net 04/10] idpf: negotiate PTP capabilies and get PTP
clock
Milena Olech wrote:
> PTP capabilities are negotiated using virtchnl command. Add get
> capabilities function, direct access to read the PTP clock time and
> direct access to read the cross timestamp - system time and PTP clock
> time. Set initial PTP capabilities exposed to the stack.
>
> Reviewed-by: Alexander Lobakin <aleksander.lobakin@...el.com>
> Signed-off-by: Milena Olech <milena.olech@...el.com>
Tested-by: Willem de Bruijn <willemb@...gle.com>
> /**
> * struct idpf_ptp - PTP parameters
> * @info: structure defining PTP hardware capabilities
> * @clock: pointer to registered PTP clock device
> * @adapter: back pointer to the adapter
> + * @cmd: HW specific command masks
> + * @dev_clk_regs: the set of registers to access the device clock
> + * @caps: PTP capabilities negotiated with the Control Plane
> + * @get_dev_clk_time_access: access type for getting the device clock time
> + * @get_cross_tstamp_access: access type for the cross timestamping
> */
> struct idpf_ptp {
> struct ptp_clock_info info;
> struct ptp_clock *clock;
> struct idpf_adapter *adapter;
> + struct idpf_ptp_cmd cmd;
> + struct idpf_ptp_dev_clk_regs dev_clk_regs;
> + u32 caps;
> + enum idpf_ptp_access get_dev_clk_time_access:16;
> + enum idpf_ptp_access get_cross_tstamp_access:16;
why are these 16 bit fields, when they are only ternary options?
Powered by blists - more mailing lists