Q6V5 MSS on certain SoCs like SDM845 are capable of operating under
completely different configuration (like Non-Modem WLAN configuration)
depending on the firmware loaded without any change in boot sequence
of the Hexagon core. The patch series is ultimately aimed to avoid
multiple compatibles per SoC to just specify different upstreamed firmware
locations. This is achieved by using "firmware-name" binding to store
the relative path of mba/modem/pas firmware images.
remoteproc@4080000 {
...
firmware-name = "qcom/sdm845/mss/mba.mbn",
"qcom/sdm845/mss/modem.mdt";
...
}
remoteproc@17300000 {
...
firmware-name = "qcom/sdm845/lpass/adsp.mdt";
...
}
Suggested-by: Bjorn Andersson <bjorn.andersson@xxxxxxxxxx>
v2:
* Replace "qcom,firmware" with "firmware-name" as suggested
by Rob
* Include dt-bindings/parsing logic for PAS based remoteprocs
Sibi Sankar (2):
dt-bindings: remoteproc: qcom: Add firmware bindings for Q6V5
remoteproc: qcom: Add support for parsing fw dt bindings
.../bindings/remoteproc/qcom,adsp.txt | 6 +++
.../bindings/remoteproc/qcom,q6v5.txt | 7 +++
drivers/remoteproc/qcom_q6v5_mss.c | 46 +++++++++++++++----
drivers/remoteproc/qcom_q6v5_pas.c | 11 ++++-
4 files changed, 59 insertions(+), 11 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
