From: <Arun.Ramadoss@microchip.com>
To: <olteanv@gmail.com>, <UNGLinuxDriver@microchip.com>,
<andrew@lunn.ch>, <f.fainelli@gmail.com>, <kuba@kernel.org>,
<a.fatoum@pengutronix.de>, <Woojung.Huh@microchip.com>,
<davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel@pengutronix.de>, <pabeni@redhat.com>,
<ore@pengutronix.de>, <edumazet@google.com>
Subject: Re: [PATCH net] net: dsa: microchip: fix probe of I2C-connected KSZ8563
Date: Fri, 20 Jan 2023 10:47:35 +0000 [thread overview]
Message-ID: <2f97cd592d188c71ebab796cc6eaf77654a43c17.camel@microchip.com> (raw)
In-Reply-To: <55b34928-e5b0-7ab7-fa40-5ae73d05a269@pengutronix.de>
On Fri, 2023-01-20 at 11:42 +0100, Ahmad Fatoum wrote:
> [Some people who received this message don't often get email from
> a.fatoum@pengutronix.de. Learn why this is important at
> https://aka.ms/LearnAboutSenderIdentification ]
>
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On 20.01.23 11:38, Arun.Ramadoss@microchip.com wrote:
> > On Fri, 2023-01-20 at 08:57 +0100, Ahmad Fatoum wrote:
> > > > In this commit, there is no KSZ8563 member in struct
> > > > ksz_switch_chips.
> > > > Whether the fixes should be to this commit "net: dsa:
> > > > microchip:
> > > > add
> > > > separate struct ksz_chip_data for KSZ8563" where the member is
> > > > introduced.
> > >
> > > I disagree. eee16b147121 introduced the check that made my device
> > > not probe anymore, so that's what's referenced in Fixes:. Commit
> > > b44908095612 should have had a Fixes: pointing at eee16b147121
> > > as well, so users don't miss it. But if they miss it, they
> > > will notice this at build-time anyway.
> >
> > The KSZ9893, KSZ9563 and KSZ8563 all has the same chip id
> > 0x00989300.
> > They belong to 3 port switch family. Differentiation is done based
> > on
> > 0x1F register. In the commit eee16b147121, there is no
> > differentiation
> > based on 0x1F, device is selected based on chip id, all the three
> > chips
> > will be identified as ksz9893 only. After the commit b44908095612,
> > KSZ8563 chips is identified based on 0x1F register.
>
> Thanks for the elaboration. I see it now. I will send a v2
> with revised commit messages and Fixes:. Should I include
> your Reviewed-by: with the commit message rewritten?
I think, I can add my Ack-by: after you post v2 version.
>
> Cheers,
> Ahmad
>
> >
> > >
> > > Cheers,
> > > Ahmad
> > >
> > > >
> > > > > chip
> > > > > Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> > > > > ---
> > > > > drivers/net/dsa/microchip/ksz9477_i2c.c | 2 +-
> > > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/drivers/net/dsa/microchip/ksz9477_i2c.c
> > > > > b/drivers/net/dsa/microchip/ksz9477_i2c.c
> > > > > index c1a633ca1e6d..e315f669ec06 100644
> > > > > --- a/drivers/net/dsa/microchip/ksz9477_i2c.c
> > > > > +++ b/drivers/net/dsa/microchip/ksz9477_i2c.c
> > > > > @@ -104,7 +104,7 @@ static const struct of_device_id
> > > > > ksz9477_dt_ids[]
> > > > > = {
> > > > > },
> > > > > {
> > > > > .compatible = "microchip,ksz8563",
> > > > > - .data = &ksz_switch_chips[KSZ9893]
> > > > > + .data = &ksz_switch_chips[KSZ8563]
> > > > > },
> > > > > {
> > > > > .compatible = "microchip,ksz9567",
> > > > > --
> > > > > 2.30.2
> > > > >
> > >
> > > --
> > > Pengutronix
> > > e.K. | |
> > > Steuerwalder Str. 21 |
> > > http://www.pengutronix.de/e/e/ |
> > > 31137 Hildesheim, Germany | Phone: +49-5121-
> > > 206917-
> > > 0 |
> > > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-
> > > 206917-
> > > 5555 |
> > >
>
> --
> Pengutronix
> e.K. | |
> Steuerwalder Str. 21 |
> http://www.pengutronix.de/e/ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-
> 0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-
> 5555 |
>
next prev parent reply other threads:[~2023-01-20 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:10 [PATCH net] net: dsa: microchip: fix probe of I2C-connected KSZ8563 Ahmad Fatoum
2023-01-19 13:56 ` Andrew Lunn
2023-01-20 7:01 ` Arun.Ramadoss
2023-01-20 7:57 ` Ahmad Fatoum
2023-01-20 10:38 ` Arun.Ramadoss
2023-01-20 10:42 ` Ahmad Fatoum
2023-01-20 10:47 ` Arun.Ramadoss [this message]
2023-01-20 13:08 ` Andrew Lunn
2023-01-20 13:15 ` Ahmad Fatoum
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=2f97cd592d188c71ebab796cc6eaf77654a43c17.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=a.fatoum@pengutronix.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=ore@pengutronix.de \
--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