[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <OSAPR01MB30895B18E4874231396BFEBED8160@OSAPR01MB3089.jpnprd01.prod.outlook.com>
Date: Wed, 5 Jun 2019 12:09:10 +0000
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
CC: Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RE: rcar_gen3_phy_usb2: unbalanced disables for USB20_VBUS0
Hi Geert-san,
> From: Geert Uytterhoeven, Sent: Wednesday, June 5, 2019 4:03 PM
>
> Hi Shimoda-san,
>
> On Wed, Jun 5, 2019 at 6:06 AM Yoshihiro Shimoda
> <yoshihiro.shimoda.uh@...esas.com> wrote:
> > > From: Geert Uytterhoeven, Sent: Wednesday, June 5, 2019 3:06 AM
> > > Using a tree based on renesas-drivers-2019-06-04-v5.2-rc3, I started seeing
> > > the following warning during a second system suspend (s2idle):
> > <snip>
> > > So far I've seen this on Salvator-X with R-Car H3 ES1.0 or M3-W, and
> > > on Salvator-XS with R-Car M3-N, but not (yet?) on H3 ES2.0.
> >
> > I could reproduce this issue on R-Car H3 ES3.0 with Suspend-to-RAM.
> > # I'm silly but I could not use s2idle that didn't wake up by ravb.
> > # https://elinux.org/R-Car/Boards/Salvator-X#Suspend-to-Idle
>
> With CONFIG_PM_DEBUG=y and CONFIG_PM_TEST_SUSPEND=y, you can use
>
> echo platform > /sys/power/pm_test
>
> to configure the system to wake up from s2idle after 5 seconds.
> This allows to loop s2idle without user intervention.
Thank you for explanation! I could use it on my environment.
Best regards,
Yoshihiro Shimoda
Powered by blists - more mailing lists