Thanx for your fast response.
I looked up the msm_defconfig and found that indeed both drivers are
active.
# CONFIG_INPUT_KEYBOARD is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_FUJITSU is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
CONFIG_TOUCHSCREEN_ELAN_I2C_8232=y <======
HERE
# CONFIG_TOUCHSCREEN_ELO is not set
# CONFIG_TOUCHSCREEN_MTOUCH is not set
# CONFIG_TOUCHSCREEN_INEXIO is not set
# CONFIG_TOUCHSCREEN_MK712 is not set
# CONFIG_TOUCHSCREEN_PENMOUNT is not set
CONFIG_TOUCHSCREEN_SYNAPTICS_I2C_RMI=y <======= and
HERE
# CONFIG_TOUCHSCREEN_TOUCHRIGHT is not set
after some googeling I found a statement that HTC used for the Dream
phone the ELAN touchscreen
as a second source. So they have both Synaptics AND Elan hardware in
use.
Probably this now is their way to only have one software version for
different hardware.
One of the drivers will fail but the other will configure correctly.
Again thank you for your fast response.
Br,
Michael
On 8 Jan., 19:32, Greg KH <gre...@gmail.com> wrote:
> On Fri, Jan 8, 2010 at 9:07 AM, mibo <mich...@bumbleb.de> wrote:
> > And now the question: When I look at the board configuration file /
> > android/msm/arch/arm/mach-msm/board-sapphire.c (I think this is for
> > the HTC Dream phone) I can see there are two touchscreen drivers
> > active:
>
> > static struct i2c_board_info i2c_devices[] = {
> > {
> > I2C_BOARD_INFO(SYNAPTICS_I2C_RMI_NAME, 0x20),
> > .platform_data = sapphire_ts_data,
> > .irq = SAPPHIRE_GPIO_TO_INT(SAPPHIRE_GPIO_TP_ATT_N)
> > },
> > {
> > I2C_BOARD_INFO(ELAN_8232_I2C_NAME, 0x10),
> > .platform_data = &elan_i2c_data,
> > .irq = SAPPHIRE_GPIO_TO_INT(SAPPHIRE_GPIO_TP_ATT_N),
> > },
> > ....
> > .....
> > }
>
> > Why are there two active drivers? Does the HTC Dream have different
> > hardware versions and either the I2C access to address 0x20 or to 0x10
> > fails and the other one then is used?
> > Or are there really two controllers?
>
> No, all this shows is that the driver supports hardware with _either_
> of these configurations.
>
> And yes, it probably would work if you had devices with both types
> of configurations on the same system, but then you would have two
> different instances of the device in the system. But odds are, that
> is not in a phone :)
>
> Hope this helps,
>
> greg k-h
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
