Boundary Device's wvga parallel screen touch

Boundary Device's wvga parallel screen touch

[Sandoval Zazueta Francisco-B20593]

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

Hello!



I found a thread looking around on touch screen working with community yocto:

http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/62



I'm trying to get touch to work with the same display on master. Did you figure out the issue? I compiled the kernel with p1003 and irq_set_irq_type. It compiles but touch still doesn't work.



evtest gives the following output:

root@imx6qsabreauto:~# evtest /dev/input/event0

Input driver version is 1.0.1

Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100

Input device name: "gpio-keys"

Supported events:

  Event type 0 (Sync)

  Event type 1 (Key)

    Event code 102 (Home)

    Event code 114 (VolumeDown)

    Event code 115 (VolumeUp)

    Event code 139 (Menu)

    Event code 158 (Back)

Testing ... (interrupt to exit)



With no response with random touches.



Any hints will be appreciated!





Regards,



Paco S.


[-- Attachment #2: Type: text/html, Size: 4333 bytes --]

Re: Boundary Device's wvga parallel screen touch

[Daiane Angolini]

On 08/28/2013 04:03 PM, Sandoval Zazueta Francisco-B20593 wrote:
> Hello!
>
> I found a thread looking around on touch screen working with community
> yocto:
>
> http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/62
>
> I'm trying to get touch to work with the same display on master. Did you
> figure out the issue? I compiled the kernel with p1003 and
> irq_set_irq_type. It compiles but touch still doesn't work.
>

Are you trying it for X11 or framebuffer only?


> evtest gives the following output:
>
> root@imx6qsabreauto:~# evtest /dev/input/event0
>
> Input driver version is 1.0.1
>
> Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
>
> Input device name: "gpio-keys"

gpio-keys?


>
> Supported events:
>
>    Event type 0 (Sync)
>
>    Event type 1 (Key)
>
>      Event code 102 (Home)
>
>      Event code 114 (VolumeDown)
>
>      Event code 115 (VolumeUp)
>
>      Event code 139 (Menu)
>
>      Event code 158 (Back)
>
> Testing ... (interrupt to exit)


Do you have another /dev/input/eventX to handle the touchscreen?


>
> With no response with random touches.
>
> Any hints will be appreciated!
>
> Regards,
>
> Paco S.
>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>


-- 
Daiane

Re: Boundary Device's wvga parallel screen touch

[Sandoval Zazueta Francisco-B20593]

I'm trying X11.
There are no more eventX under /dev/input.

I get the following in dmesg:
egalax_ts 1-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 1-0004 failed with error -5

but I think that's expected, as this display uses a different touch controller.

Thank you for your help!!

-----Original Message-----
From: Angolini Daiane-B19406 
Sent: Wednesday, August 28, 2013 3:04 PM
To: Sandoval Zazueta Francisco-B20593
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] Boundary Device's wvga parallel screen touch

On 08/28/2013 04:03 PM, Sandoval Zazueta Francisco-B20593 wrote:
> Hello!
>
> I found a thread looking around on touch screen working with community
> yocto:
>
> http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/62
>
> I'm trying to get touch to work with the same display on master. Did 
> you figure out the issue? I compiled the kernel with p1003 and 
> irq_set_irq_type. It compiles but touch still doesn't work.
>

Are you trying it for X11 or framebuffer only?


> evtest gives the following output:
>
> root@imx6qsabreauto:~# evtest /dev/input/event0
>
> Input driver version is 1.0.1
>
> Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
>
> Input device name: "gpio-keys"

gpio-keys?


>
> Supported events:
>
>    Event type 0 (Sync)
>
>    Event type 1 (Key)
>
>      Event code 102 (Home)
>
>      Event code 114 (VolumeDown)
>
>      Event code 115 (VolumeUp)
>
>      Event code 139 (Menu)
>
>      Event code 158 (Back)
>
> Testing ... (interrupt to exit)


Do you have another /dev/input/eventX to handle the touchscreen?


>
> With no response with random touches.
>
> Any hints will be appreciated!
>
> Regards,
>
> Paco S.
>
>
>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>


--
Daiane

Re: Boundary Device's wvga parallel screen touch

[Fabio Estevam]

On Wed, Aug 28, 2013 at 4:12 PM, Sandoval Zazueta Francisco-B20593
<B20593@freescale.com> wrote:
> I'm trying X11.
> There are no more eventX under /dev/input.
>
> I get the following in dmesg:
> egalax_ts 1-0004: egalax_ts: failed to read firmware version
> egalax_ts: probe of 1-0004 failed with error -5
>
> but I think that's expected, as this display uses a different touch controller.

Which touchscreen controller does it use?

Have you registered it in the board file and enabled the touchscreen
in the defconfig?

Re: Boundary Device's wvga parallel screen touch

[Fabio Estevam]

On Wed, Aug 28, 2013 at 4:03 PM, Sandoval Zazueta Francisco-B20593
<B20593@freescale.com> wrote:
> Hello!
>
>
>
> I found a thread looking around on touch screen working with community
> yocto:
>
> http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/62
>
>
>
> I'm trying to get touch to work with the same display on master. Did you
> figure out the issue? I compiled the kernel with p1003 and irq_set_irq_type.
> It compiles but touch still doesn't work.
>
>
>
> evtest gives the following output:
>
> root@imx6qsabreauto:~# evtest /dev/input/event0
>
> Input driver version is 1.0.1
>
> Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
>
> Input device name: "gpio-keys"

