From: David Heidelberg <david@ixit.cz>
To: Luca Weiss <luca.weiss@fairphone.com>,
Job Noorman <job@noorman.info>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: phone-devel@vger.kernel.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: sm7225-fairphone-fp4: Enable touchscreen
Date: Fri, 21 Aug 2026 14:41:46 +0200 [thread overview]
Message-ID: <e01a7430-1670-4aed-bb2d-3e505218d07a@ixit.cz> (raw)
In-Reply-To: <20260821-fp4-hx83112a-v1-3-474941bd8860@fairphone.com>
On 21/08/2026 09:12, Luca Weiss wrote:
> Add a node and pinctrl for the Himax HX83112A touchscreen found on this
> phone.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts | 21 ++++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts b/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts
> index 23f950067a08..ff609f7e1796 100644
> --- a/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts
> +++ b/arch/arm64/boot/dts/qcom/sm7225-fairphone-fp4.dts
> @@ -626,7 +626,19 @@ &i2c8 {
> clock-frequency = <400000>;
> status = "okay";
>
> - /* HX83112A touchscreen @ 48 */
> + touchscreen@48 {
> + compatible = "himax,hx83112a";
> + reg = <0x48>;
> +
> + interrupts-extended = <&tlmm 22 IRQ_TYPE_EDGE_FALLING>;
> + reset-gpios = <&tlmm 21 GPIO_ACTIVE_LOW>;
> +
> + touchscreen-size-x = <1080>;
> + touchscreen-size-y = <2340>;
> +
> + pinctrl-0 = <&touchscreen_default>;
> + pinctrl-names = "default";
> + };
> };
>
> &i2c10 {
> @@ -1117,6 +1129,13 @@ platform {
> &tlmm {
> gpio-reserved-ranges = <13 4>, <56 2>;
>
> + touchscreen_default: touchscreen-default-state {
> + pins = "gpio21", "gpio22";
I guess you could use here irq-pins {}, reset-pins {},
but with or without change,
Reviewed-by: David Heidelberg <david@ixit.cz>
> + function = "gpio";
> + drive-strength = <8>;
> + bias-pull-up;
> + };
> +
> qup_uart1_sleep_cts: qup-uart1-sleep-cts-state {
> pins = "gpio61";
> function = "gpio";
>
next prev parent reply other threads:[~2026-08-21 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 7:12 [PATCH 0/3] Add Himax HX83112A support for Fairphone 4 touchscreen Luca Weiss
2026-08-21 7:12 ` [PATCH 1/3] dt-bindings: touchscreen: trivial-touch: Add Himax HX83112A Luca Weiss
2026-08-21 7:12 ` [PATCH 2/3] Input: himax_hx83112b - Add HX83112A support Luca Weiss
2026-08-21 7:12 ` [PATCH 3/3] arm64: dts: qcom: sm7225-fairphone-fp4: Enable touchscreen Luca Weiss
2026-08-21 12:16 ` Abel Vesa
2026-08-21 12:41 ` David Heidelberg [this message]
2026-08-24 6:49 ` Konrad Dybcio
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=e01a7430-1670-4aed-bb2d-3e505218d07a@ixit.cz \
--to=david@ixit.cz \
--cc=Frank.Li@nxp.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=job@noorman.info \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=phone-devel@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