From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Prashant Malani <pmalani@chromium.org>
Cc: Evan Green <evgreen@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Rajat Jain <rajatja@chromium.org>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
Tinghan Shen <tinghan.shen@mediatek.com>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] platform/chrome: cros_ec: Expose suspend_timeout_ms in debugfs
Date: Mon, 22 Aug 2022 05:55:58 +0000 [thread overview]
Message-ID: <YwMabj1HazWxJEAr@google.com> (raw)
In-Reply-To: <CACeCKafyHSTiyyjA=yjSXsTub4kKECfe9gp=y10LCYYx0nGKqg@mail.gmail.com>
On Thu, Aug 18, 2022 at 10:24:23AM -0700, Prashant Malani wrote:
> On Thu, Aug 18, 2022 at 8:29 AM Evan Green <evgreen@chromium.org> wrote:
> > diff --git a/Documentation/ABI/testing/debugfs-cros-ec b/Documentation/ABI/testing/debugfs-cros-ec
> > index 1fe0add99a2a99..9f79c641b2d09f 100644
> > --- a/Documentation/ABI/testing/debugfs-cros-ec
> > +++ b/Documentation/ABI/testing/debugfs-cros-ec
> > @@ -54,3 +54,25 @@ Description:
> > this feature.
> >
> > Output will be in the format: "0x%08x\n".
> > +
> > +What: /sys/kernel/debug/<cros-ec-device>/suspend_timeout_ms
> > +Date: August 2022
> > +KernelVersion: 6.1
> > +Description:
> > + Some ECs have a feature where they will track transitions to the
> > + a hardware-controlled sleep line, such as Intel's SLP_S0 line,
> > + in order to detect cases where a system failed to go into deep
> > + sleep states. The suspend_timeout file controls the amount of
> s/suspend_timeout/suspend_timeout_ms
Please also fix it in code.
prev parent reply other threads:[~2022-08-22 5:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 15:29 [PATCH v2] platform/chrome: cros_ec: Expose suspend_timeout_ms in debugfs Evan Green
2022-08-18 17:24 ` Prashant Malani
2022-08-22 5:55 ` 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=YwMabj1HazWxJEAr@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=enric.balletbo@collabora.com \
--cc=evgreen@chromium.org \
--cc=groeck@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=rajatja@chromium.org \
--cc=tinghan.shen@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox