From: <Thangaraj.S@microchip.com>
To: <kuba@kernel.org>
Cc: <andrew+netdev@lunn.ch>, <Bryan.Whitehead@microchip.com>,
<davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>,
<edumazet@google.com>, <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH v1 net] net: lan743x: Restore SGMII CTRL register on resume
Date: Mon, 19 May 2025 09:23:56 +0000 [thread overview]
Message-ID: <067713e1ebaf303fe4aefb9c29cc7e1b70cd722a.camel@microchip.com> (raw)
In-Reply-To: <20250516164010.49dd5e8b@kernel.org>
Hi Jakub,
On Fri, 2025-05-16 at 16:40 -0700, Jakub Kicinski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Fri, 16 May 2025 09:27:19 +0530 Thangaraj Samynathan wrote:
> > SGMII_CTRL register, which specifies the active interface, was not
> > properly restored when resuming from suspend. This led to incorrect
> > interface selection after resume particularly in scenarios
> > involving
> > the FPGA.
> >
> > To fix this:
> > - Move the SGMII_CTRL setup out of the probe function.
> > - Initialize the register in the hardware initialization helper
> > function,
> > which is called during both device initialization and resume.
> >
> > This ensures the interface configuration is consistently restored
> > after
> > suspend/resume cycles.
>
> Is there a reason you're not CCing Raju Lakkaraju on this?
> Having a review tag from the author of the change under Fixes
> is always great.
Thanks for pointing this out.
Raju Lakkaraju is no longer with the company, and as I am currentlymanaging this driver, I have not included him in the CC.
Thanks,
Thangaraj Samynathan
next prev parent reply other threads:[~2025-05-19 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 3:57 [PATCH v1 net] net: lan743x: Restore SGMII CTRL register on resume Thangaraj Samynathan
2025-05-16 23:40 ` Jakub Kicinski
2025-05-19 9:23 ` Thangaraj.S [this message]
2025-05-19 22:56 ` Jakub Kicinski
2025-05-21 3: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=067713e1ebaf303fe4aefb9c29cc7e1b70cd722a.camel@microchip.com \
--to=thangaraj.s@microchip.com \
--cc=Bryan.Whitehead@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).