. | Juergen Beisert |
Linux Solutions for Science and Industry | Phone: +49-5121-206917-5128 |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Fax: +49-5121-206917- |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de
Hi Dan,
On Monday 24 February 2014 14:33:16 Dan Carpenter wrote:
On Mon, Feb 24, 2014 at 02:16:24PM +0100, Juergen Beisert wrote:
While I don't have much experience with the TS part of the code but I
can investigate if you don't have any idea.
can you please test the following patch
-by: Juergen Beisert j...@pengutronix.de
diff --git a/drivers/staging/iio/adc/mxs-lradc.c
b/drivers/staging/iio/adc/mxs-lradc.c
index 7fc66a6..514844e 100644
--- a/drivers/staging/iio/adc/mxs-lradc.c
+++ b/drivers/staging/iio/adc/mxs-lradc.c
@@ -757,6 +757,7 @@ static void mxs_lradc_finish_touch_event
In order to support i.MX23 and i.MX28 within one driver we need to separate the
register definitions which differ in both SoC variants.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux-in...@vger.kernel.org
CC: de...@driverdev.osuosl.org
CC
The LRADC units in i.MX23 and i.MX28 differ and we need to distinguish both
SoC variants in order to make the touchscreen work on i.MX23
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux-in...@vger.kernel.org
CC: de...@driverdev.osuosl.org
CC
Some things have still to be done to the LRADC driver.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux-in...@vger.kernel.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC
The following series replaces the current busy loop touchscreen implementation
for i.MX28/i.MX23 SoCs by a fully interrupt driven implementation.
Since i.MX23 and i.MX28 silicon differs, the existing implementation can
be used for the i.MX28 SoC only.
The first patch adds proper clock handling.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux-in...@vger.kernel.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc
-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux-in...@vger.kernel.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
CC: Dmitry Torokhov dmitry.torok
Distinguish i.MX23 and i.MX28 at runtime and do the same for both SoC at least
for the 4 wire touchscreen.
Note: support for the remaining LRADC channels is not tested on an
i.MX23 yet.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux
This is an RFC for the new touchscreen properties.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux-in...@vger.kernel.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan
The delay units inside the LRADC depend on the presence of a 2 kHz clock.
This change enables the clock to be able to use the delay unit for the
touchscreen part of the driver.
Signed-off-by: Juergen Beisert j...@pengutronix.de
---
arch/arm/boot/dts/imx23.dtsi| 1 +
arch/arm/boot/dts
Replace the individual register access by a few shared access function to make
the
code easier to read and in order to add the i.MX23 SoC in the next step.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: linux-in...@vger.kernel.org
CC: de
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc/mxs-lradc.c | 163
In order to support i.MX23 and i.MX28 within one driver we need to separate the
register definitions which differ in both SoC variants.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC
-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc/mxs-lradc.c | 532
Replace the individual register access by a few shared access function to make
the
code easier to read and in order to add the i.MX23 SoC in the next step.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut
This is an RFC for the new touchscreen properties.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
CC
The following series replaces the current busy loop touchscreen implementation
for i.MX28/i.MX23 SoCs by a fully interrupt driven implementation.
Since i.MX23 and i.MX28 silicon differs, the existing implementation can
be used for the i.MX28 SoC only.
So, the first two patches of this series
The LRADC units in i.MX23 and i.MX28 differ and we need to distinguish both
SoC variants in order to make the touchscreen work on i.MX23
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC
Distinguish i.MX23 and i.MX28 at runtime and do the same for both SoC at least
for the 4 wire touchscreen.
Note: support for the remaining LRADC channels is not tested on an
i.MX23 yet.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de
The following series replaces the current busy loop touchscreen implementation
for i.MX28/i.MX23 SoCs by a fully interrupt driven implementation.
Since i.MX23 and i.Mx28 silicon differs, the existing implementation can
be used for the i.MX28 SoC only.
So, the first two patches of this series
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc/mxs-lradc.c | 165
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc/mxs-lradc.c | 165
In order to support i.MX23 and i.MX28 within one driver we need to separate the
register definitions which differ in both SoC variants.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC
The following series replaces the current busy loop touchscreen implementation
for i.MX28/i.MX23 SoCs by a fully interrupt driven implementation.
Since i.MX23 and i.Mx28 silicon differs, the existing implementation can
be used for the i.MX28 SoC only.
So, the first two patches of this series
The LRADC units in i.MX23 and i.MX28 differ and we need to distinguish both
SoC variants in order to make the touchscreen work on i.MX23
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC
-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc/mxs-lradc.c | 531
The LRADC units in i.MX23 and i.MX28 differ and we need to distinguish both
SoC variants in order to make the touchscreen work on i.MX23
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC
In order to support i.MX23 and i.MX28 within one driver we need to separate the
register definitions which differ in both SoC variants.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC
-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc/mxs-lradc.c | 548
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC: Fabio Estevam fabio.este...@freescale.com
CC: Jonathan Cameron ji...@cam.ac.uk
---
drivers/staging/iio/adc/mxs-lradc.c | 165
In order to support i.MX23 and i.MX28 within one driver we need to separate the
register definitions which differ in both SoC variants.
Signed-off-by: Juergen Beisert j...@pengutronix.de
CC: linux-arm-ker...@lists.infradead.org
CC: de...@driverdev.osuosl.org
CC: Marek Vasut ma...@denx.de
CC
33 matches
Mail list logo
