patches.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Benson Leung <bleung@chromium.org>,
	linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	Guenter Roeck <groeck@chromium.org>,
	chrome-platform@lists.linux.dev,
	Evan Green <evgreen@chromium.org>,
	Rajat Jain <rajatja@chromium.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	Hsin-Yi Wang <hsinyi@chromium.org>
Subject: Re: [PATCH v2] platform/chrome: cros_ec: Always expose last resume result
Date: Tue, 14 Jun 2022 06:30:44 +0000	[thread overview]
Message-ID: <YqgrFORv5rMggcLs@google.com> (raw)
In-Reply-To: <CAE-0n53aiXq+eUC0gq=J0kO+_zFpZGnL42AgyEBVM-_wtccnJA@mail.gmail.com>

On Mon, Jun 13, 2022 at 11:17:50PM -0700, Stephen Boyd wrote:
> Quoting Tzung-Bi Shih (2022-06-13 22:30:18)
> > On Fri, Jun 10, 2022 at 11:18:25PM -0700, Stephen Boyd wrote:
> > > @@ -135,10 +135,10 @@ static int cros_ec_sleep_event(struct cros_ec_device *ec_dev, u8 sleep_event)
> > >       buf.msg.command = EC_CMD_HOST_SLEEP_EVENT;
> > >
> > >       ret = cros_ec_cmd_xfer_status(ec_dev, &buf.msg);
> > > -
> > > -     /* For now, report failure to transition to S0ix with a warning. */
> > > +     /* Report failure to transition to system wide suspend with a warning. */
> > >       if (ret >= 0 && ec_dev->host_sleep_v1 &&
> > > -         (sleep_event == HOST_SLEEP_EVENT_S0IX_RESUME)) {
> > > +         (sleep_event == HOST_SLEEP_EVENT_S0IX_RESUME ||
> > > +          sleep_event == HOST_SLEEP_EVENT_S3_RESUME)) {
> > >               ec_dev->last_resume_result =
> > >                       buf.u.resp1.resume_response.sleep_transitions;
> >
> > The warning in the if-block:
> > WARN_ONCE(buf.u.resp1.resume_response.sleep_transitions &
> >           EC_HOST_RESUME_SLEEP_TIMEOUT,
> >           "EC detected sleep transition timeout. Total slp_s0 transitions: %d",
> >           buf.u.resp1.resume_response.sleep_transitions &
> >           EC_HOST_RESUME_SLEEP_TRANSITIONS_MASK);
> >
> > Not sure and I wonder if the term "slp_s0" is still generic enough to the case.
> > And also [1].
> >
> > [1]: https://crrev.com/a311a7657ca0a488f507fa78fd9c2d825cbf083e/power_manager/powerd/system/suspend_configurator.cc#98
> 
> I don't know what "slp_s0" means. I guess it's some intelism? It could
> change to "sleep" and work for me.
> 
> >
> > At least we should fix [2] once the patch landed.
> >
> > [2]: https://crrev.com/a311a7657ca0a488f507fa78fd9c2d825cbf083e/power_manager/tools/suspend_stress_test#369
> 
> And by fix you mean change "S0iX" to "suspend"?

Yes.

      reply	other threads:[~2022-06-14  6:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  6:18 [PATCH v2] platform/chrome: cros_ec: Always expose last resume result Stephen Boyd
2022-06-11 22:01 ` Guenter Roeck
2022-06-13 15:39 ` Evan Green
2022-06-14  5:30 ` Tzung-Bi Shih
2022-06-14  6:17   ` Stephen Boyd
2022-06-14  6:30     ` Tzung-Bi Shih [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=YqgrFORv5rMggcLs@google.com \
    --to=tzungbi@kernel.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=evgreen@chromium.org \
    --cc=groeck@chromium.org \
    --cc=hsinyi@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=patches@lists.linux.dev \
    --cc=rajatja@chromium.org \
    --cc=swboyd@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).