Linux USB
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Joseph Telaak" <joseph@telaak.dev>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 3/3] usb: dwc2: Handle OTG interrupts that GINTSTS does not flag
Date: Wed, 11 Nov 2026 08:34:31 +0000	[thread overview]
Message-ID: <sashiko-outbox-208616@kernel.org> (raw)
In-Reply-To: <20261111-sf19a2890-dwc2-v2-3-cba9dd4a4256@telaak.dev>

> From: Chuanhong Guo <gch981213@gmail.com>
> 
> The DWC OTG 3.30a of the Siflower SF19A2890 has battery charger support
> enabled. It raises the MultValIpChng interrupt (bit 20 of GOTGINT)
> without setting OTGInt in GINTSTS, so the interrupt is never handled
> and the kernel disables the USB interrupt because nobody cared.
> 
> On a GL.iNet GL-SFT1200 it shows differently: after a few replugs of a
> USB stick the system stops making progress, the console repeating its
> last message with the same timestamp, until a power cycle.
> 
> Add an otg_int_unflagged parameter for such cores. With it set, the
> common interrupt handler also reads GOTGINT on every interrupt and
> handles any OTG interrupt it finds there, as it does when OTGInt is
> set. The SF19A2890 sets it; other cores are unchanged.
> 
> Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
> [Joseph Telaak:
>   - handle the unflagged OTG interrupts only on cores with the new
>     otg_int_unflagged parameter, which the SF19A2890 sets
>   - do it in the one place that already handles flagged OTG
>     interrupts, and return IRQ_HANDLED
>   - describe what a GL-SFT1200 does without the patch, and the fix as
>     it is now
>   - subject]
> Co-developed-by: Joseph Telaak <joseph@telaak.dev>
> Signed-off-by: Joseph Telaak <joseph@telaak.dev>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111-sf19a2890-dwc2-v2-0-cba9dd4a4256@telaak.dev?part=3


      reply	other threads:[~2026-11-11  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  8:26 [PATCH v2 0/3] usb: dwc2: Add Siflower SF19A2890 support Joseph Telaak via B4 Relay
2026-11-11  8:26 ` [PATCH v2 1/3] dt-bindings: usb: dwc2: Add Siflower SF19A2890 Joseph Telaak via B4 Relay
2026-11-11  8:29   ` sashiko-bot
2026-11-11  8:26 ` [PATCH v2 2/3] usb: dwc2: Add Siflower SF19A2890 support Joseph Telaak via B4 Relay
2026-11-11  8:30   ` sashiko-bot
2026-11-11  8:26 ` [PATCH v2 3/3] usb: dwc2: Handle OTG interrupts that GINTSTS does not flag Joseph Telaak via B4 Relay
2026-11-11  8:34   ` sashiko-bot [this message]

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=sashiko-outbox-208616@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=joseph@telaak.dev \
    --cc=linux-usb@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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