diff options
author | Russell King <rmk+kernel@arm.linux.org.uk> | 2015-07-24 12:21:02 +0300 |
---|---|---|
committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2015-08-11 20:45:00 +0300 |
commit | efaa6e266ba70439da00e7f1c8a218e243ae140a (patch) | |
tree | bd7d7d35ba8575eccfcc01d2338e2a91c8357ff5 /drivers/firmware | |
parent | 21caf3a765b0a88f8fedf63b36e5d15683b73fe5 (diff) | |
download | linux-efaa6e266ba70439da00e7f1c8a218e243ae140a.tar.xz |
firmware: qcom_scm-32: replace open-coded call to __cpuc_flush_dcache_area()
Rathe rthan directly accessing architecture internal functions, provide
an "method"-centric wrapper for qcom_scm-32 to do what's necessary to
ensure that the secure monitor can see the data. This is called
"secure_flush_area" and ensures that the specified memory area is
coherent across the secure boundary.
Acked-by: Andy Gross <agross@codeaurora.org>
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'drivers/firmware')
-rw-r--r-- | drivers/firmware/qcom_scm-32.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/drivers/firmware/qcom_scm-32.c b/drivers/firmware/qcom_scm-32.c index 1bd6f9c34331..29e6850665eb 100644 --- a/drivers/firmware/qcom_scm-32.c +++ b/drivers/firmware/qcom_scm-32.c @@ -24,7 +24,6 @@ #include <linux/err.h> #include <linux/qcom_scm.h> -#include <asm/outercache.h> #include <asm/cacheflush.h> #include "qcom_scm.h" @@ -219,8 +218,7 @@ static int __qcom_scm_call(const struct qcom_scm_command *cmd) * Flush the command buffer so that the secure world sees * the correct data. */ - __cpuc_flush_dcache_area((void *)cmd, cmd->len); - outer_flush_range(cmd_addr, cmd_addr + cmd->len); + secure_flush_area(cmd, cmd->len); ret = smc(cmd_addr); if (ret < 0) |