From: Yicheng Li <yichengli@chromium.org>
To: LKML <linux-kernel@vger.kernel.org>, lee.jones@linaro.org
Cc: enric.balletbo@collabora.com, gwendal@chromium.org,
bleung@chromium.org, Yicheng Li <yichengli@chromium.org>,
Guenter Roeck <groeck@chromium.org>
Subject: [PATCH] mfd: cros_ec: Update cros_ec_commands.h
Date: Mon, 8 Jul 2019 11:15:37 -0700 [thread overview]
Message-ID: <20190708181536.2125-1-yichengli@chromium.org> (raw)
Update cros_ec_commands.h to match the fingerprint MCU section in
the current ec_commands.h
Signed-off-by: Yicheng Li <yichengli@chromium.org>
---
include/linux/mfd/cros_ec_commands.h | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/include/linux/mfd/cros_ec_commands.h b/include/linux/mfd/cros_ec_commands.h
index 7ccb8757b79d..98415686cbfa 100644
--- a/include/linux/mfd/cros_ec_commands.h
+++ b/include/linux/mfd/cros_ec_commands.h
@@ -5513,6 +5513,18 @@ struct ec_params_fp_seed {
uint8_t seed[FP_CONTEXT_TPM_BYTES];
} __ec_align4;
+#define EC_CMD_FP_ENC_STATUS 0x0409
+
+/* FP TPM seed has been set or not */
+#define FP_ENC_STATUS_SEED_SET BIT(0)
+
+struct ec_response_fp_encryption_status {
+ /* Used bits in encryption engine status */
+ uint32_t valid_flags;
+ /* Encryption engine status */
+ uint32_t status;
+} __ec_align4;
+
/*****************************************************************************/
/* Touchpad MCU commands: range 0x0500-0x05FF */
--
2.20.1
next reply other threads:[~2019-07-08 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 18:15 Yicheng Li [this message]
2019-07-11 17:17 ` [PATCH] mfd: cros_ec: Update cros_ec_commands.h Gwendal Grignou
2019-07-22 14:15 ` Enric Balletbo i Serra
2019-08-12 7:28 ` Lee Jones
2019-08-21 17:27 ` Enric Balletbo i Serra
2019-08-12 7: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=20190708181536.2125-1-yichengli@chromium.org \
--to=yichengli@chromium.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.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 NNTP newsgroup(s).