From: Gokul Sriram Palanisamy <gokulsri@codeaurora.org>
To: sboyd@kernel.org, agross@kernel.org, bjorn.andersson@linaro.org,
david.brown@linaro.org, devicetree@vger.kernel.org,
jassisinghbrar@gmail.com, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-remoteproc@vger.kernel.org, mark.rutland@arm.com,
mturquette@baylibre.com, ohad@wizery.com, robh+dt@kernel.org,
sricharan@codeaurora.org, nprakash@codeaurora.org,
gokulsri@codeaurora.org
Subject: [PATCH 0/3] remoteproc: qcom: q6v5-wcss: Add driver data for IPQ6018
Date: Fri, 29 Jan 2021 22:39:35 +0530 [thread overview]
Message-ID: <1611940178-24546-1-git-send-email-gokulsri@codeaurora.org> (raw)
Q6 based WiFi fw loading is supported across
different targets, ex: IPQ8074/QCS404. In order to
support different fw name for IPQ6018, populate
hardcoded param using compatible and driver data.
Gokul Sriram Palanisamy (3):
dt-bindings: remoteproc: qcom: Add Q6V5 Modem PIL binding for IPQ6018
remoteproc: qcom: wcss: populate driver data for IPQ6018
arm64: dts: ipq6018: Update WCSS PIL driver compatible
.../devicetree/bindings/remoteproc/qcom,q6v5.txt | 4 ++++
arch/arm64/boot/dts/qcom/ipq6018.dtsi | 2 +-
drivers/remoteproc/qcom_q6v5_wcss.c | 19 +++++++++++++++++--
3 files changed, 22 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2021-01-29 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 17:09 Gokul Sriram Palanisamy [this message]
2021-01-29 17:09 ` [PATCH 1/3] dt-bindings: remoteproc: qcom: Add Q6V5 Modem PIL binding for IPQ6018 Gokul Sriram Palanisamy
2021-01-29 17:09 ` [PATCH 2/3] remoteproc: qcom: wcss: populate driver data " Gokul Sriram Palanisamy
2021-01-29 17:09 ` [PATCH 3/3] arm64: dts: ipq6018: Update WCSS PIL driver compatible Gokul Sriram Palanisamy
2021-01-29 17:11 [PATCH 0/3] remoteproc: qcom: q6v5-wcss: Add driver data for IPQ6018 Gokul Sriram Palanisamy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1611940178-24546-1-git-send-email-gokulsri@codeaurora.org \
--to=gokulsri@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=nprakash@codeaurora.org \
--cc=ohad@wizery.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sricharan@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.