Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <50b82871-6308-21e1-77db-0c8793df196d@kernel.org>
Date:   Wed, 2 Aug 2023 17:34:22 +0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.13.0
Subject: Re: [PATCH] usb: dwc3: Properly handle processing of pending events
To:     Elson Roy Serrao <quic_eserrao@quicinc.com>,
        Thinh.Nguyen@synopsys.com, gregkh@linuxfoundation.org,
        felipe.balbi@linux.intel.com, surong.pang@unisoc.com
Cc:     linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
        quic_wcheng@quicinc.com, quic_jackp@quicinc.com,
        stable@vger.kernel.org
References: <20230801192658.19275-1-quic_eserrao@quicinc.com>
Content-Language: en-US
From:   Roger Quadros <rogerq@kernel.org>
In-Reply-To: <20230801192658.19275-1-quic_eserrao@quicinc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 01/08/2023 22:26, 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>

Reviewed-by: Roger Quadros <rogerq@kernel.org>