mfd: cros_ec: stop calling ->cmd_xfer() directly
Instead of having users of the ChromeOS EC call the interface-specific cmd_xfer() callback directly, introduce a central cros_ec_cmd_xfer() to use instead. This will allow us to put all the locking and retry logic in one place instead of duplicating it across the different drivers. Signed-off-by:Andrew Bresticker <abrestic@chromium.org> Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Javier Martinez Canillas <javier.martinez@collabora.co.uk> Reviewed-by:
Doug Anderson <dianders@chromium.org> Signed-off-by:
Lee Jones <lee.jones@linaro.org>
Showing
- drivers/i2c/busses/i2c-cros-ec-tunnel.c 1 addition, 1 deletiondrivers/i2c/busses/i2c-cros-ec-tunnel.c
- drivers/input/keyboard/cros_ec_keyb.c 1 addition, 1 deletiondrivers/input/keyboard/cros_ec_keyb.c
- drivers/mfd/cros_ec.c 7 additions, 0 deletionsdrivers/mfd/cros_ec.c
- include/linux/mfd/cros_ec.h 18 additions, 6 deletionsinclude/linux/mfd/cros_ec.h
Loading
Please register or sign in to comment