From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Eric Gonçalves" <ghatto404@gmail.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/6] arm64: dts: qcom: r0q: add touchscreen support
Date: Tue, 14 Oct 2025 12:01:38 +0200 [thread overview]
Message-ID: <e114504e-4bdd-46b9-b708-8eebc3075163@oss.qualcomm.com> (raw)
In-Reply-To: <20251014044135.177210-4-ghatto404@gmail.com>
On 10/14/25 6:41 AM, Eric Gonçalves wrote:
> Enable the ST-Microelectronics FTS2BA61Y touchscreen. This patch
> depends on "Input: add support for the STM FTS2BA61Y touchscreen".
The second sentence doesn't really make sense to be included in
the git log
> The device has an issue where SPI 8 (the bus which the touchscreen is
> connected to) is not working properly right now, so
> spi-gpio is used instead.
Some Samsung devices used to use spi/i2c-gpio intentionally, also
on downstream. I'm assuming this isn't the case for r0q.
Did you enable gpi_dma1, qupv3_id_1 before spi8, when testing
that? I don't see any obvious errors in the dt that would cause
problems
Konrad
next prev parent reply other threads:[~2025-10-14 10:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 4:41 [PATCH v2 0/6] arm64: dts: qcom: r0q: enable more peripherals Eric Gonçalves
2025-10-14 4:41 ` [PATCH v2 1/6] arm64: dts: qcom: r0q: small refactor Eric Gonçalves
2025-10-14 4:41 ` [PATCH v2 2/6] arm64: dts: qcom: r0q: add gpio keys Eric Gonçalves
2025-10-14 9:59 ` Konrad Dybcio
2025-10-14 4:41 ` [PATCH v2 3/6] arm64: dts: qcom: r0q: add touchscreen support Eric Gonçalves
2025-10-14 10:01 ` Konrad Dybcio [this message]
2025-10-14 15:10 ` Ghatto
2025-10-14 15:17 ` Konrad Dybcio
2025-10-14 19:04 ` Ghatto
2025-10-16 10:06 ` Konrad Dybcio
2025-10-16 20:08 ` Ghatto
2025-10-17 8:20 ` Konrad Dybcio
2025-10-17 18:22 ` Eric Gonçalves
2025-10-20 12:18 ` Konrad Dybcio
2025-10-27 18:32 ` Eric Gonçalves
2025-10-29 9:50 ` Konrad Dybcio
2025-10-31 21:06 ` Ghatto
2025-11-04 14:53 ` Konrad Dybcio
2025-10-14 4:41 ` [PATCH v2 4/6] arm64: dts: qcom: r0q: enable max77705 fuelgauge Eric Gonçalves
2025-10-14 4:41 ` [PATCH v2 5/6] arm64: dts: qcom: r0q: enable ufs storage Eric Gonçalves
2025-10-14 10:02 ` Konrad Dybcio
2025-10-14 4:41 ` [PATCH v2 6/6] arm64: dts: qcom: r0q: fix reserved memory regions Eric Gonçalves
2025-10-14 10:02 ` Konrad Dybcio
2025-10-14 15:12 ` Ghatto
2025-10-14 9:58 ` [PATCH v2 0/6] arm64: dts: qcom: r0q: enable more peripherals Konrad Dybcio
2025-10-31 21:12 ` Ghatto
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=e114504e-4bdd-46b9-b708-8eebc3075163@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghatto404@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®