mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Michael Zimmermann <sigmaepsilon92@gmail.com>
Cc: Fabio Baltieri <fabio.baltieri@gmail.com>,
	nic_swsd@realtek.com, Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] r8169: add support for RTL8127ATF
Date: Sun, 23 Nov 2025 17:59:28 +0100	[thread overview]
Message-ID: <107ae398-4351-4be3-83ec-d03fa91e2a81@gmail.com> (raw)
In-Reply-To: <CAN9vWDLGSDQQMPBVesOwAR3vvPko+ZG-eyxrL96OUM=1J05Ojg@mail.gmail.com>

On 11/23/2025 5:26 PM, Michael Zimmermann wrote:
>> +       }, {
>> +               PHY_ID_MATCH_EXACT(0x001ccbff),
>> +               .name           = "Realtek SFP PHY Mode",
>> +               .flags          = PHY_IS_INTERNAL,
>> +               .probe          = rtl822x_probe,
>> +               .get_features   = rtlgen_sfp_get_features,
>> +               .config_aneg    = rtlgen_sfp_config_aneg,
>> +               .read_status    = rtl822x_read_status,
>> +               .suspend        = genphy_suspend,
>> +               .resume         = rtlgen_resume,
>> +               .read_page      = rtl821x_read_page,
>> +               .write_page     = rtl821x_write_page,
>> +               .read_mmd       = rtl822x_read_mmd,
>> +               .write_mmd      = rtl822x_write_mmd,
> 
> I didn't get a chance to test your patch, yet, but is this intended to
> match RTL8127AF? Because that's not it's phy id. It's the same as
> RTL_8261C and currently matches "Realtek Internal NBASE-T PHY":
> 
See earlier in the patch:

+	/* Return dummy MII_PHYSID2 in SFP mode to match SFP PHY driver */
+	if (tp->sfp_mode && reg == (OCP_STD_PHY_BASE + 2 * MII_PHYSID2))
+		return 0xcbff;

The PHY_ID read is intercepted.

> # cat /proc/self/net/r8127/enp8s0/debug/eth_phy
> 
> Dump Ethernet PHY
> 
> Offset  Value
> ------  -----
> 
> ####################page 0##################
> 
> 0x00:   0040 798d 001c c890 1c01 0000 0064 2001
> 0x08:   0000 0000 0000 0000 0000 0000 0000 2000
> ####################extra reg##################
> 
> 0xa400: 0040 798d 001c c890 1c01 0000 0064 2001
> 0xa410: 0000 0000 0000
> 0xa434: 0a0c
> 0xa5d0: 0000 0000 0001 4000
> 0xa61a: 0400
> 0xa6d0: 0000 0000 0000


  reply	other threads:[~2025-11-23 16:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 19:50 Fabio Baltieri
2025-11-20 20:55 ` Heiner Kallweit
2025-11-21 20:28   ` Fabio Baltieri
2025-11-23 15:58     ` Heiner Kallweit
2025-11-23 16:26       ` Michael Zimmermann
2025-11-23 16:59         ` Heiner Kallweit [this message]
2025-11-23 18:41       ` Fabio Baltieri
2025-11-23 22:54         ` Heiner Kallweit
2025-11-24  0:00           ` Fabio Baltieri
2025-12-03 22:11             ` Fabio Baltieri
2025-12-04  6:32               ` Heiner Kallweit
2025-12-29  4:18           ` FUKAUMI Naoki

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=107ae398-4351-4be3-83ec-d03fa91e2a81@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fabio.baltieri@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=pabeni@redhat.com \
    --cc=sigmaepsilon92@gmail.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®