From: Michael Welling <hidden> Date: 2014-08-05 17:06:40
The TSC2004 driver has yet to appear in the mainline kernel. We have
been using the driver referenced here as provided by TI:
https://www.mail-archive.com/linux-omap@vger.kernel.org/msg22018.html
Are there any plans of supporting this device in the mainline kernel?
Mysteriously a device tree entry was found in the following file:
arch/arm/boot/dts/omap4-var-som-om44.dtsi
This is obviously pointing to an out of tree driver that is not easily
obtained.
Suggestions?
I still believe that support for TSC2004 should be added 5to tsc2007, they are
too much alike to be separate drivers.
Mysteriously a device tree entry was found in the following file:
arch/arm/boot/dts/omap4-var-som-om44.dtsi
This is obviously pointing to an out of tree driver that is not easily
obtained.
Suggestions?
I still believe that support for TSC2004 should be added 5to tsc2007, they are
too much alike to be separate drivers.
I tried to add tsc2004 support to the tsc2007 driver but I didn't
really get it to work properly because the tsc2007 interrupt handling
differs from what tsc2004 needs.
I think it would be better to add tsc2004 support to the tsc2005
driver. They only difference between those two chips is the interface
(i2c vs spi). If regmap was added to tsc2005 I think it should be easy
to support tsc2004.
quoted
Mysteriously a device tree entry was found in the following file:
arch/arm/boot/dts/omap4-var-som-om44.dtsi
This is obviously pointing to an out of tree driver that is not easily
obtained.
I have patches that add tsc2004 support to the tsc2007 driver, but I
really can't recommend them. The interrupt handling is broken so for
each touch event the chip needs to be software reset...
The driver you posted a link to above also has flaw btw.
regards
Joachim Eastwood
quoted
Suggestions?
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I still believe that support for TSC2004 should be added 5to tsc2007, they are
too much alike to be separate drivers.
I tried to add tsc2004 support to the tsc2007 driver but I didn't
really get it to work properly because the tsc2007 interrupt handling
differs from what tsc2004 needs.
OK.
I think it would be better to add tsc2004 support to the tsc2005
driver. They only difference between those two chips is the interface
(i2c vs spi). If regmap was added to tsc2005 I think it should be easy
to support tsc2004.
I still believe that support for TSC2004 should be added 5to tsc2007, they are
too much alike to be separate drivers.
I tried to add tsc2004 support to the tsc2007 driver but I didn't
really get it to work properly because the tsc2007 interrupt handling
differs from what tsc2004 needs.
OK.
quoted
I think it would be better to add tsc2004 support to the tsc2005
driver. They only difference between those two chips is the interface
(i2c vs spi). If regmap was added to tsc2005 I think it should be easy
to support tsc2004.
That would also be acceptable.
The tsc2005 still needs devicetree conversion, so it is at least 2 patches away
from where I can use it.
I have missed the window for my companies OE release so I doubt I will
have time to code
in all or any of this.
I am in the process of routing a AM335x SoM which obsoletes this AM3517 one
so my resources will be elsewhere.