From: <Parthiban.Veerasooran@microchip.com>
To: <andrew@lunn.ch>
Cc: <piergiorgio.beruto@gmail.com>, <hkallweit1@gmail.com>,
<linux@armlinux.org.uk>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<steve.glendinning@shawell.net>, <UNGLinuxDriver@microchip.com>,
<netdev@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: [PATCH net-next 1/3] net: phy: phy-c45: add OATC10 Sleep/Wakeup support in 10BASE-T1S PHYs
Date: Wed, 1 Apr 2026 03:12:03 +0000 [thread overview]
Message-ID: <4c1eb339-a32b-44df-9989-561eb01c6825@microchip.com> (raw)
In-Reply-To: <239a7455-5cb6-4cbb-b9d6-1d48a0cadbc8@lunn.ch>
Hi Andrew,
On 30/03/26 8:16 pm, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
>> + /* Cache PLCA settings for later use. These values must be restored when
>> + * the PHY wakes up from the low-power sleep state, as all configured
>> + * settings are lost.
>> + */
>
> Does the standard define that this configuration is lost in low power
> mode? If the standard says this, then fine. But if not, it should be
> the PHY driver which saves its state during suspend, and restores it
> during resume.
Thank you for the review and pointing this out.
You are correct that the Open Alliance TC10 specification does not
explicitly state that PHY configuration is lost when entering the
low‑power state. My earlier assumption was based on the LAN8670/1/2 PHY
implementation, where the 'monitor and react to wake event' block
remains active while other power supplies are switched off, resulting in
configuration loss.
However, since this behavior is not mandated by the specification and
may vary across PHY implementations, it should not be handled within the
generic PHY framework.
Given this, I agree that state save and restore is PHY‑specific
behavior. I will move this logic into the lan867x PHY driver in the next
revision.
Moreover I will revisit the implementation with internal review and then
post the next version. Thank you for your support.
Best regards,
Parthiban V
>
> Andrew
next prev parent reply other threads:[~2026-04-01 3:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 13:42 [PATCH net-next 0/3] Add OATC10 Sleep Wake-up support and LAN867x Rev.D0 handling Parthiban Veerasooran
2026-03-30 13:42 ` [PATCH net-next 1/3] net: phy: phy-c45: add OATC10 Sleep/Wakeup support in 10BASE-T1S PHYs Parthiban Veerasooran
2026-03-30 14:46 ` Andrew Lunn
2026-04-01 3:12 ` Parthiban.Veerasooran [this message]
2026-03-30 13:42 ` [PATCH net-next 2/3] net: phy: microchip_t1s: add suspend and WOL support for LAN867x Rev.D0 Parthiban Veerasooran
2026-03-30 13:42 ` [PATCH net-next 3/3] net: usb: smsc95xx: suspend PHY during USB suspend Parthiban Veerasooran
2026-03-30 17:39 ` Oliver Neukum
2026-04-01 3:18 ` Parthiban.Veerasooran
2026-04-01 17:24 ` Oliver Neukum
2026-04-02 5:18 ` Parthiban.Veerasooran
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=4c1eb339-a32b-44df-9989-561eb01c6825@microchip.com \
--to=parthiban.veerasooran@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piergiorgio.beruto@gmail.com \
--cc=steve.glendinning@shawell.net \
/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