If driver successfully read configuration when starting, and than not see any input, so looks like irq not working , possible cases:
1. Irq pin not connected 2. Irq not configured right way 17 февр. 2014 г. 14:07 пользователь "Oviron Electronics" < [email protected]> написал: > Dear Mikey > The driver is only one of the brunches that you need to get the TSP > working. > I'm pretty new to linux and C programing but had a look at lot of files in > OS. As you have other platform file names will differ from those I send. > Just get this in mind: > > 0.You have to be sure that TSP pins are properly conected to driver > expectations and IO pins definitions in your kernel - > /arch/arm/mach-s3c64xx/mach-mini6410.c > 1.You have to instantiate I2C device - > Documentation/i2c/instantiating-devices > 2.Define TS platform device - /arch/arm/mach-s3c64xx/dev-ts-mini6410.c > 3.Here is the driver - /drivers/input/touchscreen/zet6221_i2c.c > 4.I don't know if this is important - > /arch/arm/plat-samsung/include/plat/ts.h > > You can try your driver with command modprobe drivername (modprobe > zet6221_i2c for my one) > > As I did not run my ZET6221 TSP yet because I had another work, will be > interesting with your work. Pls, send info. If you have some questions I > can try to answer also. > > Regards > > *Ilian Tsachev* > *General manager* > Oviron Electronics Ltd. > Bulgaria, Varna > Tel. +359 887 626483 > www.ovironelectronics.com > > *P* *Please consider the environment before printing this email* > > > On 16 February 2014 19:52, Mikael R <[email protected]> wrote: > >> Hi! >>> >>> I cant seem to get this one working, i have a A13-mid tablet (Q88) >>>> >>> I have built the driver from wingrimes git rep. >>> >>> everything seems to load, but it does not register any events >>> >>> >> uname -a >> Linux linaro-alip 3.4.61 #6 PREEMPT Sat Feb 15 14:00:57 CET 2014 armv7l >> armv7l armv7l GNU/Linux >> >> Relevant code from script.bin >> [product] >> version = "1.0" >> machine = "A13-EVB-V1.0" >> >> [ctp_para] >> ctp_used = 1 >> ctp_name = "zet6221_ts" >> ctp_twi_id = 1 >> ctp_twi_addr = 0x76 >> ctp_screen_max_x = 800 >> ctp_screen_max_y = 480 >> ctp_revert_x_flag = 0 >> ctp_revert_y_flag = 0 >> ctp_exchange_x_y_flag = 0 >> ctp_int_port = port:PG11<6><default><default><default> >> ctp_wakeup = port:PB03<1><default><default><1> >> >> Relevant data from dmesg >> >> [ 13.658993] zet_ts_init >> [ 13.661763] ctp_fetch_sysconfig_para. >> [ 13.675673] ctp_fetch_sysconfig_para: ctp_twi_id is 1. >> [ 13.729491] ctp_fetch_sysconfig_para: screen_max_x = 800. >> [ 13.780820] ctp_fetch_sysconfig_para: screen_max_y = 480. >> [ 13.785094] ctp_fetch_sysconfig_para: revert_x_flag = 0. >> [ 13.877970] ctp_fetch_sysconfig_para: revert_y_flag = 0. >> [ 13.937503] ctp_fetch_sysconfig_para: exchange_x_y_flag = 0. >> [ 13.964502] zet_ts_init:normal_i2c:0x76.normal_i2c[1]:0xfffe. >> [ 14.002128] ctp_init_platform_resource: No valid reset wire defined in >> fex. >> [ 14.039015] ctp_init_platform_resource: No valid power port wire >> defined in fex. >> [ 14.081126] ctp_wakeup. >> [ 14.325072] ctp_detect: Detected chip zet6221_ts at adapter 1, address >> 0x76 >> [ 14.338361] input: zet6221_ts as >> /devices/platform/sunxi-i2c.1/i2c-1/1-0076/input/input2 >> [ 14.351157] ctp_set_irq_mode: config gpio to int mode. >> [ 14.371161] ctp_set_irq_mode, 188: gpio_int_info, port = 7, port_num = >> 11. >> [ 14.394004] INTERRUPT CONFIG >> [ 14.404607] Device information. >> [ 14.414790] x_res=65535,y_res=65535,x_t=255,y_t=255,df=255 >> >> Relevant data from /var/log/Xorg.0.log >> >> [ 17.677] (II) config/udev: Adding input device axp20-supplyer >> (/dev/input/event0) >> [ 17.677] (**) axp20-supplyer: Applying InputClass "evdev keyboard >> catchall" >> [ 17.677] (II) LoadModule: "evdev" >> [ 17.678] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so >> [ 17.688] (II) Module evdev: vendor="X.Org Foundation" >> [ 17.688] compiled for 1.13.3, module version = 2.7.3 >> [ 17.688] Module class: X.Org XInput Driver >> [ 17.688] ABI class: X.Org XInput driver, version 18.0 >> [ 17.688] (II) Using input driver 'evdev' for 'axp20-supplyer' >> [ 17.688] (**) axp20-supplyer: always reports core events >> [ 17.688] (**) evdev: axp20-supplyer: Device: "/dev/input/event0" >> [ 17.689] (--) evdev: axp20-supplyer: Vendor 0x1 Product 0x1 >> [ 17.689] (--) evdev: axp20-supplyer: Found keys >> [ 17.689] (II) evdev: axp20-supplyer: Configuring as keyboard >> [ 17.689] (**) Option "config_info" >> "udev:/sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input0/event0" >> [ 17.689] (II) XINPUT: Adding extended input device "axp20-supplyer" >> (type: KEYBOARD, id 6) >> [ 17.689] (**) Option "xkb_rules" "evdev" >> [ 17.689] (**) Option "xkb_model" "pc105" >> [ 17.689] (**) Option "xkb_layout" "us" >> [ 17.692] (II) config/udev: Adding input device zet6221_ts >> (/dev/input/event2) >> [ 17.692] (**) zet6221_ts: Applying InputClass "evdev touchscreen >> catchall" >> [ 17.692] (II) Using input driver 'evdev' for 'zet6221_ts' >> [ 17.692] (**) zet6221_ts: always reports core events >> [ 17.693] (**) evdev: zet6221_ts: Device: "/dev/input/event2" >> [ 17.693] (--) evdev: zet6221_ts: Vendor 0 Product 0 >> [ 17.693] (--) evdev: zet6221_ts: Found absolute axes >> [ 17.693] (--) evdev: zet6221_ts: Found absolute multitouch axes >> [ 17.693] (--) evdev: zet6221_ts: Found x and y absolute axes >> [ 17.693] (--) evdev: zet6221_ts: Found absolute touchscreen >> [ 17.693] (II) evdev: zet6221_ts: Configuring as touchscreen >> [ 17.693] (**) evdev: zet6221_ts: YAxisMapping: buttons 4 and 5 >> [ 17.693] (**) evdev: zet6221_ts: EmulateWheelButton: 4, >> EmulateWheelInertia: 10, EmulateWheelTimeout: 200 >> [ 17.693] (**) Option "config_info" >> "udev:/sys/devices/platform/sunxi-i2c.1/i2c-1/1-0076/input/input2/event2" >> [ 17.693] (II) XINPUT: Adding extended input device "zet6221_ts" >> (type: TOUCHSCREEN, id 7) >> [ 17.694] (II) evdev: zet6221_ts: initialized for absolute axes. >> [ 17.695] (**) zet6221_ts: (accel) keeping acceleration scheme 1 >> [ 17.695] (**) zet6221_ts: (accel) acceleration profile 0 >> [ 17.695] (**) zet6221_ts: (accel) acceleration factor: 2.000 >> [ 17.695] (**) zet6221_ts: (accel) acceleration threshold: 4 >> [ 17.696] (II) config/udev: Adding input device zet6221_ts >> (/dev/input/mouse0) >> [ 17.696] (II) No input driver specified, ignoring this device. >> [ 17.696] (II) This device may have been added with another device >> file. >> [ 17.698] (II) config/udev: Adding input device ecompass_data >> (/dev/input/event1) >> [ 17.698] (II) No input driver specified, ignoring this device. >> [ 17.698] (II) This device may have been added with another device >> file. >> >> modinfo zet6221 >> >> filename: /lib/modules/3.4.61/all/zet6221.ko >> license: GPL >> description: Zet6221 Touchscreen driver >> author: <wingrime >> srcversion: AA04CFE9C9A87A0AFEC2BD2 >> alias: i2c:zet6221_ts >> depends: >> intree: Y >> vermagic: 3.4.61 preempt mod_unload modversions ARMv7 p2v8 >> >> sudo evtest /dev/input/event2 >> >> Input driver version is 1.0.1 >> Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0 >> Input device name: "zet6221_ts" >> >> evtest dont report any events, >> Any pointers,ideas,help would be much appreciated >> >> Thanks in advance Mikey >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "linux-sunxi" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/linux-sunxi/_y0NOJL-4YU/unsubscribe. >> To unsubscribe from this group and all of its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > You received this message because you are subscribed to the Google Groups > "linux-sunxi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
