From: <Arun.Ramadoss@microchip.com>
To: <olteanv@gmail.com>
Cc: <songliubraving@fb.com>, <linux-kernel@vger.kernel.org>,
<bpf@vger.kernel.org>, <daniel@iogearbox.net>, <ast@kernel.org>,
<robh+dt@kernel.org>, <andrew@lunn.ch>,
<devicetree@vger.kernel.org>, <linux@armlinux.org.uk>,
<andrii@kernel.org>, <UNGLinuxDriver@microchip.com>,
<john.fastabend@gmail.com>, <vivien.didelot@gmail.com>,
<f.fainelli@gmail.com>, <kuba@kernel.org>, <kpsingh@kernel.org>,
<edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <kafai@fb.com>, <yhs@fb.com>,
<krzysztof.kozlowski+dt@linaro.org>, <davem@davemloft.net>,
<Woojung.Huh@microchip.com>
Subject: Re: [Patch net-next v13 07/13] net: dsa: microchip: add LAN937x SPI driver
Date: Thu, 5 May 2022 10:32:17 +0000 [thread overview]
Message-ID: <52e682a1bcd2aac1097f2b4f1948066fe5bb6924.camel@microchip.com> (raw)
In-Reply-To: <20220504200726.pn7y73gt7wc2dpsg@skbuf>
Hi Vladimir,
Thanks for the comment.
On Wed, 2022-05-04 at 23:07 +0300, Vladimir Oltean wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Wed, May 04, 2022 at 08:47:49PM +0530, Arun Ramadoss wrote:
> > This patch add the SPI driver for the LAN937x switches. It uses the
> > lan937x_main.c and lan937x_dev.c functions.
> >
> > Signed-off-by: Arun Ramadoss <arun.ramadoss@microchip.com>
> > ---
> > drivers/net/dsa/microchip/Makefile | 1 +
> > drivers/net/dsa/microchip/ksz_common.h | 1 +
> > drivers/net/dsa/microchip/lan937x_dev.c | 7 +
> > drivers/net/dsa/microchip/lan937x_spi.c | 236
> > ++++++++++++++++++++++++
> > 4 files changed, 245 insertions(+)
> > create mode 100644 drivers/net/dsa/microchip/lan937x_spi.c
> >
> > diff --git a/drivers/net/dsa/microchip/Makefile
> > b/drivers/net/dsa/microchip/Makefile
> > index d32ff38dc240..28d8eb62a795 100644
> > --- a/drivers/net/dsa/microchip/Makefile
> > +++ b/drivers/net/dsa/microchip/Makefile
> > @@ -10,3 +10,4 @@ obj-$(CONFIG_NET_DSA_MICROCHIP_KSZ8863_SMI) +=
> > ksz8863_smi.o
> > obj-$(CONFIG_NET_DSA_MICROCHIP_LAN937X) += lan937x.o
> > lan937x-objs := lan937x_dev.o
> > lan937x-objs += lan937x_main.o
> > +lan937x-objs += lan937x_spi.o
> > diff --git a/drivers/net/dsa/microchip/ksz_common.h
> > b/drivers/net/dsa/microchip/ksz_common.h
> > index 5671f580948d..fd9e0705d2d2 100644
> > --- a/drivers/net/dsa/microchip/ksz_common.h
> > +++ b/drivers/net/dsa/microchip/ksz_common.h
> > @@ -151,6 +151,7 @@ void ksz_switch_remove(struct ksz_device *dev);
> > int ksz8_switch_register(struct ksz_device *dev);
> > int ksz9477_switch_register(struct ksz_device *dev);
> > int lan937x_switch_register(struct ksz_device *dev);
> > +int lan937x_check_device_id(struct ksz_device *dev);
> >
> > void ksz_update_port_member(struct ksz_device *dev, int port);
> > void ksz_init_mib_timer(struct ksz_device *dev);
> > diff --git a/drivers/net/dsa/microchip/lan937x_dev.c
> > b/drivers/net/dsa/microchip/lan937x_dev.c
> > index 3f1797cc1d16..f430a8711775 100644
> > --- a/drivers/net/dsa/microchip/lan937x_dev.c
> > +++ b/drivers/net/dsa/microchip/lan937x_dev.c
> > @@ -386,8 +386,15 @@ static int lan937x_mdio_register(struct
> > ksz_device *dev)
> >
> > static int lan937x_switch_init(struct ksz_device *dev)
> > {
> > + int ret;
> > +
> > dev->ds->ops = &lan937x_switch_ops;
> >
> > + /* Check device tree */
> > + ret = lan937x_check_device_id(dev);
> > + if (ret < 0)
> > + return ret;
> > +
>
> Can't this be called from lan937x_spi_probe() directly, why do you
> need
> to go through lan937x_switch_register() first?
lan937x_check_device_id function compares the dev->chip_id with the
lan937x_switch_chip array and populate the some of the parameters of
struct ksz_dev. The dev->chip_id is populated using the dev->dev_ops-
>detect in the ksz_switch_register function. If lan937x_check_device_id
needs to be called in spi_probe, then chip_id has to be identified as
part of spi_probe function. Since ksz_switch_register handles the
identifying the chip_id, checking the device_id is part of switch_init.
if (dev->dev_ops->detect(dev))
return -EINVAL;
ret = dev->dev_ops->init(dev);
if (ret)
return ret;
As per the comment, enable_spi_indirect_access function called twice
https://lore.kernel.org/netdev/20220408232557.b62l3lksotq5vuvm@skbuf/
I have removed the enable_spi_indirect_access in the lan937x_setup
function in v13 patch 6. But it actually failed our regression.
The SPI indirect is required for accessing the Internal phy registers.
We have enabled it in lan937x_init before registering the
mdio_register. We need it for reading the phy id.
And another place enabled in lan937x_setup after lan937x_switch_reset
function. When I removed enabling in setup function, switch_reset
disables the spi indirecting addressing. Because of that further phy
register r/w fails. In Summary, we need to enable spi indirect access
in both the places, one for mdio_register and another after
switch_reset.
Can I enable it both the places? Kindly suggest.
>
> > dev->port_mask = (1 << dev->port_cnt) - 1;
> >
> > dev->ports = devm_kzalloc(dev->dev,
next prev parent reply other threads:[~2022-05-05 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 15:17 [Patch net-next v13 00/13] net: dsa: microchip: DSA driver support for LAN937x Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 01/13] dt-bindings: net: make internal-delay-ps based on phy-mode Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 02/13] dt-bindings: net: dsa: dt bindings for microchip lan937x Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 03/13] net: dsa: move mib->cnt_ptr reset code to ksz_common.c Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 04/13] net: dsa: tag_ksz: add tag handling for Microchip LAN937x Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 05/13] net: dsa: microchip: add DSA support for microchip LAN937x Arun Ramadoss
2022-05-04 19:26 ` Vladimir Oltean
2022-05-04 15:17 ` [Patch net-next v13 06/13] net: dsa: microchip: add support for phy read and write Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 07/13] net: dsa: microchip: add LAN937x SPI driver Arun Ramadoss
2022-05-04 20:07 ` Vladimir Oltean
2022-05-05 10:32 ` Arun.Ramadoss [this message]
2022-05-05 15:15 ` Vladimir Oltean
2022-05-04 15:17 ` [Patch net-next v13 08/13] net: dsa: microchip: add support for MTU configuration and fast_age Arun Ramadoss
2022-05-04 20:10 ` Vladimir Oltean
2022-05-04 15:17 ` [Patch net-next v13 09/13] net: dsa: microchip: add support for phylink management Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 10/13] net: dsa: microchip: add support for ethtool port counters Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 11/13] net: dsa: microchip: add support for port mirror operations Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 12/13] net: dsa: microchip: add support for fdb and mdb management Arun Ramadoss
2022-05-04 15:17 ` [Patch net-next v13 13/13] net: dsa: microchip: add support for vlan operations Arun Ramadoss
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=52e682a1bcd2aac1097f2b4f1948066fe5bb6924.camel@microchip.com \
--to=arun.ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=songliubraving@fb.com \
--cc=vivien.didelot@gmail.com \
--cc=yhs@fb.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).