From: Jacob Keller <jacob.e.keller@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>,
"Przemek Kitszel" <przemyslaw.kitszel@intel.com>,
"Saeed Mahameed" <saeedm@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Tariq Toukan" <tariqt@nvidia.com>,
"Bryan Whitehead" <bryan.whitehead@microchip.com>,
UNGLinuxDriver@microchip.com,
"Horatiu Vultur" <horatiu.vultur@microchip.com>,
"Paul Barker" <paul.barker.ct@bp.renesas.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Richard Cochran" <richardcochran@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Andrei Botila" <andrei.botila@oss.nxp.com>,
"Claudiu Manoil" <claudiu.manoil@nxp.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] net: ptp: introduce .supported_extts_flags to ptp_clock_info
Date: Mon, 14 Apr 2025 13:00:20 -0700 [thread overview]
Message-ID: <53674f44-abee-4208-bc32-cb0eacf33a2d@intel.com> (raw)
In-Reply-To: <20250411182044.0ee40963@kernel.org>
On 4/11/2025 6:20 PM, Jakub Kicinski wrote:
> Sorry for the late nit but the conversion is pretty inconsistent..
>
> On Tue, 08 Apr 2025 13:55:14 -0700 Jacob Keller wrote:
8<--
>> @@ -1378,6 +1368,8 @@ void igb_ptp_init(struct igb_adapter *adapter)
>> adapter->ptp_caps.n_ext_ts = IGB_N_EXTTS;
>> adapter->ptp_caps.n_per_out = IGB_N_PEROUT;
>> adapter->ptp_caps.n_pins = IGB_N_SDP;
>> + adapter->ptp_caps.supported_extts_flags = PTP_EXTTS_EDGES |
>> + PTP_STRICT_FLAGS;
>
> sometimes you both drop the enabled and combine the edges
>
>> adapter->ptp_caps.pps = 1;
>> adapter->ptp_caps.pin_config = adapter->sdp_config;
>> adapter->ptp_caps.adjfine = igb_ptp_adjfine_82580;
>
> No preference which version you pick but shouldn't we go with one?
> Or is this on purpose to show we have no preference?
It wasn't on purpose. Honestly not sure how they ended up different. I
think the right thing is:
a) drop the ENABLE since we always accept that regardless of whether its
in supported_extts_flags
b) don't use PTP_EXTTS_EDGES in the supported flags, since its easier to
see which specific flags are supported if you aren't having to remember
that the macro means multiple flags.
I'll update in a v2 to be consistent.
Thanks,
Jake
next prev parent reply other threads:[~2025-04-14 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 20:55 [PATCH net-next 0/2] net: ptp: driver opt-in for supported PTP ioctl flags Jacob Keller
2025-04-08 20:55 ` [PATCH net-next 1/2] net: ptp: introduce .supported_extts_flags to ptp_clock_info Jacob Keller
2025-04-12 1:20 ` Jakub Kicinski
2025-04-14 20:00 ` Jacob Keller [this message]
2025-04-08 20:55 ` [PATCH net-next 2/2] net: ptp: introduce .supported_perout_flags " Jacob Keller
2025-04-10 10:07 ` [PATCH net-next 0/2] net: ptp: driver opt-in for supported PTP ioctl flags Vadim Fedorenko
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=53674f44-abee-4208-bc32-cb0eacf33a2d@intel.com \
--to=jacob.e.keller@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrei.botila@oss.nxp.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=bryan.whitehead@microchip.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=paul.barker.ct@bp.renesas.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).