From: <Rengarajan.S@microchip.com>
To: <horms@kernel.org>
Cc: <linux-usb@vger.kernel.org>, <davem@davemloft.net>,
<Woojung.Huh@microchip.com>, <linux-kernel@vger.kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<edumazet@google.com>, <UNGLinuxDriver@microchip.com>,
<kuba@kernel.org>
Subject: Re: [PATCH net-next v1] lan78xx: Enable 125 MHz CLK and Auto Speed configuration for LAN7801 if NO EEPROM is detected
Date: Thu, 9 May 2024 06:59:03 +0000 [thread overview]
Message-ID: <d5727bf3d176e3d71abeba7f7c3aa86cf96262cc.camel@microchip.com> (raw)
In-Reply-To: <20240504084931.GA3167983@kernel.org>
Hi Simon,
Apologies for the delay in response. Thanks for reviewing the patch.
Please find my comments inline.
On Sat, 2024-05-04 at 09:49 +0100, Simon Horman wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Thu, May 02, 2024 at 10:25:03AM +0530, Rengarajan S wrote:
> > The 125MHz and 25MHz clock configurations are done in the
> > initialization
> > regardless of EEPROM (125MHz is needed for RGMII 1000Mbps
> > operation). After
> > a lite reset (lan78xx_reset), these contents go back to
> > defaults(all 0, so
> > no 125MHz or 25MHz clock and no ASD/ADD). Also, after the lite
> > reset, the
> > LAN7800 enables the ASD/ADD in the absence of EEPROM. There is no
> > such
> > check for LAN7801.
> >
> > Signed-off-by: Rengarajan S <rengarajan.s@microchip.com>
>
> Hi Rengarajan,
>
> This patch seems address two issues.
> So I think it would be best to split it into two patches.
Sure. Will split the patch into two and will submit the updated patch
in the next revision shortly,
>
> Also, are these problems bugs - do they have adverse effect visible
> by
> users? If so perhaps they should be targeted at 'net' rather than
> 'net-next', and an appropriate Fixes tag should appear just above
> the Signed-off-by line (no blank line in between).
The changes listed in the patch are feature additions where we give an
option of configuring the clock and speed in the absence of the EEPROM.
The current code does not have any bugs related to this. Since, these
are the additional features/requirements, we are targeting at 'net-
next' rather than 'net'.
>
> ...
>
> --
> pw-bot: under-review
next prev parent reply other threads:[~2024-05-09 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 4:55 [PATCH net-next v1] lan78xx: Enable 125 MHz CLK and Auto Speed configuration for LAN7801 if NO EEPROM is detected Rengarajan S
2024-05-04 8:49 ` Simon Horman
2024-05-09 6:59 ` Rengarajan.S [this message]
2024-05-09 13:39 ` Simon Horman
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=d5727bf3d176e3d71abeba7f7c3aa86cf96262cc.camel@microchip.com \
--to=rengarajan.s@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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