From: Andrew Lunn <andrew@lunn.ch>
To: Michael Walle <michael@walle.cc>
Cc: Xu Liang <lxu@maxlinear.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v1 1/4] net: phy: mxl-gpy: add MDINT workaround
Date: Fri, 2 Dec 2022 19:23:04 +0100 [thread overview]
Message-ID: <Y4pCiOHgNCPLyZzA@lunn.ch> (raw)
In-Reply-To: <20221202151204.3318592-2-michael@walle.cc>
On Fri, Dec 02, 2022 at 04:12:01PM +0100, Michael Walle wrote:
> At least the GPY215B and GPY215C has a bug where it is still driving the
> interrupt line (MDINT) even after the interrupt status register is read
> and its bits are cleared. This will cause an interrupt storm.
>
> Although the MDINT is multiplexed with a GPIO pin and theoretically we
> could switch the pinmux to GPIO input mode, this isn't possible because
> the access to this register will stall exactly as long as the interrupt
> line is asserted. We exploit this very fact and just read a random
> internal register in our interrupt handler. This way, it will be delayed
> until the external interrupt line is released and an interrupt storm is
> avoided.
>
> The internal register access via the mailbox was deduced by looking at
> the downstream PHY API because the datasheet doesn't mention any of
> this.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
> drivers/net/phy/mxl-gpy.c | 83 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 83 insertions(+)
>
> diff --git a/drivers/net/phy/mxl-gpy.c b/drivers/net/phy/mxl-gpy.c
> index 0ff7ef076072..20e610dda891 100644
> --- a/drivers/net/phy/mxl-gpy.c
> +++ b/drivers/net/phy/mxl-gpy.c
> @@ -9,6 +9,7 @@
> #include <linux/module.h>
> #include <linux/bitfield.h>
> #include <linux/hwmon.h>
> +#include <linux/mutex.h>
> #include <linux/phy.h>
> #include <linux/polynomial.h>
> #include <linux/netdevice.h>
> @@ -81,6 +82,14 @@
> #define VSPEC1_TEMP_STA 0x0E
> #define VSPEC1_TEMP_STA_DATA GENMASK(9, 0)
>
> +/* Mailbox */
> +#define VSPEC1_MBOX_DATA 0x5
> +#define VSPEC1_MBOX_ADDRLO 0x6
> +#define VSPEC1_MBOX_CMD 0x7
> +#define VSPEC1_MBOX_CMD_ADDRHI GENMASK(7, 0)
> +#define VSPEC1_MBOX_CMD_RD (0 << 8)
> +#define VSPEC1_MBOX_CMD_READY BIT(15)
> +
> /* WoL */
> #define VPSPEC2_WOL_CTL 0x0E06
> #define VPSPEC2_WOL_AD01 0x0E08
> @@ -88,7 +97,15 @@
> #define VPSPEC2_WOL_AD45 0x0E0A
> #define WOL_EN BIT(0)
>
> +/* Internal registers, access via mbox */
> +#define REG_GPIO0_OUT 0xd3ce00
> +
> struct gpy_priv {
> + struct phy_device *phydev;
> +
> + /* serialize mailbox acesses */
> + struct mutex mbox_lock;
> +
> static int gpy_probe(struct phy_device *phydev)
> {
> struct device *dev = &phydev->mdio.dev;
> @@ -228,7 +286,9 @@ static int gpy_probe(struct phy_device *phydev)
> priv = devm_kzalloc(dev, sizeof(*priv), GFP_KERNEL);
> if (!priv)
> return -ENOMEM;
> + priv->phydev = phydev;
I don't think you use this anywhere. Maybe in one of the following
patches?
Andrew
next prev parent reply other threads:[~2022-12-02 18:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 15:12 [PATCH net-next v1 0/4] net: phy: mxl-gpy: broken interrupt fixes Michael Walle
2022-12-02 15:12 ` [PATCH net-next v1 1/4] net: phy: mxl-gpy: add MDINT workaround Michael Walle
2022-12-02 18:23 ` Andrew Lunn [this message]
2022-12-02 22:53 ` Michael Walle
2022-12-02 15:12 ` [PATCH net-next v1 2/4] dt-bindings: vendor-prefixes: add MaxLinear Michael Walle
2022-12-02 15:28 ` Krzysztof Kozlowski
2022-12-02 15:12 ` [PATCH net-next v1 3/4] dt-bindings: net: phy: add MaxLinear GPY2xx bindings Michael Walle
2022-12-02 18:31 ` Andrew Lunn
2022-12-02 22:50 ` Michael Walle
2022-12-05 21:29 ` Rob Herring
2022-12-05 21:53 ` Michael Walle
2022-12-06 8:29 ` Michael Walle
2022-12-06 8:38 ` Krzysztof Kozlowski
2022-12-06 9:44 ` Michael Walle
2022-12-16 9:03 ` Michael Walle
2022-12-20 13:21 ` Andrew Lunn
2022-12-28 15:00 ` Michael Walle
2022-12-02 15:12 ` [PATCH net-next v1 4/4] net: phy: mxl-gpy: disable interrupts on GPY215 by default Michael Walle
2022-12-02 18:42 ` Andrew Lunn
2022-12-02 23:09 ` Michael Walle
2022-12-03 20:36 ` Andrew Lunn
2022-12-16 9:46 ` Michael Walle
2022-12-20 13:33 ` Andrew Lunn
2022-12-20 21:39 ` Michael Walle
2022-12-03 20:41 ` [PATCH net-next v1 0/4] net: phy: mxl-gpy: broken interrupt fixes Andrew Lunn
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=Y4pCiOHgNCPLyZzA@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lxu@maxlinear.com \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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 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).