From: Jacob Keller <jacob.e.keller@intel.com>
To: James Clark <jjc@jclark.com>, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Richard Cochran <richardcochran@gmail.com>,
Kory Maincent <kory.maincent@bootlin.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Chintan Vankar <c-vankar@ti.com>, Aksh Garg <a-garg7@ti.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: ethernet: ti: am65-cpts: fix support for PTP_EXTTS_REQUEST2 ioctl
Date: Thu, 22 Oct 2026 11:03:37 -0700 [thread overview]
Message-ID: <988c3316-82a6-4d81-aaef-b13e9e92fa01@intel.com> (raw)
In-Reply-To: <20261022035226.1388675-1-jjc@jclark.com>
On 10/21/2026 8:52 PM, James Clark wrote:
> On Thu, 22 Oct 2026 03:37:13 +0000, netdev-bot+sashiko@kernel.org wrote:
>> Before this patch, supported_extts_flags was 0 for am65-cpts. A v1 request
>> with PTP_ENABLE_FEATURE | PTP_FALLING_EDGE, or with both edges set, was
>> accepted and reached am65_cpts_extts_enable(), which ignores the flags.
>>
>> Now the mask has PTP_STRICT_FLAGS but not PTP_FALLING_EDGE, so those same
>> v1 requests return -EOPNOTSUPP before ops->enable() is ever called.
> [...]
>> However, the commit message says:
>>
>> Only the PTP_EXTTS_REQUEST ioctl still works.
>>
>> This suggests v1 behaviour does not change. The patch has a Fixes: tag and
>> is likely to go to stable. Could the commit message say that v1 requests
>> carrying PTP_FALLING_EDGE are now rejected as well?
>
> The sentence that Sashiko quotes is part of the paragraph describing the
> state before this patch, so it has no such implication.
>
> With this patch, PTP_EXTTS_REQUEST rejects a request for PTP_FALLING_EDGE
> instead of accepting it and reporting rising edges. This is part of the
> purpose of 7c571ac57d9d. The equivalent bcm-phy-ptp fix, 3200fdd4021d
> ("broadcom: fix support for PTP_EXTTS_REQUEST2 ioctl"), made the same
> change without mentioning it.
>
> I don't plan to do a v2 for this.
Yep, I agree with this assessment.
Acked-by: Jacob Keller <jacob.e.keller@intel.com>
prev parent reply other threads:[~2026-10-22 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 0:35 James Clark
2026-10-20 8:23 ` James Clark
2026-10-22 3:37 ` netdev-bot+sashiko
2026-10-22 3:52 ` James Clark
2026-10-22 18:03 ` Jacob Keller [this message]
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=988c3316-82a6-4d81-aaef-b13e9e92fa01@intel.com \
--to=jacob.e.keller@intel.com \
--cc=a-garg7@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=c-vankar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=jjc@jclark.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=s-vadapalli@ti.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
all inboxes | Powered by JetHome®