From: Lee Jones <lee.jones@linaro.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: groeck@chromium.org, gwendal@chromium.org, kernel@collabora.com,
bleung@chromium.org, linux-kernel@vger.kernel.org,
Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [PATCH 1/2] mfd: cros_ec: instantiate properly CrOS FP MCU device
Date: Tue, 2 Apr 2019 05:01:37 +0100 [thread overview]
Message-ID: <20190402040137.GK4187@dell> (raw)
In-Reply-To: <20190307175253.14785-2-enric.balletbo@collabora.com>
On Thu, 07 Mar 2019, Enric Balletbo i Serra wrote:
> From: Vincent Palatin <vpalatin@chromium.org>
>
> Support Fingerprint MCU as a special of CrOS EC devices. The current FP
> MCU uses the same EC SPI protocol v3 as other CrOS EC devices on a SPI
> bus.
>
> When a MCU has fingerprint support (aka EC_FEATURE_FINGERPRINT), it is
> instantiated as a special CrOS EC device with device name 'cros_fp'. So
> regardless of the probing order between the actual cros_ec and cros_fp,
> the userspace and other kernel drivers should not confuse them.
>
> Signed-off-by: Vincent Palatin <vpalatin@chromium.org>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
>
> drivers/mfd/cros_ec_dev.c | 10 ++++++++++
> include/linux/mfd/cros_ec.h | 1 +
> 2 files changed, 11 insertions(+)
Applied, thanks.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2019-04-02 4:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 17:52 [PATCH 0/2] mfd: cros_ec: instantiate CrOS FP and TP devices Enric Balletbo i Serra
2019-03-07 17:52 ` [PATCH 1/2] mfd: cros_ec: instantiate properly CrOS FP MCU device Enric Balletbo i Serra
2019-04-02 4:01 ` Lee Jones [this message]
2019-04-03 3:27 ` Lee Jones
2019-03-07 17:52 ` [PATCH 2/2] mfd: cros_ec: instantiate properly CrOS Touchpad " Enric Balletbo i Serra
2019-04-02 4:01 ` Lee Jones
2019-04-03 3:27 ` Lee Jones
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=20190402040137.GK4187@dell \
--to=lee.jones@linaro.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vpalatin@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;
as well as URLs for NNTP newsgroup(s).