From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
<andersson@kernel.org>, <linus.walleij@linaro.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<konradybcio@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <quic_srichara@quicinc.com>, <quic_varada@quicinc.com>
Subject: Re: [PATCH 4/4] arm64: dts: qcom: ipq5424: configure spi0 node for rdp466
Date: Mon, 9 Dec 2024 12:13:29 +0530 [thread overview]
Message-ID: <aa8a252d-cb7c-45c9-bb44-dcaaa01d10bb@quicinc.com> (raw)
In-Reply-To: <249fb0aa-5624-41cb-8a3b-c2e54dba87df@oss.qualcomm.com>
On 12/5/2024 11:00 PM, Konrad Dybcio wrote:
> On 22.11.2024 1:45 PM, Manikanta Mylavarapu wrote:
>> Enable the SPI0 node and configure the associated gpio pins.
>>
>> Signed-off-by: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts | 45 +++++++++++++++++++++
>> 1 file changed, 45 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts b/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts
>> index d4d31026a026..6256216ca764 100644
>> --- a/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts
>> +++ b/arch/arm64/boot/dts/qcom/ipq5424-rdp466.dts
>> @@ -23,6 +23,36 @@ &sleep_clk {
>> };
>>
>> &tlmm {
>> + spi0_default_state: spi0-default-state {
>> + clk-pins {
>> + pins = "gpio6";
>> + function = "spi0_clk";
>> + drive-strength = <8>;
>> + bias-pull-down;
>> + };
>> +
>> + cs-pins {
>> + pins = "gpio7";
>> + function = "spi0_cs";
>> + drive-strength = <8>;
>> + bias-pull-up;
>> + };
>> +
>> + miso-pins {
>> + pins = "gpio8";
>> + function = "spi0_miso";
>> + drive-strength = <8>;
>> + bias-pull-down;
>> + };
>> +
>> + mosi-pins {
>> + pins = "gpio9";
>> + function = "spi0_mosi";
>> + drive-strength = <8>;
>> + bias-pull-down;
>> + };
>> + };
>> +
>> sdc_default_state: sdc-default-state {
>> clk-pins {
>> pins = "gpio5";
>> @@ -57,3 +87,18 @@ &xo_board {
>> clock-frequency = <24000000>;
>> };
>>
>> +&qupv3 {
>> + spi0: spi@1a90000 {
>
> &spi0 {
> pinctrl-0 = <..
> ...
> };
>
Thanks for reviewing the patch.
I will update in the next version.
Thanks & Regards,
Manikanta.
prev parent reply other threads:[~2024-12-09 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 12:45 [PATCH 0/4] Add SPI0 support for IPQ5424 Manikanta Mylavarapu
2024-11-22 12:45 ` [PATCH 1/4] dt-bindings: pinctrl: qcom: update spi0 function Manikanta Mylavarapu
2024-11-26 7:23 ` Krzysztof Kozlowski
2024-11-22 12:45 ` [PATCH 2/4] pinctrl: qcom: ipq5424: split spi0 pin group Manikanta Mylavarapu
2024-11-22 12:45 ` [PATCH 3/4] arm64: dts: qcom: ipq5424: add spi0 node Manikanta Mylavarapu
2024-11-22 12:45 ` [PATCH 4/4] arm64: dts: qcom: ipq5424: configure spi0 node for rdp466 Manikanta Mylavarapu
2024-12-05 17:30 ` Konrad Dybcio
2024-12-09 6:43 ` 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=aa8a252d-cb7c-45c9-bb44-dcaaa01d10bb@quicinc.com \
--to=quic_mmanikan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@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