summaryrefslogtreecommitdiffstats
path: root/drivers/firmware/Makefile
diff options
context:
space:
mode:
authorStephen Boyd <sboyd@codeaurora.org>2015-10-08 13:34:09 -0500
committerAndy Gross <agross@codeaurora.org>2015-10-14 14:51:40 -0500
commitd0bfd7c9b162612de55ca2d204403b90dc278db6 (patch)
treef3bb0e4ca2aadceab29f0578857683d1ef02633b /drivers/firmware/Makefile
parenta8ddd1b998bdad9489876a3068cc45917bee5441 (diff)
downloadlinux-d0bfd7c9b162612de55ca2d204403b90dc278db6.tar.gz
linux-d0bfd7c9b162612de55ca2d204403b90dc278db6.tar.bz2
linux-d0bfd7c9b162612de55ca2d204403b90dc278db6.zip
soc: qcom: smem: Move RPM message ram out of smem DT node
SMEM is a software construct built on top of a DDR reserved region and sometimes a device memory region called RPM message ram. Having the RPM message ram in the smem DT node's reg property leads to the smem node being located in different places depending on if the message ram is being used or not. Let's add a qcom specific property, qcom,rpm-msg-ram, and point to the device memory from the SMEM node via a phandle. As SMEM is a software construct, it really needs to reside at the root of the DT regardless of whether it's using the message ram or not. Cc: Bjorn Andersson <bjorn.andersson@sonymobile.com> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org> Signed-off-by: Andy Gross <agross@codeaurora.org>
Diffstat (limited to 'drivers/firmware/Makefile')
0 files changed, 0 insertions, 0 deletions