From: Val Packett <val@packett.cool>
To: Stanislav Zaikin <zstaseg@gmail.com>, devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, andersson@kernel.org,
konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS
Date: Mon, 23 Mar 2026 17:49:14 -0300 [thread overview]
Message-ID: <02913b5c-ce09-4fb7-a3dd-71bf7330439d@packett.cool> (raw)
In-Reply-To: <3bb1da4f-f2dc-421d-95f1-5bba9e3e1aec@gmail.com>
On 3/23/26 05:04, Stanislav Zaikin wrote:
> On 3/21/26 8:36 AM, Val Packett wrote:
>> Hello again :)
>>
>> On 3/5/26 6:39 AM, Stanislav Zaikin wrote:
>>> Xiaomi 12 Lite 5G is a handset released in 2022
>>> […]
>>> + touchscreen@0 {
>>> + compatible = "goodix,gt9916";
>>> + reg = <0>;
>>> +
>>> + interrupts-extended = <&tlmm 81 IRQ_TYPE_LEVEL_LOW>;
>>> +
>>> + reset-gpios = <&tlmm 105 GPIO_ACTIVE_LOW>;
>>> +
>>> + avdd-supply = <&vreg_l7c_3p0>;
>>> + vddio-supply = <&vreg_l2c_1p8>;
>>> +
>>> + spi-max-frequency = <5000000>;
>>> +
>>> + touchscreen-size-x = <10800>;
>>> + touchscreen-size-y = <24000>;
>>> […]
>>
>> I have noticed this previously and started wondering why the size was
>> 10x higher. Now with my own device (motorola-dubai) I actually found
>> out why…
>>
>> With the actual 1080x2400 size, the mm values reported by libinput
>> are 10x higher than what they should be, e.g. touching the bottom
>> right corner with libinput debug-events:
>>
>> event3 TOUCH_MOTION 2 +1.493s 0 (0) 98.80/98.75
>> (1067.00/2370.00mm)
>>
>> (2.4 meter tall phone! :D) which was mooooostly "fine" except Phosh's
>> on-screen keyboard was accidentally detecting super-fast down swipes
>> as I was typing normally, and suddenly closing the keyboard as I was
>> typing.
>>
> I wonder why some other devices with gt9916 (there are a couple in
> mainline) that specifies 1080x2400. I don't think we can make this
> assumption unless there was a mistake already in those mainline dts.
>
> Best regards,
> Stanislav
Not sure what you meant there..
I have not seen other devices do the 10800/24000 thing. Please set
1080/2400 (actual size not 10x larger).
~val
next prev parent reply other threads:[~2026-03-23 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 9:39 [PATCH v4 0/2] Add Xiaomi 12 Lite 5G (taoyao) device tree Stanislav Zaikin
2026-03-05 9:39 ` [PATCH v4 1/2] dt-bindings: arm: qcom: Add SM7325 Xiaomi 12 Lite 5G (taoyao) Stanislav Zaikin
2026-03-05 9:39 ` [PATCH v4 2/2] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS Stanislav Zaikin
2026-03-05 10:27 ` Konrad Dybcio
2026-03-16 4:05 ` Val Packett
2026-03-16 11:57 ` Stanislav Zaikin
2026-03-16 20:47 ` Val Packett
2026-03-18 8:22 ` Stanislav Zaikin
2026-03-21 7:36 ` Val Packett
2026-03-23 8:04 ` Stanislav Zaikin
2026-03-23 20:49 ` Val Packett [this message]
2026-03-24 8:07 ` Stanislav Zaikin
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=02913b5c-ce09-4fb7-a3dd-71bf7330439d@packett.cool \
--to=val@packett.cool \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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=zstaseg@gmail.com \
/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®