diff options
| author | Bjorn Andersson <bjorn.andersson@linaro.org> | 2017-08-15 01:46:18 +0300 |
|---|---|---|
| committer | Andy Gross <andy.gross@linaro.org> | 2017-10-12 07:48:27 +0300 |
| commit | 8c1b7dc9ba2294c6dbd1870a3d2e534bfda3047a (patch) | |
| tree | 8d9823b880adb03cdf422d6773c720b79c6233e5 /drivers/firmware/qcom_scm-32.c | |
| parent | 4e659dbe2d02a56ca0df25c77e099760252a329c (diff) | |
| download | linux-8c1b7dc9ba2294c6dbd1870a3d2e534bfda3047a.tar.xz | |
firmware: qcom: scm: Expose download-mode control
In order to aid post-mortem debugging the Qualcomm platforms provide a
"memory download mode", where the boot loader will provide an interface
for custom tools to "download" the content of RAM to a host machine.
The mode is triggered by writing a magic value somewhere in RAM, that is
read in the boot code path after a warm-restart. Two mechanism for
setting this magic value are supported in modern platforms; a direct SCM
call to enable the mode or through a secure io write of a magic value.
In order for a normal reboot not to trigger "download mode" the magic
must be cleared during a clean reboot.
Download mode has to be enabled by including qcom_scm.download_mode=1 on
the command line.
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Signed-off-by: Andy Gross <andy.gross@linaro.org>
Diffstat (limited to 'drivers/firmware/qcom_scm-32.c')
| -rw-r--r-- | drivers/firmware/qcom_scm-32.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/drivers/firmware/qcom_scm-32.c b/drivers/firmware/qcom_scm-32.c index 11fdb1584823..68b2033bc30e 100644 --- a/drivers/firmware/qcom_scm-32.c +++ b/drivers/firmware/qcom_scm-32.c @@ -561,6 +561,12 @@ int __qcom_scm_pas_mss_reset(struct device *dev, bool reset) return ret ? : le32_to_cpu(out); } +int __qcom_scm_set_dload_mode(struct device *dev, bool enable) +{ + return qcom_scm_call_atomic2(QCOM_SCM_SVC_BOOT, QCOM_SCM_SET_DLOAD_MODE, + enable ? QCOM_SCM_SET_DLOAD_MODE : 0, 0); +} + int __qcom_scm_set_remote_state(struct device *dev, u32 state, u32 id) { struct { |