From: patchwork-bot+chrome-platform@kernel.org
To: Patryk Duda <pdk@semihalf.com>
Cc: bleung@chromium.org, groeck@chromium.org, gwendal@google.com,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
upstream@semihalf.com
Subject: Re: [PATCH v1] platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure
Date: Mon, 15 Aug 2022 03:55:28 +0000 [thread overview]
Message-ID: <166053572854.30867.16514927913447252293.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220802154128.21175-1-pdk@semihalf.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Tue, 2 Aug 2022 17:41:28 +0200 you wrote:
> Some EC based devices (e.g. Fingerpint MCU) can jump to RO part of the
> firmware (intentionally or due to device reboot). The RO part doesn't
> change during the device lifecycle, so it won't support newer version
> of EC_CMD_GET_NEXT_EVENT command.
>
> Function cros_ec_query_all() is responsible for finding maximum
> supported MKBP event version. It's usually called when the device is
> running RW part of the firmware, so the command version can be
> potentially higher than version supported by the RO.
>
> [...]
Here is the summary with links:
- [v1] platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure
https://git.kernel.org/chrome-platform/c/f74c7557ed0d
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-08-15 3:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 16:09 [PATCH] platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure Patryk Duda
2022-07-14 16:31 ` Guenter Roeck
2022-07-18 3:20 ` Tzung-Bi Shih
2022-08-02 15:41 ` [PATCH v1] " Patryk Duda
2022-08-04 9:00 ` Tzung-Bi Shih
2022-08-04 10:59 ` Patryk Duda
2022-08-05 2:40 ` patchwork-bot+chrome-platform
2022-08-15 3:44 ` patchwork-bot+chrome-platform
2022-08-15 3:55 ` 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=166053572854.30867.16514927913447252293.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=gwendal@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pdk@semihalf.com \
--cc=upstream@semihalf.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.