All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] arm64: dts: renesas: add full-pwr-cycle-in-suspend into eMMC nodes
Date: Fri, 17 Jul 2020 12:33:07 +0000	[thread overview]
Message-ID: <TY2PR01MB36921E2FC932E95E6C8E46CAD87C0@TY2PR01MB3692.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdUkzNx2nUrRN+0bny6BG95YVNqUiWN2L+BXsOD_o-=Vfg@mail.gmail.com>

Hi Geert-san,

> From: Geert Uytterhoeven, Sent: Friday, July 17, 2020 7:07 PM
<snip>
> > > > However, PMIC on ULCB cannot control the KF power unfortunately.
> > > > So, we have no chance to use s2ram on ULCB+KF...
> > >
> > > Makes sense.
> > > BTW, what happens if you try s2ram? I guess the system just wakes up again
> > > immediately? Or does it crash?
> >
> > It's frozen after s2ram. Some LEDs on ULCB is OFF. But, LEDs on KF is still ON.
> 
> Oops.
> 
> > So, I'm wondering if it's better to add the property on ULCB+KF too
> > because it seems ULCB is turned off. But, what do you think?
> 
> IMHO, a graceful shutdown is better.

Thank you for your opinion. I think so. So, I'll submit a patch.

Best regards,
Yoshihiro Shimoda


      reply	other threads:[~2020-07-17 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 12:03 [PATCH] arm64: dts: renesas: add full-pwr-cycle-in-suspend into eMMC nodes Yoshihiro Shimoda
2020-07-15  9:04 ` Geert Uytterhoeven
2020-07-17  5:44   ` Yoshihiro Shimoda
2020-07-17  7:12     ` Geert Uytterhoeven
2020-07-17  8:29       ` Yoshihiro Shimoda
2020-07-17  8:35         ` Geert Uytterhoeven
2020-07-17 10:01           ` Yoshihiro Shimoda
2020-07-17 10:07             ` Geert Uytterhoeven
2020-07-17 12:33               ` Yoshihiro Shimoda [this message]

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=TY2PR01MB36921E2FC932E95E6C8E46CAD87C0@TY2PR01MB3692.jpnprd01.prod.outlook.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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.