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

Daisy touchscreen compatible #57

Merged
merged 3 commits into from
Dec 11, 2023

Conversation

ntonnaett
Copy link

Mostly copied from msm8916-mainline#217, but for msm8953 and Xiaomi Daisy.

vknecht and others added 2 commits August 26, 2023 14:12
In the case a device has variants with specific touchscreen
coupled with specific panel, it's useful to be able to declare
both touchscreens with status "disabled" in Linux DTS, and have
lk2nd NOP this status for the one associated with detected panel.

Co-authored-by: Niklas Henrik Tonnätt <[email protected]>
Co-authored-by: Nils Tonnaett <[email protected]>
Use the touchscreen-compatible support to associate the
Goodix GT917D touchscreen with panels Ilitek ili7807-fhdplus, and
Tianma otm1911-fhdplus and Focaltech ft5406 with panel Himax
hx8399c-fhdplus.

Co-authored-by: Niklas Henrik Tonnätt <[email protected]>
@alikates
Copy link
Member

Is this strictly needed? When enabling all touchscreen drivers, all but one will probe so there won't be any issues. I guess this might be a cleaner solution that saves us from having probe error messages on boot.

Also, are we sure that a panel model has always the same touchscreen controller?

@alikates
Copy link
Member

Btw, don't we need to set the status to 'okay' instead of NOPing the property?

@apolemus
Copy link

apolemus commented Aug 27, 2023

Is this strictly needed? When enabling all touchscreen drivers, all but one will probe so there won't be any issues. I guess this might be a cleaner solution that saves us from having probe error messages on boot.

Also, are we sure that a panel model has always the same touchscreen controller?

Enabling all touchscreen drivers in linux won’t work because the probe failing driver will claim the pins the other driver wants to use. IRQF_PROBE_SHARED might introduce latency and had to be added to the touchscreen drivers. So it seems there are two clean solutions:

  1. splitting the daisy device tree (like xiaomi-beryllium or pinephone) but then we have to identify hardware revisions or alike somehow (our hw-revision number with ili7807-fhdplus + gt917d is 10001),
  2. the touchscreen-compatible approach.

Sure, we don’t know if the panel touchscreen pairing is always this way but looking at this it very much seems this way.

@apolemus
Copy link

@ungeskriptet Since you added the otm1911-fhdplus panel and mentioned the use of the gt917d in the postmarketOS mainline channel. Do you have indeed this panel with the Goodix GT917D on your daisy?

@ungeskriptet
Copy link

@apolemus Yes it has gt917d and otm1911-fhdplus. I don't have daisy though, I helped a friend add support for it.

@ntonnaett
Copy link
Author

Btw, don't we need to set the status to 'okay' instead of NOPing the property?

When I created the draft PR, I only copied the source from msm8916. As it works with this change, I assumed NOPing just resets 'status' to the default value. This confirms my assumptions. NULL and 'okay' both return true.

I think this is ready to be merged.

@ntonnaett ntonnaett marked this pull request as ready for review October 21, 2023 21:26
@ntonnaett
Copy link
Author

I also just add the touchscreen-compatible properties for the sakura. They seem to have the same display/touchscreen combinations.

Use the touchscreen-compatible support to associate the
Goodix GT917D touchscreen with panels Ilitek ili7807-fhdplus, and
Tianma otm1911-fhdplus and Focaltech ft5406 with panel Himax
hx8399c-fhdplus.

Co-authored-by: Niklas Henrik Tonnätt <[email protected]>
@ntonnaett
Copy link
Author

Could we merge this?

@M0Rf30 M0Rf30 merged commit 67401d5 into msm8953-mainline:main Dec 11, 2023
@umeiko
Copy link

umeiko commented Jan 2, 2024

mido can be fixed in this way too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants