Enabling Mistral touch screen driver

Enabling Mistral touch screen driver

[Vishal Borker]

Hi all,
  Have been working on getting Microwindows working on the TI OMAP 5912 
OSK + MISTRAL QVGA LCD.
 I have reached to the point where i am able to get microwindows working 
and display onto the framebuffer. Was interested in finding asto what i 
would need to do to enable the touchscreen component & support. both, on 
the kernel as well as microwindows side. Also what is the RGB format 
that is supported on the kernel framebuffer side. any help/config files 
for microwindows on OMAP are welcome.
Thanks in advance!
warmregards,
Vishal

Re: Enabling Mistral touch screen driver

[Dirk Behme]

Vishal Borker wrote:
> Was interested in finding asto what i 
> would need to do to enable the touchscreen component & support. both, on 
> the kernel ...

Seach list archive for 'tslib' and 'touchscreen'.

Use userspace tslib for touchscreen handling:

http://cvs.arm.linux.org.uk/

-> tslib

Kernel configuration for this:

CONFIG_OMAP_OSK_MISTRAL=y
CONFIG_OMAP_UWIRE=y
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_OMAP=y

 > ... as well as microwindows side.

Search list archive for 'microwindows' as well.

Regards

Dirk

Re: Enabling Mistral touch screen driver

[David Brownell]

On Sunday 14 May 2006 8:45 am, Dirk Behme wrote:
> 
> Kernel configuration for this:
> 
> CONFIG_OMAP_OSK_MISTRAL=y
> CONFIG_OMAP_UWIRE=y
> CONFIG_INPUT_TOUCHSCREEN=y
> CONFIG_TOUCHSCREEN_OMAP=y

Erm, we're trying to move away from legacy platform-specific code,
towards code that's merged/mergeable upstream.

So instead, use: 

CONFIG_OMAP_OSK_MISTRAL=y
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=y
CONFIG_SPI_OMAP_UWIRE=y

That assumes a recent GIT tree, which includes the board-specific init
needed to make that work.

- Dave

Re: Enabling Mistral touch screen driver

[Dirk Behme]

David Brownell wrote:
> Erm, we're trying to move away from legacy platform-specific code,
> towards code that's merged/mergeable upstream.
> 
> So instead, use: 
> 
> CONFIG_OMAP_OSK_MISTRAL=y
> CONFIG_INPUT_TOUCHSCREEN=y
> CONFIG_TOUCHSCREEN_ADS7846=y
> CONFIG_SPI_OMAP_UWIRE=y
> 
> That assumes a recent GIT tree, which includes the board-specific init
> needed to make that work.

Any plans to remove CONFIG_OMAP_UWIRE or 
CONFIG_TOUCHSCREEN_OMAP so that guys like me using their 
configuration for ages are forced to rethink about it?

Dirk

Re: Enabling Mistral touch screen driver

[David Brownell]

On Monday 15 May 2006 10:38 am, Dirk Behme wrote:
> > 
> > CONFIG_OMAP_OSK_MISTRAL=y
> > CONFIG_INPUT_TOUCHSCREEN=y
> > CONFIG_TOUCHSCREEN_ADS7846=y
> > CONFIG_SPI_OMAP_UWIRE=y
> > 
> > That assumes a recent GIT tree, which includes the board-specific init
> > needed to make that work.
> 
> Any plans to remove CONFIG_OMAP_UWIRE or 
> CONFIG_TOUCHSCREEN_OMAP so that guys like me using their 
> configuration for ages are forced to rethink about it?

Yes.  Given patches merged today, and one I'll post soonish, it's almost
time to get rid of

	drivers/input/touchscreen/omap/
		ads7846.h
		ts_inn1510.c
		ts_osk.c

Until there's a tsc2101.c SPI-framework driver, the ts_hx.c support
(and omap-alsa-tsc2101) will need to stick around though.  

And there will be similar issues for the CONFIG_OMAP_UWIRE too;
likely more than just tsc2101 support needs that for the moment.

- Dave

Re: Enabling Mistral touch screen driver

[Dirk Behme]

David Brownell wrote:
> Erm, we're trying to move away from legacy platform-specific code,
> towards code that's merged/mergeable upstream.
> 
> So instead, use: 
> 
> CONFIG_OMAP_OSK_MISTRAL=y
> CONFIG_INPUT_TOUCHSCREEN=y
> CONFIG_TOUCHSCREEN_ADS7846=y
> CONFIG_SPI_OMAP_UWIRE=y

Just fyi and the archive: Using configuration like above

CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=m
CONFIG_OMAP_OSK_MISTRAL=y
CONFIG_SPI_BITBANG=m
CONFIG_SPI_OMAP_UWIRE=m

# CONFIG_OMAP_UWIRE is not set
# CONFIG_OMAP_TSC2101 is not set

on recent git works with OMAP5912 OSK. If you use modules, 
don't forget to add 'modprobe omap_uwire' to your 
configuration. This loads spi_bitbang as well. If you don't, 
ads7846 is loaded without any message (ads7846_probe isn't 
called?) and nothing works.

But seems that there is again an irq issue. Seperate mail 
follows.

Best regards

Dirk

Re: Enabling Mistral touch screen driver

[David Brownell]

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

On Friday 26 May 2006 11:32 pm, Dirk Behme wrote:

> don't forget to add 'modprobe omap_uwire' to your 
> configuration.

Hmm, I forgot about that stuff.  I've been having coldplug load
all the relevant platform drivers for me ... see the attached
script.  Sometime in 2.6.18 the special-casing for platform
devices can disappear, they'll support modalias correctly.

- Dave
 

[-- Attachment #2: S00coldplug --]
[-- Type: text/plain, Size: 978 bytes --]

#!/bin/ash
#
# "coldplug" ensures every hardware device present has its driver loaded,
# even if its hotplug event was ignored since it was too early in system
# startup for hotplug processing to work.
#
# Those drivers will create /sys/class or /sys/block nodes that receive
# normal udev processing through hotplug, leading to /dev node creation.
#
# Run this during system startup shortly after /dev has been initialized
# using udevstart.

if [ ! -d /sys/devices ]
then
	exit 1
fi

# "new style" kernel hotplug has module-init-tools do the thinking
cd /sys/devices
for DIR in $(find . -type d)
do
	if [ -f $DIR/modalias -a ! -L $DIR/driver ]
	then
		modprobe -q $(cat $DIR/modalias)
	fi
done

# REVISIT this part goes away sometime in 2.6.18 when platform_device
# gets full hotplug/modalias support
cd /sys/devices/platform
for DEV in *
do
	if [ "$DEV" != "power" -a ! -L $DEV/driver ]
	then
		# some platform drivers will need a MODULE_ALIAS()
		modprobe -q $DEV
	fi
done

[-- Attachment #3: Type: text/plain, Size: 0 bytes --]