From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Michael Walle <michael@walle.cc>
Cc: Andrew Lunn <andrew@lunn.ch>,
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>,
Divya Koppera <Divya.Koppera@microchip.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: phy: micrel: fix shared interrupt on LAN8814
Date: Wed, 21 Sep 2022 08:40:19 +0200 [thread overview]
Message-ID: <20220921064019.at4pbog6d2gzjyjq@soft-dev3-1.localhost> (raw)
In-Reply-To: <20220920141619.808117-1-michael@walle.cc>
The 09/20/2022 16:16, Michael Walle wrote:
>
> Since commit ece19502834d ("net: phy: micrel: 1588 support for LAN8814
> phy") the handler always returns IRQ_HANDLED, except in an error case.
> Before that commit, the interrupt status register was checked and if
> it was empty, IRQ_NONE was returned. Restore that behavior to play nice
> with the interrupt line being shared with others.
>
> Fixes: ece19502834d ("net: phy: micrel: 1588 support for LAN8814 phy")
> Signed-off-by: Michael Walle <michael@walle.cc>
Reviewed-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> drivers/net/phy/micrel.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> index 98e9bc101d96..21b6facf6e76 100644
> --- a/drivers/net/phy/micrel.c
> +++ b/drivers/net/phy/micrel.c
> @@ -2732,16 +2732,19 @@ static int lan8804_config_intr(struct phy_device *phydev)
> static irqreturn_t lan8814_handle_interrupt(struct phy_device *phydev)
> {
> int irq_status, tsu_irq_status;
> + int ret = IRQ_NONE;
>
> irq_status = phy_read(phydev, LAN8814_INTS);
> - if (irq_status > 0 && (irq_status & LAN8814_INT_LINK))
> - phy_trigger_machine(phydev);
> -
> if (irq_status < 0) {
> phy_error(phydev);
> return IRQ_NONE;
> }
>
> + if (irq_status & LAN8814_INT_LINK) {
> + phy_trigger_machine(phydev);
> + ret = IRQ_HANDLED;
> + }
> +
> while (1) {
> tsu_irq_status = lanphy_read_page_reg(phydev, 4,
> LAN8814_INTR_STS_REG);
> @@ -2750,12 +2753,15 @@ static irqreturn_t lan8814_handle_interrupt(struct phy_device *phydev)
> (tsu_irq_status & (LAN8814_INTR_STS_REG_1588_TSU0_ |
> LAN8814_INTR_STS_REG_1588_TSU1_ |
> LAN8814_INTR_STS_REG_1588_TSU2_ |
> - LAN8814_INTR_STS_REG_1588_TSU3_)))
> + LAN8814_INTR_STS_REG_1588_TSU3_))) {
> lan8814_handle_ptp_interrupt(phydev);
> - else
> + ret = IRQ_HANDLED;
> + } else {
> break;
> + }
> }
> - return IRQ_HANDLED;
> +
> + return ret;
> }
>
> static int lan8814_ack_interrupt(struct phy_device *phydev)
> --
> 2.30.2
>
--
/Horatiu
next prev parent reply other threads:[~2022-09-21 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 14:16 [PATCH net] net: phy: micrel: fix shared interrupt on LAN8814 Michael Walle
2022-09-20 15:44 ` Andrew Lunn
2022-09-21 6:40 ` Horatiu Vultur [this message]
2022-09-21 6:49 ` Divya.Koppera
2022-09-22 14:10 ` patchwork-bot+netdevbpf
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=20220921064019.at4pbog6d2gzjyjq@soft-dev3-1.localhost \
--to=horatiu.vultur@microchip.com \
--cc=Divya.Koppera@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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