From: Krzysztof Kozlowski <krzk@kernel.org>
To: Janaki Ramaiah Thota <quic_janathot@quicinc.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>
Cc: quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_msavaliy@quicinc.com
Subject: Re: [PATCH v3] arm64: dts: qcom: qcs6490-rb3gen2: enable Bluetooth
Date: Mon, 2 Dec 2024 10:36:06 +0100 [thread overview]
Message-ID: <6a40b442-6c4e-4abb-aeba-54ff9e86dfde@kernel.org> (raw)
In-Reply-To: <75dc7814-a55e-4a6f-9df9-39b7c875dee9@quicinc.com>
On 02/12/2024 10:32, Janaki Ramaiah Thota wrote:
>>
>>> + pinctrl-names = "default", "sleep";
>>> + pinctrl-1 = <&qup_uart7_sleep_cts>, <&qup_uart7_sleep_rts>,
>>> + <&qup_uart7_sleep_tx>, <&qup_uart7_sleep_rx>;
>>
>> This could be just one phandle to state node with multiple pins subnode.
>>
>
> Since we have different configuration for 3 GPIOs, it’s not good to
> combine all 4 GPIOs into one common sleep configuration. Each GPIO
> configuration is having separate requirements based on the Bluetooth SOC.
I did not propose that. Please read bindings and other existing DTS sources.
> This is as per hardware recommendations.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-02 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 10:46 [PATCH v3] arm64: dts: qcom: qcs6490-rb3gen2: enable Bluetooth Janaki Ramaiah Thota
2024-10-22 12:27 ` Krzysztof Kozlowski
2024-12-02 9:32 ` Janaki Ramaiah Thota
2024-12-02 9:36 ` Krzysztof Kozlowski [this message]
2024-12-02 11:26 ` Konrad Dybcio
2024-12-02 14:07 ` Janaki Ramaiah Thota
2024-10-24 16:33 ` Rob Herring (Arm)
2024-10-24 22:13 ` 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=6a40b442-6c4e-4abb-aeba-54ff9e86dfde@kernel.org \
--to=krzk@kernel.org \
--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=quic_hbandi@quicinc.com \
--cc=quic_janathot@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=quic_msavaliy@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