public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ashok Kumar Natarajan <ashokkumar.natarajan@amd.com>
Cc: <dev@dpdk.org>, <Selwin.Sebastian@amd.com>
Subject: Re: [PATCH v4] net/axgbe: mask unsupported PHY half-duplex modes
Date: Thu, 16 Apr 2026 12:01:31 -0700	[thread overview]
Message-ID: <20260416120131.12f2e761@phoenix.local> (raw)
In-Reply-To: <20260416070526.1504-1-ashokkumar.natarajan@amd.com>

On Thu, 16 Apr 2026 12:35:24 +0530
Ashok Kumar Natarajan <ashokkumar.natarajan@amd.com> wrote:

> The AXGBE MAC supports only full-duplex operation at all speeds.
> However, the PHY auto-negotiation configuration could advertise
> half-duplex modes, including 10BASE-T, 100BASE-TX, and 1000BASE-T,
> which are not supported by the MAC.
> 
> Update the Clause 22 and Clause 40 PHY advertisement handling to mask
> all half-duplex modes while preserving existing PHY, strap, and
> vendor-specific configuration using read-modify-write.
> 
> To maintain backward compatibility, full-duplex advertisement for
> 10/100 and 1000BASE-T is preserved by default when no explicit PHY
> advertising mask is provided.
> 
> This ensures IEEE 802.3 compliant PHY advertisement while avoiding
> regressions on platforms relying on PHY default configuration.
> 
> Signed-off-by: Ashok Kumar Natarajan <ashokkumar.natarajan@amd.com>
> ---

Looks good, applied to next-net

      reply	other threads:[~2026-04-16 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31  9:04 [PATCH v1] net/axgbe: fix PHY auto-negotiation advertisement Ashok Kumar Natarajan
2026-04-01  7:58 ` [PATCH v2] " Ashok Kumar Natarajan
2026-04-02  6:54   ` [PATCH v3] net/axgbe: mask unsupported PHY half-duplex modes Ashok Kumar Natarajan
2026-04-05 20:07     ` Stephen Hemminger
2026-04-05 19:57       ` Stephen Hemminger
2026-04-16  7:05     ` [PATCH v4] " Ashok Kumar Natarajan
2026-04-16 19:01       ` Stephen Hemminger [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=20260416120131.12f2e761@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=Selwin.Sebastian@amd.com \
    --cc=ashokkumar.natarajan@amd.com \
    --cc=dev@dpdk.org \
    /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