Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FT5406 (official raspberry touchscreen) wrong touchscreen resolution #8272

Closed
bahamut657 opened this issue Feb 25, 2018 · 6 comments
Closed
Labels
hwdb needs-reporter-feedback ❓ There's an unanswered question, the reporter needs to answer

Comments

@bahamut657
Copy link

bahamut657 commented Feb 25, 2018

  • Bug report
    ArchlinuxARM, libinput 1.10, kernel 4.14.18-1

FT5406 is recognized by the kernel as 800x600 (while it is 800x480)
Already discussed with @whot
https://bugs.freedesktop.org/show_bug.cgi?id=105153

It was working with no problem before kernel update.
Seems like a 60-evdev.hwdb patch is needed.
I patch it like so
evdev:name:FT5406*
EVDEV_ABS_00=2:800:1
EVDEV_ABS_01=2:480:1
EVDEV_ABS_35=2:800:1
EVDEV_ABS_36=2:480:1

@boucman
Copy link
Contributor

boucman commented Feb 25, 2018

can you make that a proper pull request ? it's easier to handle...

@whot whot added the needs-reporter-feedback ❓ There's an unanswered question, the reporter needs to answer label Feb 25, 2018
@whot
Copy link
Contributor

whot commented Feb 25, 2018

I just had another look at the driver that this thing runs (drivers/input/touchscreen/edt-ft5x06.c) and it contains the following comment where the x/y axes are set up:

 /* Unknown maximum values. Specify via devicetree */

which would indicate that this may be a devicetree issue (which would also explain the change during a kernel update). I'm not overly famiilar with device tree but please do investigate this first. This could be an ArchlinuxARM kernel bug

@bahamut657
Copy link
Author

So, which next steps?
Can I post on ArchlinuxARM Forum the issue?
I've do it 2 weeks ago but none response (and I perform sys upgrade any days with no solution)

@whot
Copy link
Contributor

whot commented Mar 2, 2018

please ping them again. see if you can figure out which kernel version broke it by installing older versions.

@bahamut657
Copy link
Author

bahamut657 commented Mar 2, 2018

I've re-ping them with a new post in the ArchlinuxARM forum.
Here is the link.
https://archlinuxarm.org/forum/viewtopic.php?f=15&t=12605

Hoping they resolve the problem soon. I let you now on update

Thanks to all for the support

@poettering
Copy link
Member

Closing this here, as this appears to be a devicetree issue. Please reopen if there's something to fix in hwdb after all. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hwdb needs-reporter-feedback ❓ There's an unanswered question, the reporter needs to answer
Development

No branches or pull requests

4 participants