mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prashanth K <prashanth.k@oss.qualcomm.com>
To: Kyle Tso <kyletso@google.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: gadget: Move vbus draw to workqueue context
Date: Wed, 4 Feb 2026 09:47:16 +0530	[thread overview]
Message-ID: <e94b8434-09ff-4ea0-a762-0869345aab4e@oss.qualcomm.com> (raw)
In-Reply-To: <CAGZ6i=3ZJ3aihjmXnPq9C-mpVYa6rqzfWTn3qXmavYUiZtE24A@mail.gmail.com>



On 2/4/2026 9:29 AM, Kyle Tso wrote:
> On Thu, Jan 29, 2026 at 7:16 PM Prashanth K
> <prashanth.k@oss.qualcomm.com> wrote:
>>
>> Currently dwc3_gadget_vbus_draw() can be called from atomic
>> context, which in turn invokes power-supply-core APIs. And
>> some these PMIC APIs have operations that may sleep, leading
>> to kernel panic.
>>
>> Fix this by moving the vbus_draw into a workqueue context.
>>
>> Fixes: 66e0ea341a2a ("usb: dwc3: core: Defer the probe until USB power supply ready")
> 
> I think the following patch is the one to fix:
> 
> https://lore.kernel.org/all/20210222115149.3606776-3-raychi@google.com/
> 

Yes agreed, i added 66e0ea341a2a because it can be backported without
conflicts only till 66e0ea341a2a, but I'll change it to the correct one.

Thanks for confirming,
Prashanth K


      reply	other threads:[~2026-02-04  4:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 11:14 Prashanth K
2026-01-31 20:14 ` Samuel Wu
2026-02-03  0:04 ` Thinh Nguyen
2026-02-04  3:59 ` Kyle Tso
2026-02-04  4:17   ` Prashanth K [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=e94b8434-09ff-4ea0-a762-0869345aab4e@oss.qualcomm.com \
    --to=prashanth.k@oss.qualcomm.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kyletso@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®