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>
This commit is contained in:
parent
3119c28634
commit
7ff22787ba
3 changed files with 11 additions and 10 deletions
|
|
@ -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)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue