public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@kernel.org>
To: "庞苏荣 (Surong Pang)" <surong.pang@unisoc.com>,
	"Thinh Nguyen" <Thinh.Nguyen@synopsys.com>,
	"Elson Roy Serrao" <quic_eserrao@quicinc.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"felipe.balbi@linux.intel.com" <felipe.balbi@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"quic_wcheng@quicinc.com" <quic_wcheng@quicinc.com>,
	"quic_jackp@quicinc.com" <quic_jackp@quicinc.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Properly handle processing of pending events
Date: Wed, 2 Aug 2023 17:37:08 +0300	[thread overview]
Message-ID: <b2ab8803-d4e0-bd63-7a64-bcc411e04cfe@kernel.org> (raw)
In-Reply-To: <2bf3663abc72448da44427dcaedb49fe@shmbx05.spreadtrum.com>

Hi,

On 02/08/2023 04:39, 庞苏荣 (Surong Pang) wrote:
> Dears,
> If there is/are event(s) in evt->buf,  in dwc3_check_event_buf,  dwc3_thread_interrupt will be woke up.

How will it be woken up if we had disabled the IRQ to begin with?

> 
>>> @@ -4718,6 +4723,8 @@ void dwc3_gadget_process_pending_events(struct
>>> dwc3 *dwc)  {
>>>       if (dwc->pending_events) {
>>>               dwc3_interrupt(dwc->irq_gadget, dwc->ev_buf);
>>> +             dwc3_thread_interrupt(dwc->irq_gadget, dwc->ev_buf);
>>> +             pm_runtime_put(dwc->dev);
>>>               dwc->pending_events = false;
>>>               enable_irq(dwc->irq_gadget);
>>>       }
> 
> I just want to know dwc3_thread_interrupt here is necessary or not?
> 
As IRQ was disabled, we will have to call dwc3_thread_interrupt() to
process the events that are still pending.

> 
>> On Tue, Aug 02, 2023 8:12 Thinh Nguyen wrote:
>>> On Tue, Aug 01, 2023, Elson Roy Serrao wrote:
>>> If dwc3 is runtime suspended we defer processing the event buffer
>>> until resume, by setting the pending_events flag. Set this flag before
>>> triggering resume to avoid race with the runtime resume callback.
>>>
>>> While handling the pending events, in addition to checking the event
>>> buffer we also need to process it. Handle this by explicitly calling
>>> dwc3_thread_interrupt(). Also balance the runtime pm get() operation
>>> that triggered this processing.
>>>
>>> Cc: stable@vger.kernel.org
>>> Fixes: fc8bb91bc83e ("usb: dwc3: implement runtime PM")
>>> Signed-off-by: Elson Roy Serrao <quic_eserrao@quicinc.com>
>>> ---
>>> Change separated from below series as an independent fix based on the
>>> earlier discussion
>>> https://urldefense.com/v3/__https://lore.kernel.org/all/be57511d-2005-
>>> a1f5-d5a5-809e71029aec@quicinc.com/__;!!A4F2R9G_pg!YtZ93ALEpDNTCEhf0WE
>>> yB5S090pPlKIKVtjqTOAEJdxdWbl8QG6eiRmlvfivUtD5qjKWWLX2C4fb4W8VAg5w9qasL
>>> uKB$
>>>
>>>  drivers/usb/dwc3/gadget.c | 9 ++++++++-
>>>  1 file changed, 8 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
>>> index 5fd067151fbf..858fe4c299b7 100644
>>> --- a/drivers/usb/dwc3/gadget.c
>>> +++ b/drivers/usb/dwc3/gadget.c
>>> @@ -4455,9 +4455,14 @@ static irqreturn_t dwc3_check_event_buf(struct dwc3_event_buffer *evt)
>>>       u32 count;
>>>
>>>       if (pm_runtime_suspended(dwc->dev)) {
>>> +             dwc->pending_events = true;
>>> +             /*
>>> +              * Trigger runtime resume. The get() function will be balanced
>>> +              * after processing the pending events in dwc3_process_pending
>>> +              * events().
>>> +              */
>>>               pm_runtime_get(dwc->dev);
>>>               disable_irq_nosync(dwc->irq_gadget);
>>> -             dwc->pending_events = true;
>>>               return IRQ_HANDLED;
>>>       }
>>>
>>> @@ -4718,6 +4723,8 @@ void dwc3_gadget_process_pending_events(struct
>>> dwc3 *dwc)  {
>>>       if (dwc->pending_events) {
>>>               dwc3_interrupt(dwc->irq_gadget, dwc->ev_buf);
>>> +             dwc3_thread_interrupt(dwc->irq_gadget, dwc->ev_buf);
>>> +             pm_runtime_put(dwc->dev);
>>>               dwc->pending_events = false;
>>>               enable_irq(dwc->irq_gadget);
>>>       }
>>> --
>>> 2.17.1
>>>
>>
>> This fix is more complete.
>>
>> Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
>>
>> Thanks,
>> Thinh

-- 
cheers,
-roger

  reply	other threads:[~2023-08-02 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02  1:39 [PATCH] usb: dwc3: Properly handle processing of pending events 庞苏荣 (Surong Pang)
2023-08-02 14:37 ` Roger Quadros [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-01 19:26 Elson Roy Serrao
2023-08-02  0:11 ` Thinh Nguyen
2023-08-02 14:34 ` Roger Quadros

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=b2ab8803-d4e0-bd63-7a64-bcc411e04cfe@kernel.org \
    --to=rogerq@kernel.org \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_eserrao@quicinc.com \
    --cc=quic_jackp@quicinc.com \
    --cc=quic_wcheng@quicinc.com \
    --cc=stable@vger.kernel.org \
    --cc=surong.pang@unisoc.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