Goodix tp not work with I2C

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I used nanopi 2 fire from friendlyarm.I want to work with GT911 goodix touch panel. it has 6 pin: 1 for reset(i just connected to one of gpio), 2 for vdd3.3 volt,3 for GND, 4 for irq (i connect it to gpioc11) and SDA and SCL (connect to pin 3 & 5 as I2C-0). I download Linux kernel 4.4.y with this source code to active goodix touch screen:



git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1


I active goodix as the module in the kernel, and follow the page to compile kernel , at last copy the files to SD.(run make command,copy zimage and dtb file to boot sd). when I run this code:



root@NanoPi2-Fire:/# find -iname goodix*
./sys/bus/i2c/drivers/Goodix-TS
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d/goodix,irq-gpio


and for detect i2c i have:



root@NanoPi2-Fire:~# ls -l /sys/bus/i2c/devices/i2c*
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-0 -> ../../../devices/platform/c0000000.soc/c00a4000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-1 -> ../../../devices/platform/c0000000.soc/c00a5000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-2 -> ../../../devices/platform/c0000000.soc/c00a6000.i2c/i2c-2
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-3 -> ../../../devices/platform/c0000000.soc/c0000000.soc:i2c@3/i2c-3


and :



root@NanoPi2-Fire:/# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
modprobe goodix_ts
modprobe: FATAL: Module goodix_ts not found in directory /lib/modules/4.4.49-s5p4418


How to use gt911 on linux?










share|improve this question

















  • 1




    If you see Godix entries under /sys, the driver should already be loaded (verify with lsmod, assuming you compiled the driver as a module. If you didn't, compile it as a module, much easier to test this way.). Look into the output of dmesg after boot (or after you attach the device) to see if there are any godix-related messages (don't grep, context is important). If everything works, the touchpad will likely show up as kernel input devices in /dev/input (use evtest on them), but the dmesg output will probably give you details on that.
    – dirkt
    Dec 3 at 8:10










  • thanks for the reply. at first, can I ask you a question? Is there any config for 'int' and 'reset' gpio pin in the source of a kernel or in the device?where am I set irq and reset pin for GT911? and also I will check that you said. really thanks for help
    – H.Ghassami
    Dec 3 at 8:52







  • 1




    The proper drive should control the reset pin, and it should also route the IRQ pin properly so it generates an interrupt. First place to look is the source code of the driver and/or at the module parameters. (I haven't done this; I haven't even google dthe source code of the driver, but since you compiled it, you should have it).
    – dirkt
    Dec 3 at 9:19










  • @dirkt , thanks
    – H.Ghassami
    Dec 3 at 9:44














up vote
1
down vote

favorite












I used nanopi 2 fire from friendlyarm.I want to work with GT911 goodix touch panel. it has 6 pin: 1 for reset(i just connected to one of gpio), 2 for vdd3.3 volt,3 for GND, 4 for irq (i connect it to gpioc11) and SDA and SCL (connect to pin 3 & 5 as I2C-0). I download Linux kernel 4.4.y with this source code to active goodix touch screen:



git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1


I active goodix as the module in the kernel, and follow the page to compile kernel , at last copy the files to SD.(run make command,copy zimage and dtb file to boot sd). when I run this code:



root@NanoPi2-Fire:/# find -iname goodix*
./sys/bus/i2c/drivers/Goodix-TS
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d/goodix,irq-gpio


and for detect i2c i have:



root@NanoPi2-Fire:~# ls -l /sys/bus/i2c/devices/i2c*
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-0 -> ../../../devices/platform/c0000000.soc/c00a4000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-1 -> ../../../devices/platform/c0000000.soc/c00a5000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-2 -> ../../../devices/platform/c0000000.soc/c00a6000.i2c/i2c-2
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-3 -> ../../../devices/platform/c0000000.soc/c0000000.soc:i2c@3/i2c-3


and :



root@NanoPi2-Fire:/# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
modprobe goodix_ts
modprobe: FATAL: Module goodix_ts not found in directory /lib/modules/4.4.49-s5p4418


How to use gt911 on linux?