event0 is monitors 'gpio-keys', ot the touchscreen.

Have you tried other eventX? Do you see the touchscreen driver to
probe in dmesg?

Re: Boundary Device's wvga parallel screen touch

[Eric Nelson]

On 08/28/2013 12:08 PM, Fabio Estevam wrote:
> On Wed, Aug 28, 2013 at 4:03 PM, Sandoval Zazueta Francisco-B20593
> <B20593@freescale.com> wrote:
>> Hello!
>>
>> I found a thread looking around on touch screen working with community
>> yocto:
>>
>> http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/62
>>
>> I'm trying to get touch to work with the same display on master. Did you
>> figure out the issue? I compiled the kernel with p1003 and irq_set_irq_type.
>> It compiles but touch still doesn't work.
>>

I have no idea what a p1003 is. It's not used on our WVGA display.

>> evtest gives the following output:
>>
>> root@imx6qsabreauto:~# evtest /dev/input/event0
>> Input driver version is 1.0.1
>> Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
>> Input device name: "gpio-keys"
> event0 is monitors 'gpio-keys', ot the touchscreen.

gpio-keys isn't a touch-screen. It's a driver for a GPIO button board
and delivers keys POWER/HOME/BACK/VOL+-. It's mostly useful for Android
on small displays.
	http://boundarydevices.com/products/nit6x_android/

>
> Have you tried other eventX? Do you see the touchscreen driver to
> probe in dmesg?

Our kernel configurations have included support for this touch
screen (TSC2004) since "the beginning" of i.MX6 support:

	CONFIG_TOUCHSCREEN_TSC2004=y

Can you double-check your kernel config?
	zcat /proc/config.gz | grep TSC2004

You can also check for connectivity to the I2C device under
U-Boot:
	U-Boot > i2c dev 2
	Setting bus to 2
	U-Boot > i2c probe
	Valid chip addresses: 48

As shown, the TSC2004 is on I2C bus 2 (I2C3 for the hardware folks),
and is at address 0x48.

Regards,


Eric

Re: Boundary Device's wvga parallel screen touch

[Eric Nelson]

Hi Paco,

On 08/28/2013 12:03 PM, Sandoval Zazueta Francisco-B20593 wrote:
> Hello!
>
> I found a thread looking around on touch screen working with community
> yocto:
>
> http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/62
>
> I'm trying to get touch to work with the same display on master. Did you
> figure out the issue? I compiled the kernel with p1003 and
> irq_set_irq_type. It compiles but touch still doesn't work.
>
> evtest gives the following output:
> root@imx6qsabreauto:~# evtest /dev/input/event0

SABRE Auto?

I didn't know you that had a matching connector.

If you're not running on our kernel (and board), you're going to need
a kernel patch: to add the driver:
	https://github.com/boundarydevices/linux-imx6/commit/2b95627cceb68bb7a045215779fac3b1a9ef6e99

And some board glue like this in SABRE Auto:
	https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.0.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L636

(Oddly requires header file tsc2007.h and the tsc2007 data structur).

Regards,


Eric
	

Re: Boundary Device's wvga parallel screen touch

[Sandoval Zazueta Francisco-B20593]

Thank you Eric,

This is exactly what I was looking for. I should have specified that I'm trying to use Boundary Device's screen with a Sabre AI board.

Regards,

Thank you.

-----Original Message-----
From: Eric Nelson [mailto:eric.nelson@boundarydevices.com] 
Sent: Wednesday, August 28, 2013 3:36 PM
To: Sandoval Zazueta Francisco-B20593
Cc: meta-freescale@yoctoproject.org
Subject: Re: [meta-freescale] Boundary Device's wvga parallel screen touch

Hi Paco,

On 08/28/2013 12:03 PM, Sandoval Zazueta Francisco-B20593 wrote:
> Hello!
>
> I found a thread looking around on touch screen working with community
> yocto:
>
> http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/62
>
> I'm trying to get touch to work with the same display on master. Did 
> you figure out the issue? I compiled the kernel with p1003 and 
> irq_set_irq_type. It compiles but touch still doesn't work.
>
> evtest gives the following output:
> root@imx6qsabreauto:~# evtest /dev/input/event0

SABRE Auto?

I didn't know you that had a matching connector.

If you're not running on our kernel (and board), you're going to need a kernel patch: to add the driver:
	https://github.com/boundarydevices/linux-imx6/commit/2b95627cceb68bb7a045215779fac3b1a9ef6e99

And some board glue like this in SABRE Auto:
	https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.0.35_4.0.0/arch/arm/mach-mx6/board-mx6_nitrogen6x.c#L636

(Oddly requires header file tsc2007.h and the tsc2007 data structur).

Regards,


Eric
	

Re: Boundary Device's wvga parallel screen touch

[Eric Nelson]

On 08/29/2013 11:16 AM, Sandoval Zazueta Francisco-B20593 wrote:
> Thank you Eric,
>
> This is exactly what I was looking for. I should have specified
 > that I'm trying to use Boundary Device's screen with a Sabre AI board.
>

NP.