From: Andrew Lunn <andrew@lunn.ch>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH net V2 1/4] net: vertexcom: mse102x: Fix possible stuck of SPI interrupt
Date: Wed, 30 Apr 2025 15:48:27 +0200 [thread overview]
Message-ID: <665ef5b5-1802-47e8-a97a-972304c5ceb9@lunn.ch> (raw)
In-Reply-To: <20250430133043.7722-2-wahrenst@gmx.net>
On Wed, Apr 30, 2025 at 03:30:40PM +0200, Stefan Wahren wrote:
> The MSE102x doesn't provide any SPI commands for interrupt handling.
> So in case the interrupt fired before the driver requests the IRQ,
> the interrupt will never fire again. In order to fix this always poll
> for pending packets after opening the interface.
>
> Fixes: 2f207cbf0dd4 ("net: vertexcom: Add MSE102x SPI support")
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2025-04-30 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 13:30 [PATCH net V2 0/4] net: vertexcom: mse102x: Fix RX handling Stefan Wahren
2025-04-30 13:30 ` [PATCH net V2 1/4] net: vertexcom: mse102x: Fix possible stuck of SPI interrupt Stefan Wahren
2025-04-30 13:48 ` Andrew Lunn [this message]
2025-04-30 13:30 ` [PATCH net V2 2/4] net: vertexcom: mse102x: Fix LEN_MASK Stefan Wahren
2025-04-30 13:47 ` Andrew Lunn
2025-04-30 13:30 ` [PATCH net V2 3/4] net: vertexcom: mse102x: Add range check for CMD_RTS Stefan Wahren
2025-04-30 13:47 ` Andrew Lunn
2025-04-30 13:30 ` [PATCH net V2 4/4] net: vertexcom: mse102x: Fix RX error handling Stefan Wahren
2025-04-30 13:47 ` Andrew Lunn
2025-04-30 14:27 ` Stefan Wahren
2025-05-01 14:40 ` [PATCH net V2 0/4] net: vertexcom: mse102x: Fix RX handling 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=665ef5b5-1802-47e8-a97a-972304c5ceb9@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=wahrenst@gmx.net \
/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).