Ilitek ILI2131 with CM4 Trixie
Hi Folks, I was delighted to see that Trixie has built-in support for our new ILI2131 touchscreen. I have written a Python script that tests the interrupt and reads the xy coordinates of touches - so far all good. However, despite the touchscreen being shown in the Control Centre / Screens menu, the touches don't move the cursor. Any ideas please?
Here is my config.txt:
Here is my config.txt:
Code: Select all
# For more options and information see
# http://rptl.io/configtxt
# Some settings may impact device functionality. See link above for details
dt_debug=1
# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Enable audio (loads snd_bcm2835)
#dtparam=audio=on
# Additional overlays and parameters are documented
# /boot/firmware/overlays/README
# Automatically load overlays for detected cameras
#camera_auto_detect=1
# Automatically load overlays for detected DSI displays
#display_auto_detect=1
# Automatically load initramfs files, if found
auto_initramfs=1
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
dtoverlay=sn65dsi83-g101ice
max_framebuffers=2
dtoverlay=ilitek251x,interrupt=17
dtoverlay=tca8418
# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1
# Run in 64-bit mode
arm_64bit=1
# Disable compensation for displays with overscan
disable_overscan=1
# Run as fast as firmware / board allows
arm_boost=1
[cm4]
# Enable host mode on the 2711 built-in XHCI USB controller.
# This line should be removed if the legacy DWC2 controller is required
# (e.g. for USB device mode) or if USB support is not required.
otg_mode=1
[cm5]
dtoverlay=dwc2,dr_mode=host
[all]
enable_uart=1
Last edited by skyfish on Fri Nov 14, 2025 10:24 am, edited 1 time in total.
- DougieLawson
- Posts: 43618
- Joined: Sun Jun 16, 2013 11:19 pm
Re: Ilitek ILI2131 with CM4 Trixie
When you write "code" in a post can you enclose it in [CODE]...[/CODE] tags as that makes it easier to read, easier to copy and generally easier. It doesn't matter if it's python, c, c++, c#, config.txt, html or anything.
This is plain text
This is plain text
Code: Select all
This is plain text (in code tags with a tab in front)Languages using left-hand whitespace for syntax are ridiculous
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
DMs sent on Bluesky or by LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
evtest is the lowest level test apps for input devices ("sudo apt install evtest" if not already installed).
That driver will only send any touch events if it gets the relevant interrupt first. Check /proc/interrupts to see if you're getting interrupts from the relevant GPIO (you've set it as GPIO17, which would be pin 11 on the header.
That driver will only send any touch events if it gets the relevant interrupt first. Check /proc/interrupts to see if you're getting interrupts from the relevant GPIO (you've set it as GPIO17, which would be pin 11 on the header.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
Re: Ilitek ILI2131 with CM4 Trixie
Hi 6by9,
Thanks for your suggestions.
cat /proc/interrupts shows
The number increases when I tap the screen, so it looks like the interrupts are working.
evtest gives
Although it says "Testing..." when I tap the screen, there is no output.
Thanks for your suggestions.
cat /proc/interrupts shows
Code: Select all
42: 106 0 0 0 pinctrl-bcm2835 17 Level ili251x
evtest gives
Code: Select all
sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: vc4-hdmi-0
/dev/input/event1: vc4-hdmi-1
/dev/input/event2: ILI210x Touchscreen
Select the device event number [0-2]: 2
Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "ILI210x Touchscreen"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 330 (BTN_TOUCH)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 0
Min 0
Max 16383
Event code 1 (ABS_Y)
Value 0
Min 0
Max 9599
Event code 24 (ABS_PRESSURE)
Value 0
Min 0
Max 10
Event code 47 (ABS_MT_SLOT)
Value 0
Min 0
Max 9
Event code 53 (ABS_MT_POSITION_X)
Value 0
Min 0
Max 16383
Event code 54 (ABS_MT_POSITION_Y)
Value 0
Min 0
Max 9599
Event code 57 (ABS_MT_TRACKING_ID)
Value 0
Min 0
Max 65535
Event code 58 (ABS_MT_PRESSURE)
Value 0
Min 0
Max 10
Properties:
Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Last edited by skyfish on Mon Nov 17, 2025 9:21 am, edited 1 time in total.
Re: Ilitek ILI2131 with CM4 Trixie
sudo i2cdetect -y 1
gives
The "UU" is at the Ilitek chip address.
dmesg output:
gives
Code: Select all
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- 62 -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Code: Select all
lsmod | grep ili
ili210x 20480 0
crc_ccitt 12288 1 ili210x
Code: Select all
[ 6.475651] input: ILI210x Touchscreen as /devices/platform/soc/fe804000.i2c/i2c-1/1-0041/input/input0
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
A fair number of the overlays have been contributed by others, so whilst they are in the Pi kernel there is limited support provided for them.
ili251x was added with https://github.com/raspberrypi/linux/pull/2926
Just looking at the tree, https://github.com/raspberrypi/linux/pull/6499/ added support for the Waveshare 13.3" 1080p display that also uses this touch controller driver. As they don't have the interrupt line wired up, they added a polling mode. For a quick test, it'd be worth trying the same thing with your panel - remove the "interrupt-parent" and "interrupts" lines from the overlay.
The overlay does appear to default the touchscreen size to being 16384x9600 which is huge! I would expect to need the "size_x" and "size_y" overrides to set the input size appropriately. I wouldn't expect that to stop it producing events at all though.
Add "trace_event=i2c" to the start of the line in /boot/firmware/cmdline.txt, and then "sudo cat /sys/kernel/debug/tracing/trace" to observe the I2C commands going to the touch controller. I haven't looked at that one before, but between the datasheet and driver it should be possible to work out what it is reporting.
ili251x was added with https://github.com/raspberrypi/linux/pull/2926
Just looking at the tree, https://github.com/raspberrypi/linux/pull/6499/ added support for the Waveshare 13.3" 1080p display that also uses this touch controller driver. As they don't have the interrupt line wired up, they added a polling mode. For a quick test, it'd be worth trying the same thing with your panel - remove the "interrupt-parent" and "interrupts" lines from the overlay.
The overlay does appear to default the touchscreen size to being 16384x9600 which is huge! I would expect to need the "size_x" and "size_y" overrides to set the input size appropriately. I wouldn't expect that to stop it producing events at all though.
Add "trace_event=i2c" to the start of the line in /boot/firmware/cmdline.txt, and then "sudo cat /sys/kernel/debug/tracing/trace" to observe the I2C commands going to the touch controller. I haven't looked at that one before, but between the datasheet and driver it should be possible to work out what it is reporting.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
- aBUGSworstnightmare
- Posts: 13465
- Joined: Tue Jun 30, 2015 1:35 pm
Re: Ilitek ILI2131 with CM4 Trixie
where is your overlay? Post it please.
Sorry, but will not bother with Python script etc.
Sorry, but will not bother with Python script etc.
Last edited by aBUGSworstnightmare on Mon Nov 17, 2025 12:09 pm, edited 2 times in total.
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
https://github.com/raspberrypi/linux/bl ... verlay.dtsaBUGSworstnightmare wrote: ↑Mon Nov 17, 2025 11:54 amwhere is your overlay? Post it please.
Sorry, but will not bother with Python script etc.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
- aBUGSworstnightmare
- Posts: 13465
- Joined: Tue Jun 30, 2015 1:35 pm
Re: Ilitek ILI2131 with CM4 Trixie
ah! Didn't know that was there! so can remove mine.6by9 wrote: ↑Mon Nov 17, 2025 12:01 pmhttps://github.com/raspberrypi/linux/bl ... verlay.dtsaBUGSworstnightmare wrote: ↑Mon Nov 17, 2025 11:54 amwhere is your overlay? Post it please.
Sorry, but will not bother with Python script etc.
EDIT: looking at the DT bindings (https://github.com/raspberrypi/linux/bl ... s_i2c.yaml) the interrupt should be level triggered (and not edge https://github.com/raspberrypi/linux/bl ... ay.dts#L32) and the size makes no sense at all (https://github.com/raspberrypi/linux/bl ... ts#L33-L34)
RESET (of ilitek IC) is also not defined from the in-tree overlay -> how ar you controlling it on your HW?
Re: Ilitek ILI2131 with CM4 Trixie
Thanks. I set size_x=1280,size_y=8006by9 wrote: ↑Mon Nov 17, 2025 11:35 amA fair number of the overlays have been contributed by others, so whilst they are in the Pi kernel there is limited support provided for them.
ili251x was added with https://github.com/raspberrypi/linux/pull/2926
Just looking at the tree, https://github.com/raspberrypi/linux/pull/6499/ added support for the Waveshare 13.3" 1080p display that also uses this touch controller driver. As they don't have the interrupt line wired up, they added a polling mode. For a quick test, it'd be worth trying the same thing with your panel - remove the "interrupt-parent" and "interrupts" lines from the overlay.
The overlay does appear to default the touchscreen size to being 16384x9600 which is huge! I would expect to need the "size_x" and "size_y" overrides to set the input size appropriately. I wouldn't expect that to stop it producing events at all though.
Add "trace_event=i2c" to the start of the line in /boot/firmware/cmdline.txt, and then "sudo cat /sys/kernel/debug/tracing/trace" to observe the I2C commands going to the touch controller. I haven't looked at that one before, but between the datasheet and driver it should be possible to work out what it is reporting.
This is the output from sudo cat /sys/kernel/debug/tracing/trace. There's one or more entries for each touch, but the read data doesn't look very plausible as all entries are identical:
Code: Select all
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00]
irq/42-ili251x-632 [001] ..... 127.895458: i2c_result: i2c-1 n=1 ret=1
irq/42-ili251x-632 [001] ..... 127.901577: i2c_write: i2c-1 #0 a=041 f=0000 l=1 [10]
irq/42-ili251x-632 [001] ..... 127.901802: i2c_result: i2c-1 n=1 ret=1
irq/42-ili251x-632 [001] ..... 127.901804: i2c_read: i2c-1 #0 a=041 f=0001 l=31
irq/42-ili251x-632 [001] ..... 127.904733: i2c_reply: i2c-1 #0 a=041 f=0001 l=31 [48-40-57-13-64-26-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00]
irq/42-ili251x-632 [001] ..... 127.904734: i2c_result: i2c-1 n=1 ret=1
irq/42-ili251x-632 [001] ..... 127.910781: i2c_write: i2c-1 #0 a=041 f=0000 l=1 [10]
irq/42-ili251x-632 [001] ..... 127.911005: i2c_result: i2c-1 n=1 ret=1
irq/42-ili251x-632 [001] ..... 127.911008: i2c_read: i2c-1 #0 a=041 f=0001 l=31
irq/42-ili251x-632 [001] ..... 127.913936: i2c_reply: i2c-1 #0 a=041 f=0001 l=31 [48-00-57-13-64-26-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00]
irq/42-ili251x-632 [001] ..... 127.913938: i2c_result: i2c-1 n=1 ret=1
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
I looked at that one too. It's only the comment in the overlay that is wrong. https://elixir.bootlin.com/linux/v6.17. ... /irq.h#L18aBUGSworstnightmare wrote: ↑Mon Nov 17, 2025 12:08 pmah! Didn't know that was there! so can remove mine.6by9 wrote: ↑Mon Nov 17, 2025 12:01 pmhttps://github.com/raspberrypi/linux/bl ... verlay.dtsaBUGSworstnightmare wrote: ↑Mon Nov 17, 2025 11:54 amwhere is your overlay? Post it please.
Sorry, but will not bother with Python script etc.
EDIT: looking at the DT bindings (https://github.com/raspberrypi/linux/bl ... s_i2c.yaml) the interrupt should be level triggered (and not edge https://github.com/raspberrypi/linux/bl ... ay.dts#L32)
Code: Select all
#define IRQ_TYPE_LEVEL_LOW 8I'd already said as much ;)aBUGSworstnightmare wrote:and the size makes no sense at all (https://github.com/raspberrypi/linux/bl ... ts#L33-L34)
It's an optional property. https://elixir.bootlin.com/linux/v6.17. ... i2c.c#L565aBUGSworstnightmare wrote:RESET (of ilitek IC) is also not defined from the in-tree overlay -> how ar you controlling it on your HW?
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
Oh, subtle detail.skyfish wrote: ↑Mon Nov 17, 2025 12:31 pmThis is the output from sudo cat /sys/kernel/debug/tracing/trace. There's one or more entries for each touch, but the read data doesn't look very plausible as all entries are identical:
Code: Select all
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00] irq/42-ili251x-632 [001] ..... 127.895458: i2c_result: i2c-1 n=1 ret=1 irq/42-ili251x-632 [001] ..... 127.901577: i2c_write: i2c-1 #0 a=041 f=0000 l=1 [10] irq/42-ili251x-632 [001] ..... 127.901802: i2c_result: i2c-1 n=1 ret=1 irq/42-ili251x-632 [001] ..... 127.901804: i2c_read: i2c-1 #0 a=041 f=0001 l=31 irq/42-ili251x-632 [001] ..... 127.904733: i2c_reply: i2c-1 #0 a=041 f=0001 l=31 [48-40-57-13-64-26-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00] irq/42-ili251x-632 [001] ..... 127.904734: i2c_result: i2c-1 n=1 ret=1 irq/42-ili251x-632 [001] ..... 127.910781: i2c_write: i2c-1 #0 a=041 f=0000 l=1 [10] irq/42-ili251x-632 [001] ..... 127.911005: i2c_result: i2c-1 n=1 ret=1 irq/42-ili251x-632 [001] ..... 127.911008: i2c_read: i2c-1 #0 a=041 f=0001 l=31 irq/42-ili251x-632 [001] ..... 127.913936: i2c_reply: i2c-1 #0 a=041 f=0001 l=31 [48-00-57-13-64-26-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00] irq/42-ili251x-632 [001] ..... 127.913938: i2c_result: i2c-1 n=1 ret=1
The ilitek251x overlay uses the compatible string "ilitek,ili251x", which loads the ili210x.c driver.
The ILI2131 driver you're after is in the ilitek_ts_i2c.c driver. That module isn't built in the standard Pi kernel, and there isn't an overlay for it.
Wrong driver means it doesn't work :(
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
Re: Ilitek ILI2131 with CM4 Trixie
Ah, okay, thanks. That would explain it! I'll try a custom build. I did this successfully for a previous (ACDC) touchscreen, but I found it necessary to disable checking for updates as any subsequent kernel patches sometimes caused the touchscreen driver to break.
Please could you leave this topic open until I can report back?
Please could you leave this topic open until I can report back?
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
Pull request at https://github.com/raspberrypi/linux/pull/7146
Once CI has completed (about 30mins), running "sudo rpi-update pulls/7146" should get you the appropriate kernel.
If it works then it can be merged, and that avoids having to make and risking losing custom kernels.
Forum threads get locked after 6 months to avoid necroposts, or if they get inflammatory.
Once CI has completed (about 30mins), running "sudo rpi-update pulls/7146" should get you the appropriate kernel.
If it works then it can be merged, and that avoids having to make and risking losing custom kernels.
Forum threads get locked after 6 months to avoid necroposts, or if they get inflammatory.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
Re: Ilitek ILI2131 with CM4 Trixie
That's a big improvement! It kind of works, except the mouse jumps off the screen when you touch the screen anywhere.
Here is the output of sudo evtest:
Touch top left
Touch bottom right
Code: Select all
dtoverlay=ilitek-ts-i2c,interrupt=17,sizex=1280,sizey=800
Touch top left
Code: Select all
vent: time 1763400317.091884, -------------- SYN_REPORT ------------
Event: time 1763400388.506610, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 43
Event: time 1763400388.506610, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 16061
Event: time 1763400388.506610, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 16045
Event: time 1763400388.506610, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1763400388.506610, type 3 (EV_ABS), code 0 (ABS_X), value 16061
Event: time 1763400388.506610, type 3 (EV_ABS), code 1 (ABS_Y), value 16045
Code: Select all
vent: time 1763400388.598900, -------------- SYN_REPORT ------------
Event: time 1763400390.970409, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 44
Event: time 1763400390.970409, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 466
Event: time 1763400390.970409, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 752
Event: time 1763400390.970409, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1763400390.970409, type 3 (EV_ABS), code 0 (ABS_X), value 466
Event: time 1763400390.970409, type 3 (EV_ABS), code 1 (ABS_Y), value 752
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
That would imply that the touch device does produce a HUGE range of position co-ords, and therefore the sizex and sizey properties probably should be set to something very high. It'll be a case of reading the datasheet to check....
You also probably want to also have the "touchscreen-inverted-x" and "touchscreen-inverted-y" properties set, as it sounds like the origin differs from your display. Those can be added as overrides....
You also probably want to also have the "touchscreen-inverted-x" and "touchscreen-inverted-y" properties set, as it sounds like the origin differs from your display. Those can be added as overrides....
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
The driver reads the min and max co-ord values from the touch controller, and notifies the rest of the system accordingly
https://github.com/torvalds/linux/blob/ ... #L297-L300
https://github.com/torvalds/linux/blob/ ... #L477-L480
So there's no need for the overlay to specify a size.
PR updated to remove sizex/sizey, and adds invx/invy. Again CI should do the business in the next 30mins.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
- aBUGSworstnightmare
- Posts: 13465
- Joined: Tue Jun 30, 2015 1:35 pm
Re: Ilitek ILI2131 with CM4 Trixie
https://github.com/raspberrypi/linux/bl ... ay.dts#L32
should be changed to
Code: Select all
interrupts = <4 8>; // high-to-low edge triggered
Code: Select all
interrupts = <4 8>; // Interrupt is active low
Re: Ilitek ILI2131 with CM4 Trixie
Thanks sooo much 6by9, that's amazing!!6by9 wrote: ↑Mon Nov 17, 2025 6:05 pmThe driver reads the min and max co-ord values from the touch controller, and notifies the rest of the system accordingly
https://github.com/torvalds/linux/blob/ ... #L297-L300
https://github.com/torvalds/linux/blob/ ... #L477-L480
So there's no need for the overlay to specify a size.
PR updated to remove sizex/sizey, and adds invx/invy. Again CI should do the business in the next 30mins.
Will it be merged into the Trixie download now?
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
Does that mean it works for your touch controller? If so then I'll merge it.
The main rpi-update branch will gain the patch first, and apt will get updated in due course when anything significant is released.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
Re: Ilitek ILI2131 with CM4 Trixie
Hi 6by9. Yes, to be clear, it works perfectly. Even has a long-press right-click emulation :)
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
Thanks for the confirmation.
I think we should be good to merge, but I'm just waiting for a colleague to give it a quick follow-up review.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
- 6by9
- Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator - Posts: 18540
- Joined: Wed Dec 04, 2013 11:27 am
Re: Ilitek ILI2131 with CM4 Trixie
PR now merged.
Software Engineer at Raspberry Pi Ltd. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
I'm not interested in doing contracts for bespoke functionality - please don't ask.
Jump to
- Community
- General discussion
- Announcements
- Other languages
- Deutsch
- Español
- Français
- Italiano
- Nederlands
- 日本語
- Polski
- Português
- Русский
- Türkçe
- User groups and events
- Raspberry Pi Official Magazine
- Using the Raspberry Pi
- Beginners
- Troubleshooting
- Advanced users
- Assistive technology and accessibility
- Education
- Picademy
- Teaching and learning resources
- Staffroom, classroom and projects
- Astro Pi
- Mathematica
- High Altitude Balloon
- Weather station
- Programming
- C/C++
- Java
- Python
- Scratch
- Other programming languages
- Windows 10 for IoT
- Wolfram Language
- Bare metal, Assembly language
- Graphics programming
- OpenGLES
- OpenVG
- OpenMAX
- General programming discussion
- Projects
- Networking and servers
- Automation, sensing and robotics
- Graphics, sound and multimedia
- Other projects
- Gaming
- Media centres
- AIY Projects
- Hardware and peripherals
- Camera board
- Compute Module
- Official Display
- HATs and other add-ons
- Device Tree
- Interfacing (DSI, CSI, I2C, etc.)
- Keyboard computers (400, 500, 500+)
- Raspberry Pi Pico
- General
- SDK
- MicroPython
- Other RP2040 boards
- Zephyr
- Rust
- AI Accelerator
- AI Camera - IMX500
- Hailo
- Software
- Raspberry Pi OS
- Raspberry Pi Connect
- Raspberry Pi Desktop for PC and Mac
- Beta testing
- Other
- Android
- Debian
- FreeBSD
- Gentoo
- Linux Kernel
- NetBSD
- openSUSE
- Plan 9
- Puppy
- Arch
- Pidora / Fedora
- RISCOS
- Ubuntu
- Ye Olde Pi Shoppe
- For sale
- Wanted
- Off topic
- Off topic discussion