From: patchwork-bot+chrome-platform@kernel.org
To: Evan Green <evgreen@chromium.org>
Cc: enric.balletbo@collabora.com, rajatja@chromium.org,
tzungbi@kernel.org, pmalani@chromium.org, bleung@chromium.org,
groeck@chromium.org, swboyd@chromium.org,
tinghan.shen@mediatek.com, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] platform/chrome: cros_ec: Expose suspend_timeout_ms in debugfs
Date: Thu, 01 Sep 2022 06:10:15 +0000 [thread overview]
Message-ID: <166201261565.19499.13279079170676259889.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822144026.v3.1.Idd188ff3f9caddebc17ac357a13005f93333c21f@changeid>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Mon, 22 Aug 2022 14:40:40 -0700 you wrote:
> In modern Chromebooks, the embedded controller has a mechanism where
> it will watch a hardware-controlled line that toggles in suspend, and
> wake the system up if an expected sleep transition didn't occur. This
> can be very useful for detecting power management issues where the
> system appears to suspend, but doesn't actually reach its lowest
> expected power states.
>
> [...]
Here is the summary with links:
- [v3] platform/chrome: cros_ec: Expose suspend_timeout_ms in debugfs
https://git.kernel.org/chrome-platform/c/e8bf17d58a4d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-09-01 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 21:40 [PATCH v3] platform/chrome: cros_ec: Expose suspend_timeout_ms in debugfs Evan Green
2022-08-22 22:58 ` Stephen Boyd
2022-08-22 23:23 ` Guenter Roeck
2022-08-24 2:40 ` patchwork-bot+chrome-platform
2022-09-01 6:10 ` patchwork-bot+chrome-platform [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=166201261565.19499.13279079170676259889.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@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=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=rajatja@chromium.org \
--cc=swboyd@chromium.org \
--cc=tinghan.shen@mediatek.com \
--cc=tzungbi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox