From: patchwork-bot+chrome-platform@kernel.org
To: Lalith Rajendran <lalithkraj@chromium.org>
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org,
groeck@chromium.org, rrangel@chromium.org, timvp@chromium.org,
tzungbi@kernel.org, chrome-platform@lists.linux.dev
Subject: Re: [PATCH v4] platform/chrome: cros_ec_lpc: Separate host command and irq disable
Date: Sun, 29 Oct 2023 02:20:21 +0000 [thread overview]
Message-ID: <169854602158.20472.60935674192148715.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231027160221.v4.1.I1725c3ed27eb7cd9836904e49e8bfa9fb0200a97@changeid>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Fri, 27 Oct 2023 16:02:22 -0500 you wrote:
> From: Lalith Rajendran <lalithkraj@chromium.org>
>
> Both cros host command and irq disable were moved to suspend
> prepare stage from late suspend recently. This is causing EC
> to report MKBP event timeouts during suspend stress testing.
> When the MKBP event timeouts happen during suspend, subsequent
> wakeup of AP by EC using MKBP doesn't happen properly. Move the
> irq disabling part back to late suspend stage which is a general
> suggestion from the suspend kernel documentaiton to do irq
> disable as late as possible.
>
> [...]
Here is the summary with links:
- [v4] platform/chrome: cros_ec_lpc: Separate host command and irq disable
https://git.kernel.org/chrome-platform/c/47ea0ddb1f56
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:[~2023-10-29 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 21:02 [PATCH v4] platform/chrome: cros_ec_lpc: Separate host command and irq disable Lalith Rajendran
2023-10-28 3:20 ` patchwork-bot+chrome-platform
2023-10-29 2:20 ` 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=169854602158.20472.60935674192148715.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=lalithkraj@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrangel@chromium.org \
--cc=timvp@chromium.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).