summaryrefslogtreecommitdiff
path: root/include/linux/platform_data/cros_ec_proto.h
diff options
context:
space:
mode:
authorPrashant Malani <pmalani@chromium.org>2021-10-04 20:07:09 +0300
committerBenson Leung <bleung@chromium.org>2021-11-01 01:52:39 +0300
commit7ff22787ba49c2e66dcec92f3e2b79ef6b6a0d71 (patch)
tree78be3c7703e7f4caed87987ba43b970c808944ac /include/linux/platform_data/cros_ec_proto.h
parent3119c28634ddc6ee3813778d9d17741baceef19d (diff)
downloadlinux-7ff22787ba49c2e66dcec92f3e2b79ef6b6a0d71.tar.xz
platform/chrome: cros_ec_proto: Use EC struct for features
The Chrome EC's features are returned through an ec_response_get_features struct, but they are stored in an independent array. Although the two are effectively the same at present (2 unsigned 32 bit ints), there is the possibility that they could go out of sync. Avoid this by only using the EC struct to store the features. Signed-off-by: Prashant Malani <pmalani@chromium.org> Link: https://lore.kernel.org/r/20211004170716.86601-1-pmalani@chromium.org Signed-off-by: Benson Leung <bleung@chromium.org>
Diffstat (limited to 'include/linux/platform_data/cros_ec_proto.h')
-rw-r--r--include/linux/platform_data/cros_ec_proto.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/platform_data/cros_ec_proto.h b/include/linux/platform_data/cros_ec_proto.h
index 9d370816a419..df3c78c92ca2 100644
--- a/include/linux/platform_data/cros_ec_proto.h
+++ b/include/linux/platform_data/cros_ec_proto.h
@@ -205,7 +205,7 @@ struct cros_ec_dev {
struct cros_ec_debugfs *debug_info;
bool has_kb_wake_angle;
u16 cmd_offset;
- u32 features[2];
+ struct ec_response_get_features features;
};
#define to_cros_ec_dev(dev) container_of(dev, struct cros_ec_dev, class_dev)