From: Simon Horman <horms@kernel.org>
To: Parthiban.Veerasooran@microchip.com
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ramon.nordin.rodriguez@ferroamp.se,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, Thorsten.Kummermehr@microchip.com
Subject: Re: [PATCH net-next 5/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1
Date: Fri, 16 Aug 2024 17:55:41 +0100 [thread overview]
Message-ID: <20240816165541.GB632411@kernel.org> (raw)
In-Reply-To: <3235fb9a-62cf-4f9a-b21e-e0b881c79c43@microchip.com>
On Fri, Aug 16, 2024 at 01:21:02PM +0000, Parthiban.Veerasooran@microchip.com wrote:
> On 15/08/24 8:12 pm, Simon Horman wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > On Mon, Aug 12, 2024 at 07:18:14PM +0530, Parthiban Veerasooran wrote:
> >> This patch adds support for LAN8670/1/2 Rev.C1 as per the latest
> >> configuration note AN1699 released (Revision E (DS60001699F - June 2024))
> >> https://www.microchip.com/en-us/application-notes/an1699
> >>
> >> Signed-off-by: Parthiban Veerasooran <Parthiban.Veerasooran@microchip.com>
> >> ---
> >> drivers/net/phy/Kconfig | 2 +-
> >> drivers/net/phy/microchip_t1s.c | 68 ++++++++++++++++++++++++++++++++-
> >> 2 files changed, 67 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/net/phy/Kconfig b/drivers/net/phy/Kconfig
> >> index 68db15d52355..63b45544c191 100644
> >> --- a/drivers/net/phy/Kconfig
> >> +++ b/drivers/net/phy/Kconfig
> >> @@ -282,7 +282,7 @@ config MICREL_PHY
> >> config MICROCHIP_T1S_PHY
> >> tristate "Microchip 10BASE-T1S Ethernet PHYs"
> >> help
> >> - Currently supports the LAN8670/1/2 Rev.B1 and LAN8650/1 Rev.B0/B1
> >> + Currently supports the LAN8670/1/2 Rev.B1/C1 and LAN8650/1 Rev.B0/B1
> >> Internal PHYs.
> >>
> >> config MICROCHIP_PHY
> >> diff --git a/drivers/net/phy/microchip_t1s.c b/drivers/net/phy/microchip_t1s.c
> >> index d0af02a25d01..62f5ce548c6a 100644
> >> --- a/drivers/net/phy/microchip_t1s.c
> >> +++ b/drivers/net/phy/microchip_t1s.c
> >> @@ -3,7 +3,7 @@
> >> * Driver for Microchip 10BASE-T1S PHYs
> >> *
> >> * Support: Microchip Phys:
> >> - * lan8670/1/2 Rev.B1
> >> + * lan8670/1/2 Rev.B1/C1
> >> * lan8650/1 Rev.B0/B1 Internal PHYs
> >> */
> >>
> >> @@ -12,6 +12,7 @@
> >> #include <linux/phy.h>
> >>
> >> #define PHY_ID_LAN867X_REVB1 0x0007C162
> >> +#define PHY_ID_LAN867X_REVC1 0x0007C164
> >> /* Both Rev.B0 and B1 clause 22 PHYID's are same due to B1 chip limitation */
> >> #define PHY_ID_LAN865X_REVB 0x0007C1B3
> >>
> >> @@ -243,7 +244,7 @@ static int lan865x_revb_config_init(struct phy_device *phydev)
> >> if (ret)
> >> return ret;
> >>
> >> - if (i == 2) {
> >> + if (i == 1) {
> >> ret = lan865x_setup_cfgparam(phydev, offsets);
> >> if (ret)
> >> return ret;
> >
> > Hi Parthiban,
> >
> > This patch is addressing LAN867X Rev.C1 support.
> > But the hunk above appears to update LAN865X Rev.B0/B1 support.
> > Is that intentional?
>
> Hi Simon,
>
> Sorry, there is a mistake here. It is supposed to be "i == 1" only, but
> it should have been in the below patch onwards,
>
> "[PATCH net-next 2/7] net: phy: microchip_t1s: update new initial
> settings for LAN865X Rev.B0"
>
> Thanks for pointing it out. Will correct it in the next version.
Thanks,
Other than the minor problem noted above, the patchset looked good to me.
next prev parent reply other threads:[~2024-08-16 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 13:48 [PATCH net-next 0/7] microchip_t1s: Update on Microchip 10BASE-T1S PHY driver Parthiban Veerasooran
2024-08-12 13:48 ` [PATCH net-next 1/7] net: phy: microchip_t1s: restructure cfg read/write functions arguments Parthiban Veerasooran
2024-08-12 13:48 ` [PATCH net-next 2/7] net: phy: microchip_t1s: update new initial settings for LAN865X Rev.B0 Parthiban Veerasooran
2024-08-12 13:48 ` [PATCH net-next 3/7] net: phy: microchip_t1s: add support for Microchip's LAN865X Rev.B1 Parthiban Veerasooran
2024-08-12 13:48 ` [PATCH net-next 4/7] net: phy: microchip_t1s: move LAN867X reset handling to a new function Parthiban Veerasooran
2024-08-12 13:48 ` [PATCH net-next 5/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C1 Parthiban Veerasooran
2024-08-15 14:42 ` Simon Horman
2024-08-16 13:21 ` Parthiban.Veerasooran
2024-08-16 16:55 ` Simon Horman [this message]
2024-08-19 7:24 ` Parthiban.Veerasooran
2024-08-12 13:48 ` [PATCH net-next 6/7] net: phy: microchip_t1s: add support for Microchip's LAN867X Rev.C2 Parthiban Veerasooran
2024-08-12 13:48 ` [PATCH net-next 7/7] net: phy: microchip_t1s: configure collision detection based on PLCA mode 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=20240816165541.GB632411@kernel.org \
--to=horms@kernel.org \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=Thorsten.Kummermehr@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-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ramon.nordin.rodriguez@ferroamp.se \
/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).