Netdev List
 help / color / mirror / Atom feed
From: "Nazle Asmade, Muhammad Nazim Amirul" <muhammad.nazim.amirul.nazle.asmade@altera.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "G Thomas, Rohan" <rohan.g.thomas@altera.com>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"rmk+kernel@armlinux.org.uk" <rmk+kernel@armlinux.org.uk>,
	"richardcochran@gmail.com" <richardcochran@gmail.com>
Subject: Re: [PATCH net] net: stmmac: Fix E2E delay mechanism
Date: Mon, 27 Jul 2026 07:59:03 +0000	[thread overview]
Message-ID: <04c444c7-606d-44bc-a2f7-b01dcdb53210@altera.com> (raw)
In-Reply-To: <1af74c3b-f717-482c-9715-7f91f14d86aa@bootlin.com>

On 27/7/2026 3:52 pm, Maxime Chevallier wrote:
> 
> 
> On 7/27/26 04:25, muhammad.nazim.amirul.nazle.asmade@altera.com wrote:
>> From: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
>>
>> For E2E delay mechanism, "received DELAY_REQ without timestamp" error
>> messages show up for dwmac v3.70+ and dwxgmac IPs.
>>
>> This issue affects socfpga platforms, Agilex7 (dwmac 3.70) and
>> Agilex5 (dwxgmac). According to the databook, to enable timestamping
>> for all events, the SNAPTYPSEL bits in the MAC_Timestamp_Control
>> register must be set to 2'b01, and the TSEVNTENA bit must be cleared
>> to 0'b0.
>>
>> Commit 3cb958027cb8 ("net: stmmac: Fix E2E delay mechanism") already
>> addresses this problem for all dwmacs above version v4.10. However,
>> same holds true for v3.70 and above, as well as for dwxgmac. Updates
>> the check accordingly.
>>
>> Fixes: 14f347334bf2 ("net: stmmac: Correctly take timestamp for PTPv2")
>> Fixes: f2fb6b6275eb ("net: stmmac: enable timestamp snapshot for required PTP packets in dwmac v5.10a")
>> Fixes: 3cb958027cb8 ("net: stmmac: Fix E2E delay mechanism")
>> Signed-off-by: Rohan G Thomas <rohan.g.thomas@altera.com>
>> Signed-off-by: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
> 
> Given the original discussions that took place, it seems that this is
> the correct fix. As Russell suggest, we need some timestamping selftest
> to make it easy to find regressions with this kind of patches, but
> I've experimented with stmmac selftests over the weekend and they are
> in a sorry state right now...
> 
> Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>

Thanks Maxime!>
> Maxime
> 
> 


  reply	other threads:[~2026-07-27  7:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260727152949eucas1p2a8679cd740d0bccf89db7d0af8904225@eucas1p2.samsung.com>
2026-07-27  2:25 ` [PATCH net] net: stmmac: Fix E2E delay mechanism muhammad.nazim.amirul.nazle.asmade
2026-07-27  7:52   ` Maxime Chevallier
2026-07-27  7:59     ` Nazle Asmade, Muhammad Nazim Amirul [this message]
2026-07-27 15:29   ` Jakub Raczynski
2026-07-28  1:21     ` Nazle Asmade, Muhammad Nazim Amirul
2021-10-20  7:04 Kurt Kanzenbach
2021-10-20 13:50 ` patchwork-bot+netdevbpf
2021-10-21  6:44 ` Wong Vee Khee
2021-10-21  6:55   ` Kurt Kanzenbach

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=04c444c7-606d-44bc-a2f7-b01dcdb53210@altera.com \
    --to=muhammad.nazim.amirul.nazle.asmade@altera.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rohan.g.thomas@altera.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