From: <Rengarajan.S@microchip.com>
To: <andrew@lunn.ch>
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: lan7801 MAC support with lan8841
Date: Thu, 20 Jun 2024 05:48:31 +0000 [thread overview]
Message-ID: <06a180e5c21761c53c18dd208c9ea756570dd142.camel@microchip.com> (raw)
In-Reply-To: <6eec7a37-13d0-4451-9b32-4b031c942aa1@lunn.ch>
Hi Andrew,
Apologies for the delay in reply. Thanks for reviewing the patch.
Please find my comments inline.
On Thu, 2024-06-13 at 22:46 +0200, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Tue, Jun 11, 2024 at 03:12:33PM +0530, Rengarajan S wrote:
> > Add lan7801 MAC only support with lan8841. The PHY fixup is
> > registered
> > for lan8841 and the initializations are done using lan8835_fixup
> > since
> > the register configs are similar for both lann8841 and lan8835.
>
> What exactly does this fixup do?
Fixup related to the phy handle and manage the configuration and status
registers of a particular phy. In this patch it is used to handle the
configuration registers of LAN8841 which are similar to registers in
LAN8835.
>
> Looking at it, what protects it from being used on some other device
> which also happens to use the same PHY? Is there something to
> guarantee:
>
> struct lan78xx_net *dev = netdev_priv(phydev->attached_dev);
>
> really is a lan78xx_net * ?
In this case fixup is called through lan78xx only when interfacing the
phy with lan78xx MAC. Since this will not be called on interfacing with
other devices, it prevents them from accessing the registers.
next prev parent reply other threads:[~2024-06-20 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 9:42 [PATCH net-next v1] lan78xx: lan7801 MAC support with lan8841 Rengarajan S
2024-06-13 1:33 ` Jakub Kicinski
2024-06-20 5:33 ` Rengarajan.S
2024-06-13 20:46 ` Andrew Lunn
2024-06-20 5:48 ` Rengarajan.S [this message]
2024-06-20 13:49 ` Andrew Lunn
2024-06-28 10:59 ` Rengarajan.S
2024-06-28 13:03 ` Andrew Lunn
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=06a180e5c21761c53c18dd208c9ea756570dd142.camel@microchip.com \
--to=rengarajan.s@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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