With the introduction of support for the non-MSA Hexagon WCSS driver from Sricharan and the non-PAS ADSP driver from Rohit it makes sense to overhaul the structure of the Qualcomm "Q6V5 drivers". The first patch is from Sricharan's series and included here for completeness. The second patch introduces a set of helper functions, based on the current state of the qcom_q6v5_pil driver. The third and forth patch migrates the PAS and the MSA drivers over to using these helpers. Finally a (completely) reworked version of Sricharan's WCSS remoteproc driver is introduced. With this in place I suggest that we rename qcom_adsp_pil.c to qcom_q6v5_pas.c, qcom_q6v5_pil.c to qcom_q6v5_msa.c and depending on the details of the non-PAS ADSP we could potentially combine that into a qcom_q6v5_pil.c - or we carry them as separate files. Looking at the remaining non-essential parts of these drivers we have memory-region handling and halt_axi handling. The prior is actively being worked on and the latter should (if no better abstraction is presented) be possible to just put in the new qcom_q6v5.c. Bjorn Andersson (3): remoteproc: q6v5: Extract common resource handling remoteproc: qcom: adsp: Use common q6v5 helpers remoteproc: qcom: q6v5-pil: Use common q6v5 helpers Sricharan R (1): remoteproc: qcom: mdt_loader: Make the firmware authentication optional drivers/remoteproc/Kconfig | 7 + drivers/remoteproc/Makefile | 1 + drivers/remoteproc/qcom_adsp_pil.c | 156 ++++-------------- drivers/remoteproc/qcom_q6v5.c | 243 ++++++++++++++++++++++++++++ drivers/remoteproc/qcom_q6v5.h | 46 ++++++ drivers/remoteproc/qcom_q6v5_pil.c | 157 ++---------------- drivers/soc/qcom/mdt_loader.c | 87 +++++++--- include/linux/soc/qcom/mdt_loader.h | 4 + 8 files changed, 405 insertions(+), 296 deletions(-) create mode 100644 drivers/remoteproc/qcom_q6v5.c create mode 100644 drivers/remoteproc/qcom_q6v5.h -- 2.17.0 -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html