From: Kaushal Kumar <quic_kaushalk@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
<vkoul@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <manivannan.sadhasivam@linaro.org>,
<miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>,
<andersson@kernel.org>, <konradybcio@kernel.org>,
<agross@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 4/6] ARM: dts: qcom: sdx75: Add QPIC NAND support
Date: Thu, 27 Mar 2025 16:18:29 +0530 [thread overview]
Message-ID: <26463cdf-f041-0dc3-dae2-cf5a91a35373@quicinc.com> (raw)
In-Reply-To: <2fb1ddf6-0fca-4bf6-9970-728448f893d2@oss.qualcomm.com>
On 3/13/2025 8:06 PM, Konrad Dybcio wrote:
> On 3/13/25 2:09 PM, Kaushal Kumar wrote:
>> Add devicetree node to enable support for QPIC
>> NAND controller on Qualcomm SDX75 platform.
>> Since there is no "aon" clock in SDX75, a dummy
>> clock is provided.
> Alter the bindings not to require it then, instead
>
> [...]
Will update in v2.
>
>>
>> + qpic_nand: nand-controller@1cc8000 {
>> + compatible = "qcom,sdx75-nand", "qcom,sdx55-nand";
>> + reg = <0x0 0x01cc8000 0x0 0x10000>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + clocks = <&rpmhcc RPMH_QPIC_CLK>,
>> + <&nand_clk_dummy>;
>> + clock-names = "core", "aon";
>> +
>> + dmas = <&qpic_bam 0>,
>> + <&qpic_bam 1>,
>> + <&qpic_bam 2>;
>> + dma-names = "tx", "rx", "cmd";
> Please make dma-names a vertical list, just like dmas
Sure, will update in v2.
>
> Konrad
next prev parent reply other threads:[~2025-03-27 10:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 13:09 [PATCH 0/6] Enable QPIC BAM and QPIC NAND support for SDX75 Kaushal Kumar
2025-03-13 13:09 ` [PATCH 1/6] dt-bindings: mtd: qcom,nandc: Document the SDX75 NAND Kaushal Kumar
2025-03-13 14:31 ` Rob Herring (Arm)
2025-03-13 14:48 ` Krzysztof Kozlowski
2025-03-27 10:42 ` Kaushal Kumar
2025-03-13 13:09 ` [PATCH 2/6] dt-bindings: dma: qcom,bam: Document dma-coherent property Kaushal Kumar
2025-03-13 14:50 ` Krzysztof Kozlowski
2025-03-27 10:46 ` Kaushal Kumar
2025-03-13 13:09 ` [PATCH 3/6] ARM: dts: qcom: sdx75: Add QPIC BAM support Kaushal Kumar
2025-03-13 13:09 ` [PATCH 4/6] ARM: dts: qcom: sdx75: Add QPIC NAND support Kaushal Kumar
2025-03-13 14:36 ` Konrad Dybcio
2025-03-27 10:48 ` Kaushal Kumar [this message]
2025-03-13 14:50 ` Krzysztof Kozlowski
2025-03-27 10:47 ` Kaushal Kumar
2025-03-13 13:09 ` [PATCH 5/6] ARM: dts: qcom: sdx75-idp: Enable QPIC BAM support Kaushal Kumar
2025-03-13 14:37 ` Konrad Dybcio
2025-03-27 10:25 ` Kaushal Kumar
2025-03-13 13:09 ` [PATCH 6/6] ARM: dts: qcom: sdx75-idp: Enable QPIC NAND support Kaushal Kumar
2025-03-13 14:30 ` [PATCH 0/6] Enable QPIC BAM and QPIC NAND support for SDX75 Konrad Dybcio
2025-03-27 10:23 ` Kaushal Kumar
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=26463cdf-f041-0dc3-dae2-cf5a91a35373@quicinc.com \
--to=quic_kaushalk@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@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=linux-mtd@lists.infradead.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
--cc=vkoul@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