Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Pengyu Luo <mitltlatltl@gmail.com>
To: eugen.hristev@linaro.org
Cc: andersson@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
	dmitry.baryshkov@foundries.io, konradybcio@kernel.org,
	krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mitltlatltl@gmail.com,
	robh@kernel.org, vkoul@kernel.org
Subject: Re: [PATCH RESEND 2/3] arm64: dts: qcom: sc8280xp: Add GPI DMA configuration
Date: Thu,  5 Jun 2025 21:17:18 +0800	[thread overview]
Message-ID: <20250605131719.472132-1-mitltlatltl@gmail.com> (raw)
In-Reply-To: <550a7ead-99a8-44ac-af49-c0e9d79c35c9@linaro.org>

On Thu, Jun 5, 2025 at 8:48 PM Eugen Hristev <eugen.hristev@linaro.org> wrote:
> On 6/5/25 10:54, Pengyu Luo wrote:
> > SPI on SC8280XP requires DMA (GSI) mode to function properly. Without it,
> > SPI controllers fall back to FIFO mode, which causes:
> >
> > [    0.901296] geni_spi 898000.spi: error -ENODEV: Failed to get tx DMA ch
> > [    0.901305] geni_spi 898000.spi: FIFO mode disabled, but couldn't get DMA, fall back to FIFO mode
> > ...
> > [   45.605974] goodix-spi-hid spi0.0: SPI transfer timed out
> > [   45.605988] geni_spi 898000.spi: Can't set CS when prev xfer running
> > [   46.621555] spi_master spi0: failed to transfer one message from queue
> > [   46.621568] spi_master spi0: noqueue transfer failed
> > [   46.621577] goodix-spi-hid spi0.0: spi transfer error: -110
> > [   46.621585] goodix-spi-hid spi0.0: probe with driver goodix-spi-hid failed with error -110
> >
> > Therefore, add GPI DMA controller nodes for qup{0,1,2}, and add DMA
> > channels for SPI and I2C, UART is excluded for now, as it does not
> > yet support this mode.
> >
> > Note that, since there is no public schematic, this configuration
>
> Device tree should describe the hardware, not hold a configuration. If
> you are configuring hardware, DT is not the place for this. Same goes
> for the commit short message.
>

Since I am just an amateur, so I followed some applied examples, like [1]
If you mind this, I will describe in next version.

[1]: https://lore.kernel.org/linux-arm-msm/20241021102815.12079-1-quic_vdadhani@quicinc.com

Best wishes,
Pengyu

  reply	other threads:[~2025-06-05 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  7:54 [PATCH RESEND 0/3] arm64: dts: qcom: Enable GPI DMA for sc8280xp Pengyu Luo
2025-06-05  7:54 ` [PATCH RESEND 1/3] dt-bindings: dma: qcom,gpi: Document the sc8280xp GPI DMA engine Pengyu Luo
2025-06-05  7:54 ` [PATCH RESEND 2/3] arm64: dts: qcom: sc8280xp: Add GPI DMA configuration Pengyu Luo
2025-06-05 12:48   ` Eugen Hristev
2025-06-05 13:17     ` Pengyu Luo [this message]
2025-06-05  7:54 ` [PATCH RESEND 3/3] arm64: dts: qcom: sc8280xp: Enable GPI DMA Pengyu Luo
2025-06-05  8:56 ` [PATCH RESEND 0/3] arm64: dts: qcom: Enable GPI DMA for sc8280xp Dmitry Baryshkov

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=20250605131719.472132-1-mitltlatltl@gmail.com \
    --to=mitltlatltl@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=dmitry.baryshkov@foundries.io \
    --cc=eugen.hristev@linaro.org \
    --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=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