From: Stephan Gerhold <stephan@gerhold.net>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-remoteproc@vger.kernel.org, phone-devel@vger.kernel.org,
Aleksander Morgado <aleksander@aleksander.es>,
Stephan Gerhold <stephan@gerhold.net>
Subject: [PATCH v2 0/2] Enable BAM-DMUX/WWAN on Qualcomm MSM8916
Date: Mon, 28 Feb 2022 23:53:58 +0100 [thread overview]
Message-ID: <20220228225400.146555-1-stephan@gerhold.net> (raw)
This series enables using mobile Internet/WWAN on devices based on Qualcomm
MSM8916. The network driver for that has already landed in Linux 5.17.
The device tree node of BAM-DMUX does not have any own memory resources.
It just bundles resources from other hardware blocks. It could be added to the
device tree root node, but it logically belongs below the modem remote processor.
To allow adding it there, the qcom_q6v5_mss driver is modified slightly to
create a platform device for it.
Changes in v2:
- Avoid using of_platform_populate() and create platform device
specifically only for "qcom,bam-dmux".
Stephan Gerhold (2):
remoteproc: qcom_q6v5_mss: Create platform device for BAM-DMUX
arm64: dts: qcom: msm8916: Add BAM-DMUX for WWAN network interfaces
arch/arm64/boot/dts/qcom/msm8916.dtsi | 30 +++++++++++++++++++++++++++
drivers/remoteproc/qcom_q6v5_mss.c | 8 +++++++
2 files changed, 38 insertions(+)
--
2.35.1
next reply other threads:[~2022-02-28 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 22:53 Stephan Gerhold [this message]
2022-02-28 22:53 ` [PATCH v2 1/2] remoteproc: qcom_q6v5_mss: Create platform device for BAM-DMUX Stephan Gerhold
2022-02-28 22:54 ` [PATCH v2 2/2] arm64: dts: qcom: msm8916: Add BAM-DMUX for WWAN network interfaces Stephan Gerhold
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=20220228225400.146555-1-stephan@gerhold.net \
--to=stephan@gerhold.net \
--cc=agross@kernel.org \
--cc=aleksander@aleksander.es \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=phone-devel@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.