From: Sean Anderson <sean.anderson@linux.dev>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next 2/2] net: phy: dp83867: Always program R/SGMII enable bits
Date: Thu, 29 Jan 2026 12:32:00 -0500 [thread overview]
Message-ID: <de1d615d-85a6-495d-b830-b169f7f8310a@linux.dev> (raw)
In-Reply-To: <aXuXWxhtR-1Hvlv4@shell.armlinux.org.uk>
Hi Russell,
On 1/29/26 12:22, Russell King (Oracle) wrote:
> On Thu, Jan 29, 2026 at 12:12:05PM -0500, Sean Anderson wrote:
>> If the board designers have neglected to populate the appropriate
>> resistors on the strapping pins then the phy may default to the wrong
>> interface mode. Enable/disable the RGMII/SGMII enable bits as necessary
>> to select the correct interface.
>>
>> The dp83867 strapping pins have four levels and typically configure two
>> features at once. LED_0 controls both port mirroring and whether SGMII
>> is enabled. If it is pulled to VDDIO, both port mirroring and SGMII
>> will be enabled. For variants of the dp83867 that do not support SGMII,
>> this will prevent data from being transferred. As we now explicitly set
>> the SGMII and RGMII enable bits, we do not need to detect whether SGMII
>> has been inadvertently enabled.
>>
>> Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
>
> Something to consider:
>
> You have separate enable bits for SGMII and RGMII. The code you're
> submitting sets the SGMII enable before clearing the RGMII enable.
> Is it permitted to have both set?
Section 7.4.1 of SNLS504F says:
| The SGMII enable has higher priority than the RGMII enable. Table 7-1 is
| the configuration table for the MAC interfaces:
|
| Table 7-1. Configuration Table for the MAC Interfaces
| SGMII ENABLE RGMII ENABLE DEVICE FUNCTIONAL MODE
| (REGISTER 0x0010, BIT 11) (REGISTER 0x0032, BIT 7)
| ========================= ======================== ======================
| 0x1 0x1 SGMII
| 0x1 0x0 SGMII
| 0x0 0x1 RGMII
So I don't think we will have any problems.
--Sean
next prev parent reply other threads:[~2026-01-29 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 17:12 [PATCH net-next 0/2] net: phy: dp83867: Always program R/SGMII enable bits Sean Anderson
2026-01-29 17:12 ` [PATCH net-next 1/2] net: phy: dp83867: Program TX FIFO for all interfaces Sean Anderson
2026-01-29 17:12 ` [PATCH net-next 2/2] net: phy: dp83867: Always program R/SGMII enable bits Sean Anderson
2026-01-29 17:22 ` Russell King (Oracle)
2026-01-29 17:32 ` Sean Anderson [this message]
2026-02-03 1:30 ` [PATCH net-next 0/2] " patchwork-bot+netdevbpf
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=de1d615d-85a6-495d-b830-b169f7f8310a@linux.dev \
--to=sean.anderson@linux.dev \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.