From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@somainline.org>
Subject: Re: [PATCH RFC v2 2/6] arm64: dts: qcom: sdm845-tama: Add Synaptics Touchscreen
Date: Mon, 13 Mar 2023 18:01:13 +0100 [thread overview]
Message-ID: <a131ffa0-1e9c-d355-16db-19e679ab0380@linaro.org> (raw)
In-Reply-To: <20230313-topic-tama_disp-v2-2-37ececf43770@linaro.org>
On 13.03.2023 17:32, Konrad Dybcio wrote:
> From: Konrad Dybcio <konrad.dybcio@somainline.org>
>
> Add required pins and RMI4 node to the common DT and remove it
> from Akatsuki, as it uses a different touch.
>
> Since the panels are super high tech proprietary incell, they
> need to be handled with very precise timings. As such the panel
> driver sets up the power rails and GPIOs and the touchscreen
> driver *has to* probe afterwards.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@somainline.org>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
[...]
> &i2c5 {
> - status = "okay";
> clock-frequency = <400000>;
> + status = "okay";
> +
> + touchscreen: touchscreen@2c {
> + compatible = "syna,rmi4-i2c";
> + reg = <0x2c>;
> +
> + interrupt-parent = <&tlmm>;
> + interrupts = <125 IRQ_TYPE_EDGE_FALLING>;
interrupts-extended
> + vdd-supply = <&vreg_l14a_1p8>;
> + /*
> + * This is a blatant abuse of OF, but the panel driver *needs*
> + * to probe first, as the power/gpio switching needs to be precisely
> + * timed in order for both the display and touch panel to function properly.
> + */
> + incell-supply = <&panel>;
> +
> + syna,reset-delay-ms = <220>;
> + syna,startup-delay-ms = <1000>;
> +
> + pinctrl-names = "default", "sleep";
> + pinctrl-0 = <&ts_default>;
> + pinctrl-1 = <&ts_sleep>;
swapped
>
> - /* Synaptics touchscreen @ 2c, 3c */
> + #address-cells = <1>;
> + #size-cells = <0>;
Konrad
next prev parent reply other threads:[~2023-03-13 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 16:32 [PATCH v2 0/6] Sony SDM845 panel and remoteproc enablement Konrad Dybcio
2023-03-13 16:32 ` [PATCH v2 1/6] arm64: dts: qcom: sdm845-tama: Add display nodes Konrad Dybcio
2023-03-13 17:00 ` Konrad Dybcio
2023-03-13 16:32 ` [PATCH RFC v2 2/6] arm64: dts: qcom: sdm845-tama: Add Synaptics Touchscreen Konrad Dybcio
2023-03-13 17:01 ` Konrad Dybcio [this message]
2023-03-13 16:32 ` [PATCH v2 3/6] arm64: dts: qcom: sdm845-tama: Add regulator-system-load to l14a/l28a Konrad Dybcio
2023-03-13 16:32 ` [PATCH v2 4/6] arm64: dts: qcom: sdm845-tama: Enable remoteprocs Konrad Dybcio
2023-03-13 16:32 ` [PATCH v2 5/6] arm64: dts: qcom: sdm845-tama: Enable GPU Konrad Dybcio
2023-03-13 16:32 ` [PATCH v2 6/6] arm64: dts: qcom: sdm845-tama: Enable GPI_DMA0/1 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=a131ffa0-1e9c-d355-16db-19e679ab0380@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).