Netdev List
 help / color / mirror / Atom feed
From: "Karumanchi, Vineeth" <vineeth@amd.com>
To: "Théo Lebrun" <theo.lebrun@bootlin.com>,
	"Vineeth Karumanchi" <vineeth.karumanchi@amd.com>,
	conor.dooley@microchip.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com
Cc: git@amd.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: macb: configure ENST registers for all queues
Date: Mon, 27 Jul 2026 11:02:16 +0530	[thread overview]
Message-ID: <3924babc-9755-46ce-97b2-bd6dfce6f6c6@amd.com> (raw)
In-Reply-To: <DK701YU8OWST.2CDXDR5SUJYJQ@bootlin.com>

Hi Théo Lebrun,

On 7/24/2026 11:36 PM, Théo Lebrun wrote:
> Hello Vineeth,
>
> On Fri Jul 24, 2026 at 6:32 AM CEST, Vineeth Karumanchi wrote:
>> The initial "tc" command was not overwriting the reset value of ENST
>> registers if only a subset of queues were configured, leading to an
>> invalid setup. To fix this, configure all queues unconditionally.
>> Unconfigured queues are zero-initialized via kcalloc(), ensuring a
>> complete and consistent configuration.
> But if a subset of queues are configured, the remaining queues don't
> have their ENST support enabled thanks to ENST_CONTROL and their ENST
> per-queue register values aren't read? Or HW is broken and reads ENST
> registers anyway? Or something else I misunderstood?
>
> What reset value of ENST regs you observed that caused you trouble?
> That info could make it into the commit message.
//
Yes, this is a confirmed hardware issue. We raised it with Cadence, and 
they have
acknowledged the problem. The reset value of the |enst_on_time_qX| 
registers is *0x0001FFFF*.

During ENST initialization, packet interleaving was observed when only a
subset of the available queues was configured, while the remaining 
queues—whose
corresponding |enst_on_time_qX| registers still contained non-zero 
values—were left disabled in |ENST_CONTROL|.


For example, in a configuration where only two of the four queues are 
enabled,
some packets from *Q0* getting transmitted during the *Q1* time slot, 
and vice versa.

Furthermore, once the hardware enters this state, it does not recover 
even after a
complete ENST queue reconfiguration is performed.

Thanks

🙏 Vineeth

>> The queue_id field in struct macb_queue_enst_config becomes redundant
>> once the array is indexed by queue id, so drop it.
>>
>> Key changes:
>> - Drop queue_id from struct macb_queue_enst_config
>> - Allocate enst_queue[] based on bp->num_queues instead of
>>    conf->num_entries
>> - Index enst_queue[] directly with the queue number
>> - Program ENST registers for all queues
>>
>> Fixes: 89934dbf169e ("net: macb: Add TAPRIO traffic scheduling support")
>> Signed-off-by: Vineeth Karumanchi <vineeth.karumanchi@amd.com>
> Thanks,
>
> --
> Théo Lebrun, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>

  reply	other threads:[~2026-07-27  5:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  4:32 [PATCH net-next 0/2] net: macb: fix ENST configuration for all queues Vineeth Karumanchi
2026-07-24  4:32 ` [PATCH net-next 1/2] net: macb: remove unused ENST Q0/Q1 time register defines Vineeth Karumanchi
2026-07-24 17:49   ` Théo Lebrun
2026-07-24 19:40   ` Nicolai Buchwitz
2026-07-24  4:32 ` [PATCH net-next 2/2] net: macb: configure ENST registers for all queues Vineeth Karumanchi
2026-07-24 18:06   ` Théo Lebrun
2026-07-27  5:32     ` Karumanchi, Vineeth [this message]
2026-07-27 12:05       ` Théo Lebrun
2026-07-27 12:52         ` Théo Lebrun
2026-07-24 19:57   ` Nicolai Buchwitz
2026-07-27 10:01     ` Karumanchi, Vineeth

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=3924babc-9755-46ce-97b2-bd6dfce6f6c6@amd.com \
    --to=vineeth@amd.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=conor.dooley@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=git@amd.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=theo.lebrun@bootlin.com \
    --cc=vineeth.karumanchi@amd.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