On Tue, Jun 18, 2024 at 12:05:05AM +0000, Thinh Nguyen wrote: > On Thu, Jun 13, 2024, joswang wrote: > > On Thu, Jun 13, 2024 at 1:04 AM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > > > On Wed, Jun 12, 2024 at 11:39:22PM +0800, joswang wrote: > > > > From: Jos Wang <joswang@xxxxxxxxxx> > > > > > > > > This is a workaround for STAR 4846132, which only affects > > > > DWC_usb31 version2.00a operating in host mode. > > > > > > > > There is a problem in DWC_usb31 version 2.00a operating > > > > in host mode that would cause a CSR read timeout When CSR > > > > read coincides with RAM Clock Gating Entry. By disable > > > > Clock Gating, sacrificing power consumption for normal > > > > operation. > > > > > > > > Cc: stable@xxxxxxxxxxxxxxx > > > > Signed-off-by: Jos Wang <joswang@xxxxxxxxxx> > > > > --- > > > > v1 -> v2: > > > > - add "dt-bindings: usb: dwc3: Add snps,p2p3tranok quirk" patch, > > > > this patch does not make any changes > > > > v2 -> v3: > > > > - code refactor > > > > - modify comment, add STAR number, workaround applied in host mode > > > > - modify commit message, add STAR number, workaround applied in host mode > > > > - modify Author Jos Wang > > > > v3 -> v4: > > > > - modify commit message, add Cc: stable@xxxxxxxxxxxxxxx > > > > > > This thread is crazy, look at: > > > https://urldefense.com/v3/__https://lore.kernel.org/all/20240612153922.2531-1-joswang1221@xxxxxxxxx/__;!!A4F2R9G_pg!a29V9NsG_rMKPnub-JtIe5I_lAoJmzK8dgo3UK-qD_xpT_TOgyPb6LkEMkIsijsDKIgdxB_QVLW_MwtdQLnyvOujOA$ > > > for how it looks. How do I pick out the proper patches to review/apply > > > there at all? What would you do if you were in my position except just > > > delete the whole thing? > > > > > > Just properly submit new versions of patches (hint, without the ','), as > > > the documentation file says to, as new threads each time, with all > > > commits, and all should be fine. > > > > > > We even have tools that can do this for you semi-automatically, why not > > > use them? > > > > > > thanks, > > > > > > greg k-h > > > > We apologize for any inconvenience this may cause. > > The following incorrect operation caused the problem you mentioned: > > git send-email --in-reply-to command sends the new version patch > > git format-patch --subject-prefix='PATCH v3 > > > > Should I resend the v5 patch now? > > Please send this as a stand-alone patch outside of the series as v5. (ie. > remove the "3/3"). I still need to review the other issue of the series. > > Thanks, > Thinh Hi Thinh, We faced similar issue on DRD mode operating as device. Could you check it internally? Case: 01635304 Best Regards, Jung Daehwan
