From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To: Kathiravan Thirumoorthy
<kathiravan.thirumoorthy@oss.qualcomm.com>,
<andersson@kernel.org>, <konradybcio@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<quic_srichara@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <quic_varada@quicinc.com>
Subject: Re: [PATCH v1] arm64: dts: qcom: ipq5424: fix and relocate uart1 gpio configurations
Date: Mon, 17 Mar 2025 14:52:40 +0530 [thread overview]
Message-ID: <a1cbab24-d931-4946-ba58-4c37f0bb9cc0@quicinc.com> (raw)
In-Reply-To: <8efdc560-d061-4f03-bed5-8571044119cc@oss.qualcomm.com>
On 3/12/2025 10:10 PM, Kathiravan Thirumoorthy wrote:
> On 3/12/2025 2:44 PM, Manikanta Mylavarapu wrote:
>> Update the bias configuration for UART1 TX and RX pins to ensure correct
>> settings for RDP466.
>>
>> Additionally, move the UART1 GPIO configurations from the common .dtsi
>> file to the RDP-specific .dts files to account for differing bias
>> configurations across RDPs of IPQ5424.
>>
>> Fixes: 1a91d2a6021e ("arm64: dts: qcom: add IPQ5424 SoC and rdp466 board support")
>> Signed-off-by: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts | 16 +++++++++++++++-
>> arch/arm64/boot/dts/qcom/ipq5424.dtsi | 7 -------
>> 2 files changed, 15 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts b/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts
>> index b6e4bb3328b3..7b85aaa11ee8 100644
>> --- a/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts
>> +++ b/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts
>> @@ -147,10 +147,24 @@ data-pins {
>> bias-pull-up;
>> };
>> };
>> +
>> + uart1_tx_state: uart1-tx-state {
>> + pins = "gpio44";
>> + function = "uart1";
>> + drive-strength = <8>;
>> + bias-pull-down;
>> + };
>> +
>> + uart1_rx_state: uart1-rx-state {
>> + pins = "gpio43";
>> + function = "uart1";
>> + drive-strength = <8>;
>> + bias-pull-up;
>> + };
>> };
>> &uart1 {
>> - pinctrl-0 = <&uart1_pins>;
>> + pinctrl-0 = <&uart1_tx_state>, <&uart1_rx_state>;
>
>
> Change LGTM. But can we define both TX and RX pin definition under one node like below, to align with the SPI and SDCC gpio definition layout?
>
> qup_uart1_default_state: qup-uart1-default-state {
>
> uart1_tx_state: uart1-tx-state {
>
> ...
>
> };
>
> uart1_rx_state: uart1-rx-state {
>
> ...
>
> };
>
> };
>
> and refer it like pinctrl-0 = <&qup_uart1_default_state>;
>
>
Hi Kathir,
Thank you for reviewing the patch.
I will incorporate the suggested change in the next version.
Thanks & Regards,
Manikanta.
prev parent reply other threads:[~2025-03-17 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:14 Manikanta Mylavarapu
2025-03-12 16:40 ` Kathiravan Thirumoorthy
2025-03-17 9:22 ` Manikanta Mylavarapu [this message]
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=a1cbab24-d931-4946-ba58-4c37f0bb9cc0@quicinc.com \
--to=quic_mmanikan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--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
all inboxes | Powered by JetHome®