From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH RESUBMIT net-next] r8169: simplify EEE handling
Date: Fri, 2 Feb 2024 07:55:38 +0100 [thread overview]
Message-ID: <be436811-af21-4c8e-9298-69706e6895df@gmail.com> (raw)
In-Reply-To: <d5d18109-e882-43cd-b0e5-a91ffffa7fed@lunn.ch>
On 02.02.2024 01:16, Andrew Lunn wrote:
>> @@ -5058,7 +5033,9 @@ static int r8169_mdio_register(struct rtl8169_private *tp)
>> }
>>
>> tp->phydev->mac_managed_pm = true;
>> -
>> + if (rtl_supports_eee(tp))
>> + linkmode_copy(tp->phydev->advertising_eee,
>> + tp->phydev->supported_eee);
>
> This looks odd. Does it mean something is missing on phylib?
>
Reason is that we treat "normal" advertising and EEE advertising differently
in phylib. See this code snippet from phy_probe().
phy_advertise_supported(phydev);
/* Get PHY default EEE advertising modes and handle them as potentially
* safe initial configuration.
*/
err = genphy_c45_read_eee_adv(phydev, phydev->advertising_eee);
For EEE we don't change the initial advertising to what's supported,
but preserve the EEE advertising at the time of phy probing.
So if I want to mimic the behavior of phy_advertise_supported() for EEE,
I have to populate advertising_eee in the driver.
Alternative would be to change phy_advertise_supported(), but this may
impact systems with PHY's with EEE flaws.
> Andrew
Heiner
next prev parent reply other threads:[~2024-02-02 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 20:31 [PATCH RESUBMIT net-next] r8169: simplify EEE handling Heiner Kallweit
2024-02-02 0:16 ` Andrew Lunn
2024-02-02 6:55 ` Heiner Kallweit [this message]
2024-02-02 13:12 ` Andrew Lunn
2024-02-02 16:06 ` Heiner Kallweit
2024-02-02 16:15 ` Jakub Kicinski
2024-02-02 20:36 ` Heiner Kallweit
2024-02-03 5:10 ` 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=be436811-af21-4c8e-9298-69706e6895df@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).