From: sashiko-bot@kernel.org
To: "Bartosz Golaszewski" <bartosz.golaszewski@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: nord: wire up GPI DMA for QUP I2C/SPI engines
Date: Fri, 13 Nov 2026 09:47:54 +0000 [thread overview]
Message-ID: <sashiko-outbox-212570@kernel.org> (raw)
In-Reply-To: <20261113-nord-gpi-dts-v4-2-e4a1510687c0@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential
issues to consider:
- [Medium] arm64: dts: qcom: nord: QCOM_GPI_SPI DMA properties added to
UART nodes
- [Medium] arm64: dts: qcom: nord: missing GPI DMA properties on spi4
and spi14..spi19
--
commit 9c6fd2386259cb23b0a0394993d22bac655549bb
Author: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
arm64: dts: qcom: nord: wire up GPI DMA for QUP I2C/SPI engines
This commit adds GPI DMA channel phandles and dma-names properties to QUPv3
I2C and SPI serial engine nodes in nord.dtsi.
> diff --git a/arch/arm64/boot/dts/qcom/nord.dtsi b/arch/arm64/boot/dts/qcom/nord.dtsi
> index 68787db708f61..818f6054bcec8 100644
> --- a/arch/arm64/boot/dts/qcom/nord.dtsi
> +++ b/arch/arm64/boot/dts/qcom/nord.dtsi
[ ... ]
> @@ -1244,6 +1272,10 @@ spi20: spi@898000 {
> reg = <0x0 0x00898000 0x0 0x4000>;
> interrupts = <GIC_SPI 461 IRQ_TYPE_LEVEL_HIGH>;
>
> + dmas = <&gpi_dma2 0 6 QCOM_GPI_SPI>,
> + <&gpi_dma2 1 6 QCOM_GPI_SPI>;
> + dma-names = "tx", "rx";
> +
> status = "disabled";
> };
>
[Severity: Medium]
Were the GPI DMA properties for spi14 through spi19 (on gpi_dma2 SE 0..5)
and spi4 (on gpi_dma0 SE 4) accidentally omitted?
All seven I2C nodes in qupv3_2 (i2c14..i2c20) and all six I2C nodes in
qupv3_0 (i2c0..i2c5) are wired up, but among the SPI nodes in qupv3_2 only
spi20 receives gpi_dma2 channels, and spi4 in qupv3_0 is also skipped. In
particular, spi16 (spi@888000) is enabled on Nord Ride and Nord RRD, so
spi_geni_grab_gpi_chan() will fail to acquire the tx and rx DMA channels
when FIFO_IF_DISABLE is set and fall back to FIFO mode.
[ ... ]
> @@ -1309,6 +1345,10 @@ uart0: serial@980000 {
> reg = <0x0 0x00980000 0x0 0x4000>;
> interrupts = <GIC_SPI 314 IRQ_TYPE_LEVEL_HIGH>;
>
> + dmas = <&gpi_dma0 0 0 QCOM_GPI_SPI>,
> + <&gpi_dma0 1 0 QCOM_GPI_SPI>;
> + dma-names = "tx", "rx";
> +
> status = "disabled";
> };
>
[Severity: Medium]
As reported by Konrad Dybcio on v3 [1], should these QCOM_GPI_SPI DMA
channels be added to spi0..spi3, spi7..spi8, and spi11..spi12 instead of
their sibling UART nodes (uart0..uart3, uart7..uart8, and uart11..uart12)?
Those eight SPI nodes are left without GPI DMA channels, causing
spi_geni_grab_gpi_chan() to fail to acquire tx and rx DMA channels when
FIFO_IF_DISABLE is set, while the UART nodes gain dmas and dma-names
properties that are not permitted by the GENI UART bindings.
[1] https://lore.kernel.org/r/6e91b34f-367e-4835-a7ce-e899953a5bd1@oss.qualcomm.com
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-nord-gpi-dts-v4-0-e4a1510687c0@oss.qualcomm.com?part=2
prev parent reply other threads:[~2026-11-13 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 9:38 [PATCH v4 0/2] arm64: dts: qcom: nord: add GPI DMA nodes Bartosz Golaszewski
2026-11-13 9:38 ` [PATCH v4 1/2] arm64: dts: qcom: nord: add GPI DMA controller nodes Bartosz Golaszewski
2026-11-13 9:38 ` [PATCH v4 2/2] arm64: dts: qcom: nord: wire up GPI DMA for QUP I2C/SPI engines Bartosz Golaszewski
2026-11-13 9:47 ` sashiko-bot [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=sashiko-outbox-212570@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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