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

Include I2C bus details in ft5x06 and goodix touch driver names #5703

Merged
merged 2 commits into from
Nov 22, 2023

Conversation

6by9
Copy link
Contributor

@6by9 6by9 commented Nov 8, 2023

raspberrypi/bookworm-feedback#138

The name is only taken as a const char *, so there's no easy way for the framework to do this munge.

Adds the I2C bus number and address to the name, so DSI-2 wants to be associated with 4-0038 generic ft5x06 (79), and DSI-1 with 6-0038 generic ft5x06 (79) for Pi5, and 10-0038 generic ft5x06 (79) with DSI-1 on Pi0-4.
Goodix is used by the HyperPixel and a few other displays, hence converted that one too.

Needs the relevant wayfire.ini updates before merging / releasing, hence draft for now.

@lurch
Copy link
Contributor

lurch commented Nov 9, 2023

with DSI-1 on Pi0-4.

Pi1-4, as Pi0 doesn't have a DSI connector 😉

@6by9 6by9 marked this pull request as ready for review November 22, 2023 18:44
6by9 added 2 commits November 22, 2023 18:45
libinput uses the input device name alone. If you have two
identical input devices, then there is no way to differentiate
between them, and in the case of touchscreens that means no
way to associate them with the appropriate display device.

Add the I2C bus and address to the start of the input device
name so that the name is always unique within the system.

Signed-off-by: Dave Stevenson <[email protected]>
libinput uses the input device name alone. If you have two
identical input devices, then there is no way to differentiate
between them, and in the case of touchscreens that means no
way to associate them with the appropriate display device.

Add the I2C bus and address to the start of the input device
name so that the name is always unique within the system.

Signed-off-by: Dave Stevenson <[email protected]>
@6by9 6by9 force-pushed the rpi-6.1.y-touchscreens branch from f2efc75 to b915a85 Compare November 22, 2023 18:45
@6by9
Copy link
Contributor Author

6by9 commented Nov 22, 2023

Simon has made the relevant ini file changes, so this is ready for review and merge.

@pelwell pelwell merged commit a420bbd into raspberrypi:rpi-6.1.y Nov 22, 2023
popcornmix added a commit to raspberrypi/firmware that referenced this pull request Nov 23, 2023
…OGUE_GAIN

See: raspberrypi/linux#5711

kernel: DRM fixes
See: raspberrypi/linux#5716

kernel: drm: vc4: Free the dlist alloc immediately if it never hit the hw
See: raspberrypi/linux#5733

kernel: Include I2C bus details in ft5x06 and goodix touch driver names
See: raspberrypi/linux#5703

kernel: drm: vc4: Block swiotlb bounce buffers being imported as dmabuf
See: raspberrypi/linux#5734
popcornmix added a commit to raspberrypi/rpi-firmware that referenced this pull request Nov 23, 2023
…OGUE_GAIN

See: raspberrypi/linux#5711

kernel: DRM fixes
See: raspberrypi/linux#5716

kernel: drm: vc4: Free the dlist alloc immediately if it never hit the hw
See: raspberrypi/linux#5733

kernel: Include I2C bus details in ft5x06 and goodix touch driver names
See: raspberrypi/linux#5703

kernel: drm: vc4: Block swiotlb bounce buffers being imported as dmabuf
See: raspberrypi/linux#5734
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.

3 participants