From: Simon Horman <horms@kernel.org>
To: Przemyslaw Korba <przemyslaw.korba@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
Jacob Keller <jacob.e.keller@intel.com>
Subject: Re: [PATCH iwl-next] i40e: PTP: set supported flags in ptp_clock_info
Date: Tue, 10 Mar 2026 18:24:58 +0000 [thread overview]
Message-ID: <20260310182458.GQ461701@kernel.org> (raw)
In-Reply-To: <20260309141220.343224-1-przemyslaw.korba@intel.com>
+ Jacob
On Mon, Mar 09, 2026 at 03:11:51PM +0100, Przemyslaw Korba wrote:
> Since upstream commit d9f3e9ecc456 ("net: ptp: introduce
> .supported_perout_flags to ptp_clock_info") and commit 7c571ac57d9d ("net:
> ptp: introduce .supported_extts_flags to ptp_clock_info"), kernel core now
> requires that the driver set the .supported_perout_flags and
> .supported_extts_flags fields in PTP clock info. Otherwise, the additional
> flags will be rejected by the kernel automatically.
>
> i40e does not support perout flags, so reject any request with perout
> flags.
>
> Signed-off-by: Przemyslaw Korba <przemyslaw.korba@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e_ptp.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/i40e/i40e_ptp.c b/drivers/net/ethernet/intel/i40e/i40e_ptp.c
> index 7bcea7d9720f..8d7958692235 100644
> --- a/drivers/net/ethernet/intel/i40e/i40e_ptp.c
> +++ b/drivers/net/ethernet/intel/i40e/i40e_ptp.c
> @@ -601,10 +601,18 @@ static int i40e_ptp_feature_enable(struct ptp_clock_info *ptp,
> /* TODO: Implement flags handling for EXTTS and PEROUT */
> switch (rq->type) {
> case PTP_CLK_REQ_EXTTS:
> + if (rq->extts.flags & ~(PTP_ENABLE_FEATURE |
> + PTP_RISING_EDGE |
> + PTP_FALLING_EDGE |
> + PTP_STRICT_FLAGS))
> + return -EOPNOTSUPP;
> +
> func = PTP_PF_EXTTS;
> chan = rq->extts.index;
> break;
> case PTP_CLK_REQ_PEROUT:
> + if (rq->perout.flags)
> + return -EOPNOTSUPP;
> func = PTP_PF_PEROUT;
> chan = rq->perout.index;
> break;
I am a little confused.
My understanding of the cited patches is that they add checking
of flags to the code. So code like the above isn't needed in drivers.
> @@ -1340,7 +1348,9 @@ static int i40e_init_pin_config(struct i40e_pf *pf)
> pf->ptp_caps.n_ext_ts = 2;
> pf->ptp_caps.pps = 1;
> pf->ptp_caps.n_per_out = 2;
> -
> + pf->ptp_caps.supported_extts_flags = PTP_RISING_EDGE |
> + PTP_FALLING_EDGE |
> + PTP_STRICT_FLAGS;
> pf->ptp_caps.pin_config = kzalloc_objs(*pf->ptp_caps.pin_config,
> pf->ptp_caps.n_pins);
> if (!pf->ptp_caps.pin_config)
>
> base-commit: d5fbc991435eac7a1ead7cd2ddb5a743528718bb
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-03-10 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 14:11 [PATCH iwl-next] i40e: PTP: set supported flags in ptp_clock_info Przemyslaw Korba
2026-03-09 16:34 ` [Intel-wired-lan] " Paul Menzel
2026-03-11 12:42 ` Korba, Przemyslaw
2026-03-10 18:24 ` Simon Horman [this message]
2026-03-11 12:42 ` Korba, Przemyslaw
2026-03-13 13:34 ` Simon Horman
2026-03-13 13:47 ` Korba, Przemyslaw
2026-03-26 0:15 ` Jacob Keller
2026-03-11 8:01 ` [Intel-wired-lan] " Dawid Osuchowski
2026-03-11 12:45 ` Korba, Przemyslaw
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=20260310182458.GQ461701@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=przemyslaw.korba@intel.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