summaryrefslogtreecommitdiff
path: root/drivers/tee
diff options
context:
space:
mode:
authorJorge Ramirez-Ortiz <jorge@foundries.io>2020-08-31 19:11:02 +0300
committerJens Wiklander <jens.wiklander@linaro.org>2020-09-01 13:03:16 +0300
commit539f8fc253ece5501fdea1a6aa227d0618374111 (patch)
tree21b0f582054c14fbadd139abcf6220660b90a1a0 /drivers/tee
parentc05210ab975771e161427eb47696b869d820bdaf (diff)
downloadlinux-539f8fc253ece5501fdea1a6aa227d0618374111.tar.xz
drivers: optee: fix i2c build issue
When the optee driver is compiled into the kernel while the i2c core is configured as a module, the i2c symbols are not available. This commit addresses the situation by disabling the i2c support for this use case while allowing it in all other scenarios: i2c=y, optee=y i2c=m, optee=m i2c=y, optee=m i2c=m, optee=y (not supported) Fixes: c05210ab9757 ("drivers: optee: allow op-tee to access devices on the i2c bus") Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
Diffstat (limited to 'drivers/tee')
-rw-r--r--drivers/tee/optee/rpc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/tee/optee/rpc.c b/drivers/tee/optee/rpc.c
index 64a206c56264..1e3614e4798f 100644
--- a/drivers/tee/optee/rpc.c
+++ b/drivers/tee/optee/rpc.c
@@ -50,7 +50,7 @@ bad:
arg->ret = TEEC_ERROR_BAD_PARAMETERS;
}
-#if IS_ENABLED(CONFIG_I2C)
+#if IS_REACHABLE(CONFIG_I2C)
static void handle_rpc_func_cmd_i2c_transfer(struct tee_context *ctx,
struct optee_msg_arg *arg)
{