From: Lee Jones <lee.jones@linaro.org>
To: Yicheng Li <yichengli@chromium.org>
Cc: linux-kernel@vger.kernel.org, bleung@chromium.org,
gwendal@chromium.org, enric.balletbo@collabora.com
Subject: Re: [PATCH v4] mfd / platform: cros_ec: Query EC protocol version if EC transitions between RO/RW
Date: Mon, 16 Dec 2019 10:40:46 +0000 [thread overview]
Message-ID: <20191216104046.GD3601@dell> (raw)
In-Reply-To: <20191125221517.91611-1-yichengli@chromium.org>
On Mon, 25 Nov 2019, Yicheng Li wrote:
> RO and RW of EC may have different EC protocol version. If EC transitions
> between RO and RW, but AP does not reboot (this is true for fingerprint
> microcontroller / cros_fp, but not true for main ec / cros_ec), the AP
> still uses the protocol version queried before transition, which can
> cause problems. In the case of fingerprint microcontroller, this causes
> AP to send the wrong version of EC_CMD_GET_NEXT_EVENT to RO in the
> interrupt handler, which in turn prevents RO to clear the interrupt
> line to AP, in an infinite loop.
>
> Once an EC_HOST_EVENT_INTERFACE_READY is received, we know that there
> might have been a transition between RO and RW, so re-query the protocol.
>
> Signed-off-by: Yicheng Li <yichengli@chromium.org>
> ---
> drivers/platform/chrome/cros_ec.c | 24 +++++++++++++++++++++
> include/linux/platform_data/cros_ec_proto.h | 3 +++
> 2 files changed, 27 insertions(+)
This is not an MFD patch. Please drop it from the subject line.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2019-12-16 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 21:29 [PATCH v2] mfd / platform: cros_ec: Query EC protocol version if EC transitions between RO/RW Yicheng Li
2019-11-25 17:09 ` Enric Balletbo i Serra
2019-11-25 22:08 ` [PATCH v3] " Yicheng Li
2019-11-25 22:15 ` [PATCH v4] " Yicheng Li
2019-11-26 9:56 ` Enric Balletbo i Serra
2019-12-03 19:20 ` Gwendal Grignou
2019-12-16 10:40 ` Lee Jones [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=20191216104046.GD3601@dell \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yichengli@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