Re: [PATCH 15/15] ARM: dts: qcom: Add initial device tree for Kuno SoC
Hardeep Sharma <[email protected]>
| Newsgroups | org.kernel.vger.linux-clk,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-gpio,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pm |
|---|---|
| Message-ID | <[email protected]> |
On 8/13/2026 9:31 PM, Dmitry Baryshkov wrote: > On Thu, Aug 13, 2026 at 11:44:28AM +0200, Krzysztof Kozlowski wrote: >> On Tue, Aug 11, 2026 at 04:13:40AM +0300, Dmitry Baryshkov wrote: >>> On Sun, Aug 09, 2026 at 12:57:14PM +0530, Hardeep Sharma wrote: >>>> Add SoC-level DTSI (qcom-kuno.dtsi) and IDP board DTS >>>> (qcom-kuno-idp.dts) for the Qualcomm Kuno SoC. >>>> >>>> Peripherals included in this initial set: >>>> - Single Cortex-A7 CPU with PSCI idle states >>>> - RPMh RSC with clock controller, power domains, and BCM voter >>>> - GCC (Global Clock Controller) >>>> - TLMM pin controller (110 GPIOs) >>>> - Interconnect (aggre-noc, cnoc-main) >>>> - GENI UART console (QUP SE3) >>>> - SMEM, hardware spinlocks (TCSR mutex) >>> This is pretty limited without any storage. Does it NAND? >> It has serial connection. this is enough for a start. At least one >> communication interface is needed for early upstreaming. > Yes, but then, as I wrote, it is pretty useless without the backing > storage. Also, it would be nice if we new the future plan. Is it going > to stop at this point? Is it going to be expanded in the next few weeks? > Will we see a spread of conflicting patches 'arm64: qcom: kuno: add > support for foo' with foo in 'USB, PCI, remoteproc, NAND, etc.'. Hi Dmitry Thanks for review. Kuno is 32-bit ARM (Cortex-A7), so follow-ups will be `ARM: qcom: kuno:`, not `arm64:`. This series is the minimum-viable base (console + core infra), following the sdx55/sdx75 pattern. Storage and the other drivers will follow in coordinated series on top of this base. Best wishes, Hardeep Sharma