On Wed, Jan 15, 2020 at 03:15:26PM +0200, Felipe Balbi wrote: > > Hi Greg, > > Minas Harutyunyan <Minas.Harutyunyan@xxxxxxxxxxxx> writes: > > > On 11/20/2019 2:15 PM, Lukas Wunner wrote: > >> The original dwc_otg driver used a DWC_WORKQ_SCHEDULE() wrapper to queue > >> work items. Because that wrapper acquired the driver's global spinlock, > >> an unlock/lock dance was necessary whenever a work item was queued up > >> while the global spinlock was already held. > >> > >> The dwc2 driver dropped DWC_WORKQ_SCHEDULE() in favor of a direct call > >> to queue_work(), but retained the (now gratuitous) unlock/lock dance in > >> dwc2_handle_conn_id_status_change_intr(). Drop it. > >> > >> Signed-off-by: Lukas Wunner <lukas@xxxxxxxxx> > >> --- > > > > Acked-by: Minas Harutyunyan <hminas@xxxxxxxxxxxx> > > Do you mind picking this one up as a patch? > > Acked-by: Felipe Balbi <balbi@xxxxxxxxxx> > > ps: if you don't have the patch anymore, I can dig it up and resend with > all appropriate acked-by tags. I can take it, thanks. greg k-h
