public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Ansuel Smith <ansuelsmth@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: dsa: qca8k: fix kernel panic with legacy mdio mapping
Date: Sat, 11 Sep 2021 08:31:51 -0700	[thread overview]
Message-ID: <5ec1a416-45e5-4679-9aa4-aa96b7f738b0@gmail.com> (raw)
In-Reply-To: <20210911150731.16586-1-ansuelsmth@gmail.com>



On 9/11/2021 08:07, Ansuel Smith wrote:
> When the mdio legacy mapping is used the mii_bus priv registred by DSA

typo: registered

> refer to the dsa switch struct instead of the qca8k_priv struct and
> cause a kernel panic.

typo: causes

> Create dedicated function when the internal
> dedicated mdio driver is used to proprely handle the 2 different
> implementation.

typo: properly

> 
> Fixes: 759bafb8a322 ("net: dsa: qca8k: add support for internal phy and internal mdio")
> Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
> ---
>   drivers/net/dsa/qca8k.c | 30 ++++++++++++++++++++++--------
>   1 file changed, 22 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/net/dsa/qca8k.c b/drivers/net/dsa/qca8k.c
> index 1f63f50f73f1..a701323daf72 100644
> --- a/drivers/net/dsa/qca8k.c
> +++ b/drivers/net/dsa/qca8k.c
> @@ -643,10 +643,8 @@ qca8k_mdio_busy_wait(struct mii_bus *bus, u32 reg, u32 mask)
>   }
>   
>   static int
> -qca8k_mdio_write(struct mii_bus *salve_bus, int phy, int regnum, u16 data)
> +qca8k_mdio_write(struct mii_bus *bus, int phy, int regnum, u16 data)
>   {
> -	struct qca8k_priv *priv = salve_bus->priv;
> -	struct mii_bus *bus = priv->bus;
>   	u16 r1, r2, page;
>   	u32 val;
>   	int ret;
> @@ -682,10 +680,8 @@ qca8k_mdio_write(struct mii_bus *salve_bus, int phy, int regnum, u16 data)
>   }
>   
>   static int
> -qca8k_mdio_read(struct mii_bus *salve_bus, int phy, int regnum)
> +qca8k_mdio_read(struct mii_bus *bus, int phy, int regnum)
>   {
> -	struct qca8k_priv *priv = salve_bus->priv;
> -	struct mii_bus *bus = priv->bus;
>   	u16 r1, r2, page;
>   	u32 val;
>   	int ret;
> @@ -726,6 +722,24 @@ qca8k_mdio_read(struct mii_bus *salve_bus, int phy, int regnum)
>   	return ret;
>   }
>   
> +static int
> +qca8k_internal_mdio_write(struct mii_bus *salve_bus, int phy, int regnum, u16 data)
> +{
> +	struct qca8k_priv *priv = salve_bus->priv;

You are only moving code here but while at it, mind fixing that typo?

> +	struct mii_bus *bus = priv->bus;
> +
> +	return qca8k_mdio_write(bus, phy, regnum, data);
> +}
> +
> +static int
> +qca8k_internal_mdio_read(struct mii_bus *salve_bus, int phy, int regnum)
> +{
> +	struct qca8k_priv *priv = salve_bus->priv;
> +	struct mii_bus *bus = priv->bus;
> +
> +	return qca8k_mdio_read(bus, phy, regnum);
> +}
> +
>   static int
>   qca8k_phy_write(struct dsa_switch *ds, int port, int regnum, u16 data)
>   {
> @@ -775,8 +789,8 @@ qca8k_mdio_register(struct qca8k_priv *priv, struct device_node *mdio)
>   
>   	bus->priv = (void *)priv;
>   	bus->name = "qca8k slave mii";
> -	bus->read = qca8k_mdio_read;
> -	bus->write = qca8k_mdio_write;
> +	bus->read = qca8k_internal_mdio_read;
> +	bus->write = qca8k_internal_mdio_write;
>   	snprintf(bus->id, MII_BUS_ID_SIZE, "qca8k-%d",
>   		 ds->index);
>   
> 

-- 
Florian

  reply	other threads:[~2021-09-11 15:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-11 15:07 [PATCH] net: dsa: qca8k: fix kernel panic with legacy mdio mapping Ansuel Smith
2021-09-11 15:31 ` Florian Fainelli [this message]
2021-09-11 15:36   ` Ansuel Smith
2021-09-11 15:40     ` Vladimir Oltean
2021-09-11 15:44       ` Ansuel Smith

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=5ec1a416-45e5-4679-9aa4-aa96b7f738b0@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=vivien.didelot@gmail.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