diff options
| author | Heinrich Schuchardt <xypron.glpk@gmx.de> | 2020-11-09 21:34:25 +0100 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-11-14 15:23:41 -0700 |
| commit | a3e458524c15710e4ac9ce1556a5f0898084d09a (patch) | |
| tree | c433f9abf09a77a11504670ccdb3dc6fbf3507bb /drivers/ddr/imx/imx8m/ddr_init.c | |
| parent | 4cb862fe28332f187f636b37b48fb0fbaf3432ec (diff) | |
| download | u-boot-a3e458524c15710e4ac9ce1556a5f0898084d09a.tar.gz u-boot-a3e458524c15710e4ac9ce1556a5f0898084d09a.tar.xz u-boot-a3e458524c15710e4ac9ce1556a5f0898084d09a.zip | |
cros_ec: Handling EC_CMD_GET_NEXT_EVENT
With commit 690079767803 ("cros_ec: Support keyboard scanning with
EC_CMD_GET_NEXT_EVENT") check_for_keys() tries to read keyboard
strokes using EC_CMD_GET_NEXT_EVENT. But the sandbox driver does
not understand this command. We need to reply with
-EC_RES_INVALID_COMMAND to force check_for_keys() to fall back to
use EC_CMD_MKBP_STATE. Currently the driver prints
** Unknown EC command 0x67
in this case. With the patch the message is suppressed.
In a future patch we should upgrade the sandbox driver to provide
EC_CMD_GET_NEXT_EVENT support.
Fixes: 690079767803 ("cros_ec: Support keyboard scanning with EC_CMD_GET_NEXT_EVENT")
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Diffstat (limited to 'drivers/ddr/imx/imx8m/ddr_init.c')
0 files changed, 0 insertions, 0 deletions