From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Luca Weiss <luca.weiss@fairphone.com>,
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>,
Alexander Koskovich <AKoskovich@pm.me>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/5] arm64: dts: qcom: milos: Split up uart11 pinctrl
Date: Tue, 20 Jan 2026 15:12:52 +0100 [thread overview]
Message-ID: <41840083-0cf9-493f-a9be-d671b4d59a0d@oss.qualcomm.com> (raw)
In-Reply-To: <20260116-milos-fp6-bt-wifi-v1-2-27b4fbb77e9c@fairphone.com>
On 1/16/26 3:50 PM, Luca Weiss wrote:
> In order to set the pinctrl for the individual CTS, RTS, TX and RX pins,
> split up the pinctrl configuration into 4 nodes so that boards can set
> some properties separately.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> arch/arm64/boot/dts/qcom/milos.dtsi | 26 +++++++++++++++-----------
> 1 file changed, 15 insertions(+), 11 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/milos.dtsi b/arch/arm64/boot/dts/qcom/milos.dtsi
> index 0f69deabb60c..024e1c9992fe 100644
> --- a/arch/arm64/boot/dts/qcom/milos.dtsi
> +++ b/arch/arm64/boot/dts/qcom/milos.dtsi
> @@ -915,7 +915,7 @@ &clk_virt SLAVE_QUP_CORE_1 QCOM_ICC_TAG_ALWAYS>,
> interconnect-names = "qup-core",
> "qup-config";
>
> - pinctrl-0 = <&qup_uart11_default>, <&qup_uart11_cts_rts>;
> + pinctrl-0 = <&qup_uart11_cts>, <&qup_uart11_rts>, <&qup_uart11_tx>, <&qup_uart11_rx>;
> pinctrl-names = "default";
>
> status = "disabled";
> @@ -1835,20 +1835,24 @@ qup_uart5_default: qup-uart5-default-state {
> bias-disable;
> };
>
> - qup_uart11_default: qup-uart11-default-state {
> - /* TX, RX */
> - pins = "gpio50", "gpio51";
> + qup_uart11_cts: qup-uart11-cts-state {
> + pins = "gpio48";
> function = "qup1_se4";
> - drive-strength = <2>;
> - bias-pull-up;
> };
I think the best setup is
qup_uart11_default: foo-state {
qup_uart11_tx: bar-pins {
...
};
};
qup_uart11_cts_rts: foo-state {
qup_uart11_rts: bar-pins {
...
};
};
Since there's a lower amount of references at the user (default vs
cts/rts still makes sense as that's a wiring difference) but we still
keep a label for customizing the properties
Konrad
next prev parent reply other threads:[~2026-01-20 14:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 14:50 [PATCH 0/5] Enable Bluetooth and WiFi on Fairphone (Gen. 6) Luca Weiss
2026-01-16 14:50 ` [PATCH 1/5] soc: qcom: pd-mapper: Add Milos compatible Luca Weiss
2026-01-16 16:13 ` Dmitry Baryshkov
2026-01-16 14:50 ` [PATCH 2/5] arm64: dts: qcom: milos: Split up uart11 pinctrl Luca Weiss
2026-01-20 14:12 ` Konrad Dybcio [this message]
2026-01-16 14:50 ` [PATCH 3/5] arm64: dts: qcom: milos: Add WCN6750 WiFi node Luca Weiss
2026-01-16 16:14 ` Dmitry Baryshkov
2026-01-20 14:39 ` Konrad Dybcio
2026-02-13 13:42 ` Luca Weiss
2026-02-17 11:01 ` Konrad Dybcio
2026-02-13 14:31 ` Dmitry Baryshkov
2026-02-17 10:59 ` Konrad Dybcio
2026-01-16 14:50 ` [PATCH 4/5] arm64: dts: qcom: milos-fairphone-fp6: Enable Bluetooth Luca Weiss
2026-01-16 16:15 ` Dmitry Baryshkov
2026-01-21 11:52 ` Konrad Dybcio
2026-03-13 10:40 ` Luca Weiss
2026-03-13 12:41 ` Konrad Dybcio
2026-03-13 14:00 ` Luca Weiss
2026-03-16 12:50 ` Konrad Dybcio
2026-01-16 14:50 ` [PATCH 5/5] arm64: dts: qcom: milos-fairphone-fp6: Enable WiFi Luca Weiss
2026-01-16 16:17 ` Dmitry Baryshkov
2026-01-21 11:50 ` Konrad Dybcio
2026-02-13 14:24 ` Luca Weiss
2026-02-17 10:56 ` Konrad Dybcio
2026-03-19 3:31 ` (subset) [PATCH 0/5] Enable Bluetooth and WiFi on Fairphone (Gen. 6) Bjorn Andersson
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=41840083-0cf9-493f-a9be-d671b4d59a0d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=AKoskovich@pm.me \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox