Hello,Jigar,
I checked your BSP file and touchscreen driver. Your porting method is correct. Because I don't have device to test it, I can only give you some advice or remind you.
(1)Conifirmming if I2C address is correct
In our linux BSP, I2C device is using 7-bit address, So check it comparing datasheet of touchscreen.
(2)Compiling atmel_mxt_ts driver into linux kernel
Let us adjust compiling method, compile ts driver into linux kernel directly.
(3)Confirmming if issue was from I2C controller
In order to confirm if the issue was generated by I2C controller, we can use GPIO to simulate these 2 lines of I2C3(from yourto BSP, i2c3 is being used). The following is an example for you, you can refter to this usage.
--------a) Adding some code in BSP file.
...
#include <linux/i2c-gpio.h>
...
#define GPIO_I2C4_SDA IMX_GPIO_NR(3, 18) /*EIM_D18 pin*/
#define GPIO_I2C4_SCL IMX_GPIO_NR(1, 3) /*GPIO_3 pin*/
...
/* GPIO I2C data -- I2C4 */
struct i2c_gpio_platform_data mx6q_gpio_i2c4_data = {
.sda_pin = GPIO_I2C4_SDA,
.scl_pin = GPIO_I2C4_SCL,
.sda_is_open_drain = 0,
.scl_is_open_drain = 0,
};
/* GPIO I2C platform device -- I2C4*/
static struct platform_device gpio_i2c_device[] = {
{
.name = "i2c-gpio",
.id = 3,
.dev = {
.platform_data = &mx6q_gpio_i2c4_data,
},
},
};
...
static struct i2c_board_info gpio_i2c3_board_info[] __initdata = {
{
I2C_BOARD_INFO("atmel_mxt_ts", 0x4c),
.platform_data = &mxt_platform_data,
.irq = gpio_to_irq(MXT_CHG_PIN),
},
};
...
platform_device_register(&gpio_i2c_device[0]); /*gpio simulate I2C - here is I2C4*/
....
i2c_register_board_info(3, gpio_i2c3_board_info,ARRAY_SIZE(gpio_i2c3_board_info)); /*gpio i2c board*/
....
--------b) Adjusting baord-mx6q_sabreauto.h file ( Multiplex these 2 pins as GPIOs)
...
static iomux_v3_cfg_t mx6q_i2c3_pads_rev_b[] __initdata = {
MX6Q_PAD_GPIO_3__GPIO_1_3,
MX6Q_PAD_EIM_D18__GPIO_3_18,
};
...
-------c) Adding gpio i2c drivers when compiling linux kernel
The driver is in path "liunx/drivers/i2c/busses/i2c-gpio.c"
At first , please test (1) & (2) steps ! If there is no improvement, you can use 3rd way to debug your i2c device.
Regards,
Weidong
