From: Kathiravan Thirumoorthy <kathiravan.thirumoorthy@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.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>,
Abel Vesa <abelvesa@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 02/11] arm64: dts: qcom: ipq5210: Introduce RDP504 common DT file
Date: Tue, 13 Oct 2026 20:46:45 +0530 [thread overview]
Message-ID: <78480c25-6d83-4e70-a9f6-826760046cda@oss.qualcomm.com> (raw)
In-Reply-To: <3fff91c4-b831-410f-a151-847ea407acb2@oss.qualcomm.com>
On 10/13/2026 8:11 PM, Konrad Dybcio wrote:
> On 10/13/26 3:14 PM, Kathiravan Thirumoorthy wrote:
>> On 10/12/2026 12:53 PM, Varadarajan Narayanan wrote:
>>> RDP504 has USB, PCIe and SPI NAND devices populated. EMMC and NAND
>>> share the GPIOs. The board has to be reworked to change from EMMC
>>> to NAND variant. Rename ipq5210-rdp504.dts as ipq5210-rdp504-common.dtsi
>>> and include it in variant specific DTS file.
>>>
>>> Describe the fixed USB regulators, PCIe reset GPIOs, QPIC SPI NAND flash
>>> and required pinctrl states. Enable QPIC BAM, USB and PCIe for the board.
>>>
>>> Signed-off-by: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>
>>> ---
>>> .../arm64/boot/dts/qcom/ipq5210-rdp504-common.dtsi | 209 +++++++++++++++++++++
>>> arch/arm64/boot/dts/qcom/ipq5210-rdp504.dts | 66 +------
>>> 2 files changed, 211 insertions(+), 64 deletions(-)
>> [...]
>>
>>> +
>>> +&qpic_bam {
>>> + status = "okay";
>>> +};
>> NAND is the only consumer of this BAM. Should we move it to NAND DTS?
> Can we enable it by default? (i.e. is there any reason not to?)
I don't see any reason for not enabling this by default . Since nand is
the only consumer of the BAM DMA, we enable both nodes together to keep
the unneeded devices in disabled state.
>
> Konrad
next prev parent reply other threads:[~2026-10-13 15:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 7:23 [PATCH v7 00/11] Enable mutliple peripherals in IPQ5210 Varadarajan Narayanan
2026-10-12 7:23 ` [PATCH v7 01/11] arm64: dts: qcom: ipq5210: Add nodes for multiple peripherals Varadarajan Narayanan
2026-10-12 7:23 ` [PATCH v7 02/11] arm64: dts: qcom: ipq5210: Introduce RDP504 common DT file Varadarajan Narayanan
2026-10-13 13:14 ` Kathiravan Thirumoorthy
2026-10-13 14:41 ` Konrad Dybcio
2026-10-13 15:16 ` Kathiravan Thirumoorthy [this message]
2026-10-13 15:49 ` Konrad Dybcio
2026-10-12 7:23 ` [PATCH v7 03/11] arm64: dts: qcom: ipq5210: Introduce RDP504 NAND variant " Varadarajan Narayanan
2026-10-12 7:23 ` [PATCH v7 04/11] arm64: dts: qcom: ipq5210: Add support for WPS button Varadarajan Narayanan
2026-10-13 14:42 ` Konrad Dybcio
2026-10-12 7:23 ` [PATCH v7 05/11] arm64: dts: qcom: ipq5210: Add C3 CPU idle state Varadarajan Narayanan
2026-10-13 14:42 ` Konrad Dybcio
2026-10-12 7:23 ` [PATCH v7 06/11] arm64: dts: qcom: ipq5210: Add ICE support to SDHCI Varadarajan Narayanan
2026-10-13 14:43 ` Konrad Dybcio
2026-10-14 5:03 ` Varadarajan Narayanan
2026-10-12 7:23 ` [PATCH v7 07/11] arm64: dts: qcom: ipq5210: Enable download mode support Varadarajan Narayanan
2026-10-13 14:44 ` Konrad Dybcio
2026-10-12 7:23 ` [PATCH v7 08/11] arm64: dts: qcom: ipq5210: Enable the PWM block Varadarajan Narayanan
2026-10-13 14:46 ` Konrad Dybcio
2026-10-12 7:23 ` [PATCH v7 09/11] arm64: dts: qcom: ipq5210: Add I2C nodes Varadarajan Narayanan
2026-10-13 13:08 ` Kathiravan Thirumoorthy
2026-10-12 7:23 ` [PATCH v7 10/11] arm64: dts: qcom: ipq5210: Add SPI node definitions Varadarajan Narayanan
2026-10-13 13:10 ` Kathiravan Thirumoorthy
2026-10-12 7:23 ` [PATCH v7 11/11] arm64: dts: qcom: ipq5210: Add random number generator node Varadarajan Narayanan
2026-10-13 14:45 ` Konrad Dybcio
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=78480c25-6d83-4e70-a9f6-826760046cda@oss.qualcomm.com \
--to=kathiravan.thirumoorthy@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=varadarajan.narayanan@oss.qualcomm.com \
/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®