- 01 Oct, 2013 40 commits
-
-
Juergen Beisert authored
Distinguish i.MX23 and i.MX28 at runtime and do the same for both SoC at least for the 4 wire touchscreen. Signed-off-by:
Juergen Beisert <jbe@pengutronix.de> Tested-by:
Marek Vasut <marex@denx.de> Acked-by:
Lothar Waßmann <LW@KARO-electronics.de> Signed-off-by:
Jonathan Cameron <jic23@kernel.org> CC: linux-arm-kernel@lists.infradead.org CC: linux-input@vger.kernel.org CC: devel@driverdev.osuosl.org CC: Marek Vasut <marex@denx.de> CC: Fabio Estevam <fabio.estevam@freescale.com>
-
Juergen Beisert authored
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 authored
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 authored
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 authored
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:
-
Peter Meerwald authored
Signed-off-by:
Peter Meerwald <pmeerw@pmeerw.net> Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
and use it to simplify code Signed-off-by:
-
Lars-Peter Clausen authored
The documentation says that the result of raw * scale should be in microvolts, but in reallity all drivers actually report the scale so that the result is in millivolts. So update the documentation to match reallity. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Also fix a off by one error in the comment describing the transfer function. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Lars-Peter Clausen authored
Move the complexity of calculating the fixed point scale to the core. Signed-off-by:
-
Srinivas Pandruvada authored
Call hid_sensor_hub_device_open when user space opens device and call hid_sensor_hub_device_close when device is closed. This helps in saving power. Signed-off-by:
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by:
-
Srinivas Pandruvada authored
Don't call hid_open_device till there is actually an user. This saves power by not opening underlying transport for HID. Also close device if there are no active mfd client using HID sensor hub. Signed-off-by:
Jiri Kosina <jkosina@suse.cz> Signed-off-by:
-
Greg Kroah-Hartman authored
Turns out that LL_MRF_RETURN is "void" so loop_make_request() would fall through to the error path for a successful call. Either this never matters, or the error path really doesn't do anything. Fix it up to do what the code is written to look like it is doing, if that really is what it should be doing is another story... Cc: Peng Tao <tao.peng@emc.com> Cc: Zhao Hongjiang <zhaohongjiang@huawei.com> Cc: Andreas Dilger <andreas.dilger@intel.com> Signed-off-by:Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Greg Kroah-Hartman authored
It's just 'void' and only used in one place, so just remove it, it's useless. Cc: Peng Tao <tao.peng@emc.com> Cc: Zhao Hongjiang <zhaohongjiang@huawei.com> Cc: Andreas Dilger <andreas.dilger@intel.com> Signed-off-by:
-