share|improve this question

















  • 1




    If you see Godix entries under /sys, the driver should already be loaded (verify with lsmod, assuming you compiled the driver as a module. If you didn't, compile it as a module, much easier to test this way.). Look into the output of dmesg after boot (or after you attach the device) to see if there are any godix-related messages (don't grep, context is important). If everything works, the touchpad will likely show up as kernel input devices in /dev/input (use evtest on them), but the dmesg output will probably give you details on that.
    – dirkt
    Dec 3 at 8:10










  • thanks for the reply. at first, can I ask you a question? Is there any config for 'int' and 'reset' gpio pin in the source of a kernel or in the device?where am I set irq and reset pin for GT911? and also I will check that you said. really thanks for help
    – H.Ghassami
    Dec 3 at 8:52







  • 1




    The proper drive should control the reset pin, and it should also route the IRQ pin properly so it generates an interrupt. First place to look is the source code of the driver and/or at the module parameters. (I haven't done this; I haven't even google dthe source code of the driver, but since you compiled it, you should have it).
    – dirkt
    Dec 3 at 9:19










  • @dirkt , thanks
    – H.Ghassami
    Dec 3 at 9:44












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I used nanopi 2 fire from friendlyarm.I want to work with GT911 goodix touch panel. it has 6 pin: 1 for reset(i just connected to one of gpio), 2 for vdd3.3 volt,3 for GND, 4 for irq (i connect it to gpioc11) and SDA and SCL (connect to pin 3 & 5 as I2C-0). I download Linux kernel 4.4.y with this source code to active goodix touch screen:



git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1


I active goodix as the module in the kernel, and follow the page to compile kernel , at last copy the files to SD.(run make command,copy zimage and dtb file to boot sd). when I run this code:



root@NanoPi2-Fire:/# find -iname goodix*
./sys/bus/i2c/drivers/Goodix-TS
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d/goodix,irq-gpio


and for detect i2c i have:



root@NanoPi2-Fire:~# ls -l /sys/bus/i2c/devices/i2c*
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-0 -> ../../../devices/platform/c0000000.soc/c00a4000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-1 -> ../../../devices/platform/c0000000.soc/c00a5000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-2 -> ../../../devices/platform/c0000000.soc/c00a6000.i2c/i2c-2
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-3 -> ../../../devices/platform/c0000000.soc/c0000000.soc:i2c@3/i2c-3


and :



root@NanoPi2-Fire:/# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
modprobe goodix_ts
modprobe: FATAL: Module goodix_ts not found in directory /lib/modules/4.4.49-s5p4418


How to use gt911 on linux?










share|improve this question













I used nanopi 2 fire from friendlyarm.I want to work with GT911 goodix touch panel. it has 6 pin: 1 for reset(i just connected to one of gpio), 2 for vdd3.3 volt,3 for GND, 4 for irq (i connect it to gpioc11) and SDA and SCL (connect to pin 3 & 5 as I2C-0). I download Linux kernel 4.4.y with this source code to active goodix touch screen:



git clone https://github.com/friendlyarm/linux.git -b nanopi2-v4.4.y --depth 1


I active goodix as the module in the kernel, and follow the page to compile kernel , at last copy the files to SD.(run make command,copy zimage and dtb file to boot sd). when I run this code:



root@NanoPi2-Fire:/# find -iname goodix*
./sys/bus/i2c/drivers/Goodix-TS
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d
./sys/firmware/devicetree/base/soc/i2c@c00a6000/goodix_ts@5d/goodix,irq-gpio


and for detect i2c i have:



root@NanoPi2-Fire:~# ls -l /sys/bus/i2c/devices/i2c*
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-0 -> ../../../devices/platform/c0000000.soc/c00a4000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-1 -> ../../../devices/platform/c0000000.soc/c00a5000.i2c/i2c-1
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-2 -> ../../../devices/platform/c0000000.soc/c00a6000.i2c/i2c-2
lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/bus/i2c/devices/i2c-3 -> ../../../devices/platform/c0000000.soc/c0000000.soc:i2c@3/i2c-3


and :



root@NanoPi2-Fire:/# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 2
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@NanoPi2-Fire:/# i2cdetect -y 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
modprobe goodix_ts
modprobe: FATAL: Module goodix_ts not found in directory /lib/modules/4.4.49-s5p4418


How to use gt911 on linux?







linux-kernel drivers touch-screen






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 2 at 11:32









H.Ghassami

1235




