All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: "Marek Mojík" <marek.mojik@nic.cz>,
	rfried.dev@gmail.com, u-boot@lists.denx.de,
	joe.hershberger@ni.com, tharvey@gateworks.com, marex@denx.de
Subject: Re: [PATCH v2] net: mv88e6xxx: fix missing SMI address initialization
Date: Mon, 4 Mar 2024 15:48:12 +0100	[thread overview]
Message-ID: <20240304154812.48850405@dellmb> (raw)
In-Reply-To: <45ffb9f2-8986-4d85-868e-eca618ff16ab@denx.de>

Hi Stefan,

On Wed, 14 Feb 2024 08:50:16 +0100
Stefan Roese <sr@denx.de> wrote:

> Hi Ramon,
> 
> On 1/9/24 10:37, Stefan Roese wrote:
> > On 12/18/23 17:09, Marek Behún wrote:  
> >> On Wed, 6 Dec 2023 15:35:56 +0100
> >> Marek Mojík <marek.mojik@nic.cz> wrote:
> >>  
> >>> The mv88e6xxx driver does not currently initialize the smi_addr 
> >>> field, but
> >>> instead keeps the default zero value. This leads to driver being 
> >>> unusable
> >>> on devices where the switch is not on address zero of the mdio bus. Fix
> >>> this problem by reading the SMI address from device tree.
> >>>
> >>> Signed-off-by: Marek Mojík <marek.mojik@nic.cz>
> >>> ---
> >>>   drivers/net/mv88e6xxx.c | 8 ++++++++
> >>>   1 file changed, 8 insertions(+)
> >>>
> >>> diff --git a/drivers/net/mv88e6xxx.c b/drivers/net/mv88e6xxx.c
> >>> index c073f81e72..8fbbc1cacc 100644
> >>> --- a/drivers/net/mv88e6xxx.c
> >>> +++ b/drivers/net/mv88e6xxx.c
> >>> @@ -745,6 +745,7 @@ static int mv88e6xxx_probe(struct udevice *dev)
> >>>   {
> >>>       struct dsa_pdata *dsa_pdata = dev_get_uclass_plat(dev);
> >>>       struct mv88e6xxx_priv *priv = dev_get_priv(dev);
> >>> +    fdt_addr_t smi_addr;
> >>>       int val, ret;
> >>>       if (ofnode_valid(dev_ofnode(dev)) &&
> >>> @@ -753,6 +754,13 @@ static int mv88e6xxx_probe(struct udevice *dev)
> >>>           return -ENODEV;
> >>>       }
> >>> +    smi_addr = dev_read_addr(dev);
> >>> +    if (smi_addr == FDT_ADDR_T_NONE) {
> >>> +        dev_err(dev, "Missing SMI address\n");
> >>> +        return -EINVAL;
> >>> +    }
> >>> +    priv->smi_addr = smi_addr;
> >>> +
> >>>       /* probe internal mdio bus */
> >>>       ret = mv88e6xxx_probe_mdio(dev);
> >>>       if (ret)  
> >>
> >> Reviewed-by: Marek Behún <kabel@kernel.org>  
> > 
> > Reviewed-by: Stefan Roese <sr@denx.de>
> > 
> > Ramon, this patch was assigned to me as an Marvell MVEBU patch
> > depends on it. I've assigned it to you now. Or if it's okay that
> > I pull it with the Marvell tree, just let me know.  
> 
> Any updates on this?
> 
> Thanks,
> Stefan

Stefan, it seems that Ramon is unavailable for this.
Can we take this? We've been using it on Omnia and it works correctly.

Marek

  reply	other threads:[~2024-03-04 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 14:35 [PATCH v2] net: mv88e6xxx: fix missing SMI address initialization Marek Mojík
2023-12-18 16:09 ` Marek Behún
2024-01-09  9:37   ` Stefan Roese
2024-02-14  7:50     ` Stefan Roese
2024-03-04 14:48       ` Marek Behún [this message]
2024-03-05 10:27         ` Stefan Roese
2024-03-05 10:31 ` Stefan Roese

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=20240304154812.48850405@dellmb \
    --to=kabel@kernel.org \
    --cc=joe.hershberger@ni.com \
    --cc=marek.mojik@nic.cz \
    --cc=marex@denx.de \
    --cc=rfried.dev@gmail.com \
    --cc=sr@denx.de \
    --cc=tharvey@gateworks.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.