From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
Sean Wang <sean.wang@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Benjamin Larsson <benjamin.larsson@genexis.eu>,
linux-mediatek@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] pinctrl: airoha: fix wrong MDIO function bitmaks
Date: Mon, 8 Sep 2025 19:48:17 +0200 [thread overview]
Message-ID: <68bf16e5.df0a0220.2e182c.b822@mx.google.com> (raw)
In-Reply-To: <583981f9-b2ed-45fe-a327-4fd8218dc23e@lunn.ch>
On Mon, Sep 08, 2025 at 06:54:15PM +0200, Andrew Lunn wrote:
> On Mon, Sep 08, 2025 at 01:37:19PM +0200, Christian Marangi wrote:
> > With further testing with an attached Aeonsemi it was discovered that
> > the pinctrl MDIO function applied the wrong bitmask. The error was
> > probably caused by the confusing documentation related to these bits.
> >
> > Inspecting what the bootloader actually configure, the SGMII_MDIO_MODE
> > is never actually set but instead it's set force enable to the 2 GPIO
> > (gpio 1-2) for MDC and MDIO pin.
>
> Is the MDIO bus implemented using the GPIO bitbanging driver?
>
No it does use the MDIO bus integrated in the MT7530 Switch. It's just
that the MDIO pin can be muxed as GPIO usage.
--
Ansuel
next prev parent reply other threads:[~2025-09-08 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 11:37 [PATCH] pinctrl: airoha: fix wrong MDIO function bitmaks Christian Marangi
2025-09-08 12:12 ` Benjamin Larsson
2025-09-08 13:04 ` Linus Walleij
2025-09-08 16:54 ` Andrew Lunn
2025-09-08 17:48 ` Christian Marangi [this message]
2025-09-08 19:06 ` Andrew Lunn
2025-09-08 19:14 ` Christian Marangi
2025-09-08 20:07 ` Andrew Lunn
2025-09-08 21:03 ` Linus Walleij
2025-09-08 21:05 ` Christian Marangi
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=68bf16e5.df0a0220.2e182c.b822@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.larsson@genexis.eu \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@kernel.org \
--cc=stable@vger.kernel.org \
/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.