1235







  • 1




    If you see Godix entries under /sys, the driver should already be loaded (verify with lsmod, assuming you compiled the driver as a module. If you didn't, compile it as a module, much easier to test this way.). Look into the output of dmesg after boot (or after you attach the device) to see if there are any godix-related messages (don't grep, context is important). If everything works, the touchpad will likely show up as kernel input devices in /dev/input (use evtest on them), but the dmesg output will probably give you details on that.
    – dirkt
    Dec 3 at 8:10










  • thanks for the reply. at first, can I ask you a question? Is there any config for 'int' and 'reset' gpio pin in the source of a kernel or in the device?where am I set irq and reset pin for GT911? and also I will check that you said. really thanks for help
    – H.Ghassami
    Dec 3 at 8:52







  • 1




    The proper drive should control the reset pin, and it should also route the IRQ pin properly so it generates an interrupt. First place to look is the source code of the driver and/or at the module parameters. (I haven't done this; I haven't even google dthe source code of the driver, but since you compiled it, you should have it).
    – dirkt
    Dec 3 at 9:19










  • @dirkt , thanks
    – H.Ghassami
    Dec 3 at 9:44












  • 1




    If you see Godix entries under /sys, the driver should already be loaded (verify with lsmod, assuming you compiled the driver as a module. If you didn't, compile it as a module, much easier to test this way.). Look into the output of dmesg after boot (or after you attach the device) to see if there are any godix-related messages (don't grep, context is important). If everything works, the touchpad will likely show up as kernel input devices in /dev/input (use evtest on them), but the dmesg output will probably give you details on that.
    – dirkt
    Dec 3 at 8:10










  • thanks for the reply. at first, can I ask you a question? Is there any config for 'int' and 'reset' gpio pin in the source of a kernel or in the device?where am I set irq and reset pin for GT911? and also I will check that you said. really thanks for help
    – H.Ghassami
    Dec 3 at 8:52







  • 1




    The proper drive should control the reset pin, and it should also route the IRQ pin properly so it generates an interrupt. First place to look is the source code of the driver and/or at the module parameters. (I haven't done this; I haven't even google dthe source code of the driver, but since you compiled it, you should have it).
    – dirkt
    Dec 3 at 9:19










  • @dirkt , thanks
    – H.Ghassami
    Dec 3 at 9:44







1




1




If you see Godix entries under /sys, the driver should already be loaded (verify with lsmod, assuming you compiled the driver as a module. If you didn't, compile it as a module, much easier to test this way.). Look into the output of dmesg after boot (or after you attach the device) to see if there are any godix-related messages (don't grep, context is important). If everything works, the touchpad will likely show up as kernel input devices in /dev/input (use evtest on them), but the dmesg output will probably give you details on that.
– dirkt
Dec 3 at 8:10




If you see Godix entries under /sys, the driver should already be loaded (verify with lsmod, assuming you compiled the driver as a module. If you didn't, compile it as a module, much easier to test this way.). Look into the output of dmesg after boot (or after you attach the device) to see if there are any godix-related messages (don't grep, context is important). If everything works, the touchpad will likely show up as kernel input devices in /dev/input (use evtest on them), but the dmesg output will probably give you details on that.
– dirkt
Dec 3 at 8:10












thanks for the reply. at first, can I ask you a question? Is there any config for 'int' and 'reset' gpio pin in the source of a kernel or in the device?where am I set irq and reset pin for GT911? and also I will check that you said. really thanks for help
– H.Ghassami
Dec 3 at 8:52





thanks for the reply. at first, can I ask you a question? Is there any config for 'int' and 'reset' gpio pin in the source of a kernel or in the device?where am I set irq and reset pin for GT911? and also I will check that you said. really thanks for help
– H.Ghassami
Dec 3 at 8:52





1




1




The proper drive should control the reset pin, and it should also route the IRQ pin properly so it generates an interrupt. First place to look is the source code of the driver and/or at the module parameters. (I haven't done this; I haven't even google dthe source code of the driver, but since you compiled it, you should have it).
– dirkt
Dec 3 at 9:19




The proper drive should control the reset pin, and it should also route the IRQ pin properly so it generates an interrupt. First place to look is the source code of the driver and/or at the module parameters. (I haven't done this; I haven't even google dthe source code of the driver, but since you compiled it, you should have it).
– dirkt
Dec 3 at 9:19












@dirkt , thanks
– H.Ghassami
Dec 3 at 9:44




@dirkt , thanks
– H.Ghassami
Dec 3 at 9:44















active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485471%2fgoodix-tp-not-work-with-i2c%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485471%2fgoodix-tp-not-work-with-i2c%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?