From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: [PATCH v3 0/4] arm64: dts: qcom: sc8280xp: enable WLAN and Bluetooth
Date: Thu, 5 Sep 2024 14:20:18 +0200 [thread overview]
Message-ID: <20240905122023.47251-1-brgl@bgdev.pl> (raw)
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
This correctly models the WLAN and Bluetooth modules on two boards using
the sc8280xp SoC. For the sc8280xp-crd we add the PMU, wifi and bluetooth
nodes with the correctly modelled wiring between them. For the X13s, we
rework existing nodes so that they align with the new DT bindings
contract.
v2 -> v3:
- move adding the bt-enable-gpios to the PMU on the CRD to patch 2/4
- add a patch removing the regulator-always-on property from regulators
on X13s that no longer need it
v1 -> v2:
- fix commit message in patch 1/3
- drop drive-strength from the wlan enable pin function
- drop the calibration variant property from the wifi node of the CRD
Bartosz Golaszewski (3):
arm64: dts: qcom: sc8280xp-crd: enable bluetooth
arm64: dts: qcom: sc8280xp-x13s: model the PMU of the on-board wcn6855
arm64: dts: qcom: sc8280xp-x13s: keep less regulators always-on
Konrad Dybcio (1):
arm64: dts: qcom: sc8280xp-crd: model the PMU of the on-board wcn6855
arch/arm64/boot/dts/qcom/sc8280xp-crd.dts | 166 ++++++++++++++++++
.../qcom/sc8280xp-lenovo-thinkpad-x13s.dts | 102 +++++++++--
2 files changed, 252 insertions(+), 16 deletions(-)
--
2.43.0
next reply other threads:[~2024-09-05 12:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 12:20 Bartosz Golaszewski [this message]
2024-09-05 12:20 ` [PATCH v3 1/4] arm64: dts: qcom: sc8280xp-crd: model the PMU of the on-board wcn6855 Bartosz Golaszewski
2024-09-05 12:50 ` Dmitry Baryshkov
2024-09-05 12:53 ` Bartosz Golaszewski
2024-09-05 12:56 ` Dmitry Baryshkov
2024-09-05 13:00 ` Bartosz Golaszewski
2024-09-05 13:13 ` Konrad Dybcio
2024-09-05 18:41 ` Kalle Valo
2024-09-05 19:26 ` Dmitry Baryshkov
2024-09-06 7:45 ` Bartosz Golaszewski
2024-09-06 9:37 ` Dmitry Baryshkov
2024-09-06 9:45 ` Bartosz Golaszewski
2024-09-09 11:18 ` Kalle Valo
2024-09-06 14:53 ` Johan Hovold
2024-09-06 21:37 ` Dmitry Baryshkov
2024-09-05 12:20 ` [PATCH v3 2/4] arm64: dts: qcom: sc8280xp-crd: enable bluetooth Bartosz Golaszewski
2024-09-05 12:20 ` [PATCH v3 3/4] arm64: dts: qcom: sc8280xp-x13s: model the PMU of the on-board wcn6855 Bartosz Golaszewski
2024-09-05 12:27 ` Dmitry Baryshkov
2024-09-05 12:29 ` Bartosz Golaszewski
2024-09-05 12:20 ` [PATCH v3 4/4] arm64: dts: qcom: sc8280xp-x13s: keep less regulators always-on Bartosz Golaszewski
2024-09-05 14:04 ` Johan Hovold
2024-09-05 18:23 ` Bartosz Golaszewski
2024-09-05 19:27 ` Dmitry Baryshkov
2024-09-06 14:49 ` Johan Hovold
2024-09-06 21:37 ` Dmitry Baryshkov
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=20240905122023.47251-1-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox