All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Roger Quadros <rogerq@kernel.org>
Subject: Re: [PATCH 2/2] usb: dwc3: core: Prevent phy suspend during init
Date: Tue, 29 Oct 2024 22:49:14 +0000	[thread overview]
Message-ID: <20241029224900.by3zglncf33izsgw@synopsys.com> (raw)
In-Reply-To: <CADcbR4KhWdXpynk2c-tryx1=Eg4LhC4t=C6zcVHAMcMz2hH-8Q@mail.gmail.com>

Hi,

On Tue, Oct 29, 2024, Chris Morgan wrote:
> Sorry, to be specific it was the fix that causes the issues I'm now
> observing. When I explicitly revert commit
> 705e3ce37bccdf2ed6f848356ff355f480d51a91 things start working again
> for me. With that commit in place, however, suspend fails for me.

Ok, Roger's patch is causing issue on your platform and the $subject
patch? Can you provide more details on your test sequence?

* What does "no longer able to suspend" mean exactly (what error?)
* What mode is your usb controller?
* Is there any device connected while going into suspend?
* Can you provide dwc3 regdump?

Thanks,
Thinh

> 
> On Fri, Oct 25, 2024 at 5:40 PM Thinh Nguyen <Thinh.Nguyen@synopsys.com> wrote:
> >
> > Hi,
> >
> > On Fri, Oct 25, 2024, Chris Morgan wrote:
> > >
> > > This patch seems to break system suspend on at least the Rockchip
> > > RK3566 platform. I noticed that I was no longer able to suspend
> > > and git bisect led me to this patch.
> > >
> > > My kernel message log shows the following, at which point it freezes
> > > and does not allow me to resume from suspend:
> > >
> > > [   27.235049] PM: suspend entry (deep)
> > > [   27.871641] Filesystems sync: 0.636 seconds
> > > [   27.885320] Freezing user space processes
> > > [   27.886932] Freezing user space processes completed (elapsed 0.001 seconds)
> > > [   27.887642] OOM killer disabled.
> > > [   27.887981] Freezing remaining freezable tasks
> > > [   27.889655] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
> > >
> > > Thank you,
> > > Chris
> >
> > Did you try out Roger's fix?
> > 705e3ce37bcc ("usb: dwc3: core: Fix system suspend on TI AM62 platforms")
> >
> > https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=705e3ce37bccdf2ed6f848356ff355f480d51a91__;!!A4F2R9G_pg!ZXQdR2uLykSD67_3JSm0RZHuyJ7IVnw5EvmYvLnPsf3dDEilv5ZgHD9GX7gZr52t0H7oFKifzAEhbdK8EGYzmSji2UI$ 
> >
> > BR,
> > Thinh

  parent reply	other threads:[~2024-10-29 22:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-16 23:41 [PATCH 0/2] usb: dwc3: Disable susphy during initialization Thinh Nguyen
2024-04-16 23:41 ` [PATCH 1/2] usb: xhci-plat: Don't include xhci.h Thinh Nguyen
2024-04-17 10:58   ` kernel test robot
2024-04-17 11:08   ` Greg Kroah-Hartman
2024-04-17 21:01     ` Thinh Nguyen
2024-04-16 23:41 ` [PATCH 2/2] usb: dwc3: core: Prevent phy suspend during init Thinh Nguyen
2024-09-25  7:50   ` Roger Quadros
2024-09-26 21:51     ` Thinh Nguyen
2024-09-27  9:52       ` Roger Quadros
2024-10-01  1:00         ` Thinh Nguyen
2024-10-01  7:52           ` Roger Quadros
2024-10-25 19:20     ` Chris Morgan
2024-10-25 19:20       ` Chris Morgan
2024-10-25 22:40       ` Thinh Nguyen
2024-10-25 22:40         ` Thinh Nguyen
     [not found]         ` <CADcbR4KhWdXpynk2c-tryx1=Eg4LhC4t=C6zcVHAMcMz2hH-8Q@mail.gmail.com>
2024-10-29 22:49           ` Thinh Nguyen [this message]
2024-10-30 13:10             ` Roger Quadros
2024-10-30 20:06               ` Chris Morgan
2024-10-31  1:33                 ` Thinh Nguyen
2024-11-07 18:50                   ` Chris Morgan
2024-11-07 19:02                     ` Roger Quadros
2024-11-13 19:30                       ` Chris Morgan
2024-11-14  2:35                     ` Thinh Nguyen
2024-11-19 19:51                       ` Chris Morgan
2024-11-19 22:19                         ` Thinh Nguyen

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=20241029224900.by3zglncf33izsgw@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=macroalpha82@gmail.com \
    --cc=rogerq@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.