DMA Engine development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: robh@kernel.org, Frank.Li@kernel.org, vkoul@kernel.org,
	conor+dt@kernel.org, dmaengine@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v6 02/11] arm64: dts: qcom: Add QUPv3 configuration for Shikra
Date: Mon, 13 Jul 2026 19:51:22 +0000	[thread overview]
Message-ID: <20260713195123.271331F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714-shikra-dt-m1-v6-2-bee265d3499b@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Missing `interrupts` property for the `uart0` (qcom,geni-debug-uart) node.
- [Medium] The wakeup interrupt for uart2 on the RX pin (GPIO 9) is configured as IRQ_TYPE_LEVEL_HIGH instead of IRQ_TYPE_EDGE_FALLING.
--

--- Patch [2]: [PATCH v6 02/11] arm64: dts: qcom: Add QUPv3 configuration for Shikra ---
commit 1c9c89a1544a0e5440dc4a0a7e665dfb65d85dc8
Author: Xueyao An <xueyao.an@oss.qualcomm.com>

arm64: dts: qcom: Add QUPv3 configuration for Shikra

This commit adds device tree support for QUPv3 serial engine protocols on
the Qualcomm Shikra platform. It defines 10 QUP serial engines under a single
wrapper, with support for GPI DMA engines.

> diff --git a/arch/arm64/boot/dts/qcom/shikra.dtsi b/arch/arm64/boot/dts/qcom/shikra.dtsi
> index 4e5bc9e17c8ed..f0fb55b9deb90 100644
> --- a/arch/arm64/boot/dts/qcom/shikra.dtsi
> +++ b/arch/arm64/boot/dts/qcom/shikra.dtsi
[ ... ]
> @@ -613,10 +896,75 @@ qupv3_0: geniqup@4ac0000 {
[ ... ]
>  			uart0: serial@4a80000 {
>  				compatible = "qcom,geni-debug-uart";
>  				reg = <0x0 0x04a80000 0x0 0x4000>;

[Severity: High]
Does this node need an interrupts property? The qcom,geni-debug-uart binding
requires it, and qcom_geni_serial will fail to probe if it's missing (it calls
platform_get_irq(pdev, 0)). Since it shares SE0 with i2c0 and spi0, should
this be <GIC_SPI 527 IRQ_TYPE_LEVEL_HIGH 0>?

[ ... ]
> @@ -638,6 +986,609 @@ &clk_virt SLAVE_QUP_CORE_0 RPM_ALWAYS_TAG>,
[ ... ]
> +			uart2: serial@4a88000 {
> +				compatible = "qcom,geni-uart";
> +				reg = <0x0 0x04a88000 0x0 0x4000>;
> +
> +				interrupts-extended = <&intc GIC_SPI 529 IRQ_TYPE_LEVEL_HIGH 0>,
> +						      <&tlmm 9 IRQ_TYPE_LEVEL_HIGH>;

[Severity: Medium]
Is IRQ_TYPE_LEVEL_HIGH correct for the tlmm 9 wakeup interrupt? UART RX lines
idle HIGH and transition LOW on the start bit. Using a level high trigger
could cause an interrupt storm when the line is idle, or prevent low-power
states. Should this be IRQ_TYPE_EDGE_FALLING instead?

> +
> +				clocks = <&gcc GCC_QUPV3_WRAP0_S2_CLK>;
> +				clock-names = "se";

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714-shikra-dt-m1-v6-0-bee265d3499b@oss.qualcomm.com?part=2

  reply	other threads:[~2026-07-13 19:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 19:36 [PATCH v6 00/11] arm64: dts: qcom: Extend Shikra device tree with peripheral and subsystem support Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 01/11] dt-bindings: interconnect: qcom-bwmon: Add Shikra cpu-bwmon compatible Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 02/11] arm64: dts: qcom: Add QUPv3 configuration for Shikra Komal Bajaj
2026-07-13 19:51   ` sashiko-bot [this message]
2026-07-13 19:36 ` [PATCH v6 03/11] arm64: dts: qcom: shikra: Add DDR BWMON support Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 04/11] arm64: dts: qcom: shikra: Add cpufreq-hw, EPSS L3 interconnect and OPP tables Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 05/11] arm64: dts: qcom: shikra: Add SMP2P nodes Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 06/11] arm64: dts: qcom: shikra: Add CDSP, LPAICP, MPSS remoteproc PAS nodes Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 07/11] arm64: dts: qcom: shikra: Enable CDSP, LPAICP and MPSS on EVK boards Komal Bajaj
2026-07-13 19:42   ` sashiko-bot
2026-07-13 19:36 ` [PATCH v6 08/11] arm64: dts: qcom: shikra: Enable TSENS and thermal zones Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 09/11] arm64: dts: qcom: shikra: add WiFi node support Komal Bajaj
2026-07-13 19:36 ` [PATCH v6 10/11] arm64: dts: qcom: shikra: Enable WiFi/BT on SoMs Komal Bajaj
2026-07-13 19:57   ` sashiko-bot
2026-07-13 19:37 ` [PATCH v6 11/11] arm64: dts: qcom: shikra: Add gpio-reserved-ranges to tlmm Komal Bajaj

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=20260713195123.271331F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=komal.bajaj@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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