- 12 Mar, 2013 8 commits
-
-
Dmitry Torokhov authored
The IMS PCU (Passenger Control Unit) device used custom protocol over serial line, so it is presenting itself as CDC ACM device. Now that we have proper in-kernel driver for it we need to black-list the device in cdc-acm driver. Acked-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Dmitry Torokhov authored
The PCU is a device installed in the armrest of a plane seat and is connected to IMS Rave Entertainment System. It has a set of control buttons (Volume Up/Down, Attendant, Lights, etc) on one side and gamepad-like controls on the other side. Originally the device was handled from userspace and because of that it presents itself on USB bus as a CDC-ACM modem device that however can not make calls. However the custom handling is not as convenient as using standard input subsystem facilities. If it was pure input device it would be possible to continue using userspace solution (moving it over to uinput), but the device also has backlighted keys which can not be supported via uinput. Signed-off-by: -
Dmitry Torokhov authored
Entertainment systems used in aircraft need additional keycodes for their Passenger Control Units, so let's add them. Signed-off-by: -
Markus Pargmann authored
dev_dbg should end with a new line. Signed-off-by:
Markus Pargmann <mpa@pengutronix.de> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
-
Markus Pargmann authored
Often a reading can be wrong. This patch assures that this is really a pen up event and not a false reading. Based on wm9712: pen up by Teresa Gámez and Christian Hemp. Signed-off-by:
-
Markus Pargmann authored
Instead of interpreting a wrong measurement as pen up, we should try to read again. Based on wm9712: pen up by Teresa Gámez and Christian Hemp. Signed-off-by:
-
Markus Pargmann authored
With fast movements, there occured some out of screen jumps with my touchscreen. The abs_x and abs_y module parameters should fix this by default, but the driver doesn't actively checks the x/y coordinates. Instead it seems that the input layer was supposed to drop out of range inputs, as described in the comments: "These parameters are used to help the input layer discard out of range readings and reduce jitter etc" The input layer documentation describes that values that are not in the absolute range are also accepted. So this patch adds a check within the driver. Signed-off-by:
-
Daniel Hellstrom authored
APBPS2 is a PS/2 core part of GRLIB found in SPARC32/LEON products. Signed-off-by:
Daniel Hellstrom <daniel@gaisler.com> Signed-off-by:
-
- 26 Feb, 2013 2 commits
-
-
Dmitry Torokhov authored
This simplifies error unwinding and device teardown. Tested-by:
Heiko Stuebner <heiko@sntech.de> Signed-off-by:
-
Dmitry Torokhov authored
Sometimes drivers need to execute one-off actions in their error handling or device teardown paths. An example would be toggling a GPIO line to reset the controlled device into predefined state. To allow performing such actions when using managed resources let's allow adding them to stack/group of devres resources. Acked-by:
Tejun Heo <tj@kernel.org> Acked-by:
-
- 25 Feb, 2013 4 commits
-
-
Heiko Stübner authored
Add the necessary code to create the needed platformdata from devicetree informations. The interrupt mode of the chip is not set via devicetree, as it is not a property of the hardware but instead only a preferred type of operation. This should probably be made settable via configfs in the future. The option set as default is the mode the datasheet mentions as default. Signed-off-by:
-
Heiko Stübner authored
When supporting devicetree the platformdata may not necessarily come from the dev but may be generated in the driver instead. Therefore keep the pointer in the driver struct instead of using dev.platform_data. Signed-off-by:
-
Heiko Stübner authored
Devicetree based platforms don't handle device callbacks very well and until now no board has come along that needs more extended hwinit than pulling the rst gpio high. Therefore pull the reset handling directly into the driver and remove the callbacks from the driver. If extended device setup is needed at some later point, power-sequences would probably be the solution of choice. Signed-off-by:
-
Heiko Stübner authored
Previously the gpio was not configured at all. Signed-off-by:
-
- 17 Feb, 2013 2 commits
-
-
Dmitry Torokhov authored
Signed-off-by: -
Pali Rohár authored
This enables autoloading of tsc2005 driver when is compiled as a module. Signed-off-by:
Pali Rohár <pali.rohar@gmail.com> Signed-off-by:
-
- 16 Feb, 2013 5 commits
-
-
Stephen Warren authored
Tegra only supports, and always enables, device tree. Remove all ifdefs and runtime checks for DT support from the driver. Platform data is therefore no longer required. Delete the header that defines it, and rework the driver to parse the device tree directly into struct tegra_kbc. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Signed-off-by:
-
Henrik Rydberg authored
To properly setup event parameters for emulated events, pass the appropriate flag to the slot initialization function. Also, all MT-related events should be setup before initialization. Incidentally, this solves the issue of doubly filtered pointer events. Reported-by:
Daniel Kurtz <djkurtz@chromium.org> Signed-off-by:
Henrik Rydberg <rydberg@euromail.se> Signed-off-by:
-
Henrik Rydberg authored
The pointer emulation events are derived from contact values that have already been filtered, so send the emulated events as is. Reported-by:
-
Michael Trimarchi authored
Make the constants referring to range and bandwidth public so they can be used when initializing the platform data fields in the platform code. Fix also some comments regarding the unit of measurement to use for the range and bandwidth fields, the values are not actually expected to be in G or HZ, the code in bma150.c just uses the BMA150_RANGE_xxx and BMA150_BW_xxx constants like they are with no translation from actual values in G or HZ. Signed-off-by:
Michael Trimarchi <michael@amarulasolutions.com> Signed-off-by:
Antonio Ospite <ao2@amarulasolutions.com> Signed-off-by:
-
Michael Trimarchi authored
When PM_RUNTIME is not defined, pm_runtime_get_sync() returns 1, see include/linux/pm_runtime.c::__pm_runtime_resume(), and the check of the return value was overlooking this, in this case bma150_open() would return 1 which is not expected by upper layers. Maybe the check for != -ENOSYS (Function not implemented) was meant to cover this, but pm_runtime_get_sync() does not return this value. For now fix the issue locally by checking explicitly for negative return values. Signed-off-by:
-
- 14 Feb, 2013 17 commits
-
-
Kevin Cernekee authored
Separate out the common trackstick probe/setup sequences, then call them from each of the v3 init functions. Credits: Emmanual Thome furnished the information on the trackstick init and how it affected the report format. Signed-off-by:
Kevin Cernekee <cernekee@gmail.com> Tested-by:
Dave Turvene <dturvene@dahetral.com> Signed-off-by:
-
Kevin Cernekee authored
Rushmore touchpads are found on Dell E6230/E6430/E6530. They use the V3 protocol with slightly tweaked init sequences and report formats. The E7 report is 73 03 0a, and the EC report is 88 08 1d Credits: Emmanuel Thome reported the MT bitmap changes. Signed-off-by:
-
Kevin Cernekee authored
A number of different ALPS touchpad protocols can reuse alps_process_touchpad_packet_v3() with small tweaks to the bitfield decoding. Create a new priv->decode_fields() callback that handles the per-model differences. Signed-off-by:
-
Kevin Cernekee authored
Newer touchpads use different constants, so make them runtime- configurable. Signed-off-by:
-
Kevin Cernekee authored
Pinnacle class devices should return "88 07 xx" or "88 08 xx" when entering command mode. If either the first byte or the second byte is invalid, return an error. Signed-off-by:
-
Kevin Cernekee authored
The official ALPS driver uses the EC report, not the E7 report, to detect these devices. Also, they check for a range of values; the original table-based code only checked for two specific ones. Signed-off-by:
-
Kevin Cernekee authored
This allows alps_identify() to override these settings based on the device characteristics, if it is ever necessary. Signed-off-by:
-
Kevin Cernekee authored
In anticipation of adding more ALPS protocols and more per-device quirks, use function pointers instead of switch statements to call functions that differ from one device to the next. Signed-off-by:
-
Kevin Cernekee authored
If the E6 report test passes, get the E7 and EC reports right away and then try to match an entry in the table. Pass in the alps_data struct, so that the detection code will be able to set operating parameters based on information found during detection. Change the version (psmouse->model) to report the protocol version only, in preparation for supporting models that do not show up in the ID table. Signed-off-by:
-
Kevin Cernekee authored
Several ALPS driver init sequences repeat a command three times, then issue PSMOUSE_CMD_GETINFO to read the result. Move this into a helper function to simplify the code. Signed-off-by:
-
Kevin Cernekee authored
This will minimize the number of forward declarations needed when alps_get_model() starts assigning function pointers. Signed-off-by:
-
Kevin Cernekee authored
Not every type of ALPS touchpad is well-suited to table-based detection. Start moving the various alps_model_data attributes into the alps_data struct so that we don't need a unique table entry for every possible permutation of protocol version, flags, byte0/mask0, etc. Signed-off-by:
-
Kevin Cernekee authored
Add kernel-doc markup. Signed-off-by:
-
Ping Cheng authored
It is a pen with 10 finger touch device. Signed-off-by:
Ping Cheng <pingc@wacom.com> Signed-off-by:
-
Benson Leung authored
This patch adds support for the Cypress APA Smbus Trackpad type, which uses a modified register map that fits within the limitations of the smbus protocol. Devices that use this protocol include: CYTRA-116001-00 - Samsung Series 5 550 Chromebook trackpad CYTRA-103002-00 - Acer C7 Chromebook trackpad CYTRA-101003-00 - HP Pavilion 14 Chromebook trackpad Signed-off-by:
Dudley Du <dudl@cypress.com> Signed-off-by:
Benson Leung <bleung@chromium.org> Reviewed-by:
-
Daniel Kurtz authored
Investigating the following gesture highlighted two slight implementation errors with choosing which slots to report in which slot when multiple contacts are present: Action SGM AGM (MTB slot:Contact) 1. Touch contact 0 (0:0) 2. Touch contact 1 (0:0, 1:1) 3. Lift contact 0 (1:1) 4. Touch contacts 2,3 (0:2, 1:3) In step 4, slot 1 was not being cleared first, which means the same tracking ID was being used for reporting both the old contact 1 and the new contact 3. This could result in "drumroll", where the old contact 1 would appear to suddenly jump to new finger 3 position. Similarly, if contacts 2 & 3 are not detected at the same sample, step 4 is split into two: Action SGM AGM (MTB slot:contact) 1. Touch contact 0 (0:0) 2. Touch contact 1 (0:0, 1:1) 3. Lift contact 0 (1:1) 4. Touch contact 2 (0:2, 1:1) 5. Touch contact 3 (0:2, 1:3) In this case, there was also a bug. In step 4, when contact 1 moves from SGM to AGM and contact 2 is first reported in SGM, slot 0 was actually empty. So slot 0 can be used to report the new SGM (contact 0), immediately. Since it was empty, contact 2 in slot 0 will get a new tracking ID. Signed-off-by:
-
Heiko Carstens authored
When removing the !S390 dependency from drivers/input/Kconfig a couple of drivers don't compile because they have a dependency on GENERIC_HARDIRQS. So add the missing dependencies. Fixes e.g. this one: drivers/input/keyboard/lm8323.c: In function ‘lm8323_suspend’: drivers/input/keyboard/lm8323.c:801:2: error: implicit declaration of function ‘irq_set_irq_wake’ [-Werror=implicit-function-declaration] Signed-off-by:
Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by:
-
- 25 Jan, 2013 2 commits
-
-
Peter Ujfalusi authored
It is time to switch to system wq instead creating a queue for the driver. Signed-off-by:
Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by:
-
Peter Ujfalusi authored
Convert the probe to use devm_*. At the same time reorder the calls so we will register the input device as the last step when the driver is loaded. Signed-off-by:
-
