- 23 Sep, 2022 8 commits
-
-
Matthias Schiffer authored
A full erase is required to recover from error conditions like "Bad Partition Table". Various individual partition erase commands can be (and need to be) omitted, as they will fail until a new partition table has been written. Signed-off-by:
Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Reviewed-by:
Lyude Paul <lyude@redhat.com> Link: https://lore.kernel.org/r/20220608124808.51402-7-matthias.schiffer@ew.tq-group.comSigned-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Matthias Schiffer authored
When recovering from a bad partition table (for example after an interrupted update), a reset is necessary for the new partition table to become effective. Without this reset, writing the core code partition will fail with status 0x03 (Invalid Command). Signed-off-by:
-
Matthias Schiffer authored
Preparation for use of the "erase application" command, which is required to recover from a bad partition table error condition. Rather than adding complex fallback error paths for such errors, it seems more robust to do the full erase unconditionally. Signed-off-by:
-
Matthias Schiffer authored
The command register is reset to 0 when a command has completed. Check for this condition instead of the error status, which will not accurately reflect completion. In particular, the incorrect condition caused every command error to be reported as a timeout. Signed-off-by:
-
Matthias Schiffer authored
Add a function that waits for the last command to complete and checks the status, and use it where appropriate. This prepares for the subsequent fix of the completion condition in rmi_f34_attention(), which would previously lead to a timeout instead of a more detailed error message whenever a command was unsuccessful with v7/v8 bootloaders. Signed-off-by:
-
Matthias Schiffer authored
Commit a6977d75 ("Input: synaptics-rmi4 - support bootloader v8 in f34v7") allowed the F34v7 driver to probe with bootloader v8, but it did not update various other bootloader version checks in the F34 code. Fixes: a6977d75 ("Input: synaptics-rmi4 - support bootloader v8 in f34v7") Signed-off-by:
-
Andy Shevchenko authored
The gpiod_count() API is defined in gpio/consumer.h. Include it. Fixes: f8f7f47d ("Input: matrix_keypad - replace of_gpio_named_count() by gpiod_count()") Signed-off-by:
Andy Shevchenko <andriy.shevchenko@linux.intel.com> Link: https://lore.kernel.org/r/20220923184632.2157-1-andriy.shevchenko@linux.intel.comSigned-off-by:
-
Yunlong Jia authored
This adds a new compatible string for Elan eth3915n touchscreen controller, which is compatible with ekth3500. Signed-off-by:
Yunlong Jia <ecs.beijing2022@gmail.com> Suggested-by:
Douglas Anderson <dianders@chromium.org> Reviewed-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by:
-
- 16 Sep, 2022 5 commits
-
-
Dmitry Torokhov authored
Add proper interrupt trigger and gpio polarity data to the binding example. Reviewed-by:
Heiko Stuebner <heiko@sntech.de> Link: https://lore.kernel.org/r/20220914141428.2201784-5-dmitry.torokhov@gmail.comSigned-off-by:
-
Dmitry Torokhov authored
Let's use generic device properties API instead of OF-specific one. Reviewed-by:
-
Dmitry Torokhov authored
Instead of hard-coding rising edge as the interrupt trigger, let's rely on the platform (ACPI, DT) to configure the interrupt properly. Reviewed-by:
-
Dmitry Torokhov authored
This switches the driver to gpiod API and drops uses of of_get_gpio() API. Reviewed-by:
-
Dmitry Torokhov authored
Currently there are no users of auo_pixcir_ts_platdata in the mainline, and having it (with legacy gpio numbers) prevents us from converting the driver to gpiod API, so let's drop it. If, in the future, someone wants to use this driver on non-device tree, non-ACPI system, they should use static device properties instead of platform data. Reviewed-by:
-
- 14 Sep, 2022 6 commits
-
-
AngeloGioacchino Del Regno authored
Add a compatible for the keys found on MT6331 PMIC. Signed-off-by:
AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> Reviewed-by:
Rob Herring <robh@kernel.org> Reviewed-by:
Mattijs Korpershoek <mkorpershoek@baylibre.com> Link: https://lore.kernel.org/r/20220914103021.43593-3-angelogioacchino.delregno@collabora.comSigned-off-by:
-
AngeloGioacchino Del Regno authored
Convert the mtk-pmic-keys to DT schema format. The old binding was missing documentation for key press/release interrupts, even though it was supported in hardware and driver, so support for the same was added during the conversion. Signed-off-by:
-
Lyude Paul authored
Noticed this while trying to debug some unrelated issues: this laptop has the ability to use rmi4 but doesn't by default. So let's fix that. Tested locally, including mouse buttons, on my ThinkPad P1 G3. This might also enable the X1 Extreme G3, but I don't have such a system to test locally (presumably Mark can chime in if that's the case). Signed-off-by:
-
Jeff LaBundy authored
Some devices expose an ultra-low-power (ULP) mode entry mask for each channel. If the mask is set, the device cannot enter ULP so long as the corresponding channel remains in an active state. The vendor has advised setting the mask for any disabled channel. To accommodate this suggestion, initially set all masks and then clear them only if specified in the device tree. Fixes: e505edae ("Input: add support for Azoteq IQS7222A/B/C") Signed-off-by:
Jeff LaBundy <jeff@labundy.com> Link: https://lore.kernel.org/r/20220908131548.48120-8-jeff@labundy.comSigned-off-by:
-
Jeff LaBundy authored
Add a check to prevent sending undefined events, which ultimately map to SYN_REPORT. Fixes: e505edae ("Input: add support for Azoteq IQS7222A/B/C") Signed-off-by:
-
Jeff LaBundy authored
According to the datasheets, writing only 0xFF is sufficient to elicit a communication window. Remove the superfluous 0x00 from the force communication command. Fixes: e505edae ("Input: add support for Azoteq IQS7222A/B/C") Signed-off-by:
-
- 13 Sep, 2022 1 commit
-
-
AngeloGioacchino Del Regno authored
Add support for PMIC Keys of the MT6331 PMIC. Signed-off-by:
-
- 08 Sep, 2022 1 commit
-
-
wangjianli authored
Delete the redundant word 'to'. Signed-off-by:
wangjianli <wangjianli@cdjrlc.com> Link: https://lore.kernel.org/r/20220908131043.37099-1-wangjianli@cdjrlc.comSigned-off-by:
-
- 06 Sep, 2022 5 commits
-
-
Christopher Crockett authored
An effort has been made to support every official model and firmware version I could track down info on. The following controllers _should_ have working paddles with this PR: - Xbox Elite (**untested**) - Xbox Elite Series 2 on early firmwares (**untested**) - Xbox Elite Series 2 on v4 firmwares (Tested v4.8.1908.0) - Xbox Elite Series 2 on v5 pre-BLE firmwares (**untested**) - Xbox Elite Series 2 on v5 post-BLE firmwares (Tested v5.13.3143.0) This patch also introduces correct handling for the Elite 1 controller and properly suppresses paddle inputs when using a custom profile slot. Starting with firmware v5.11, certain inputs for the Elite 2 were moved to an extra packet that is not enabled by default. We must first manually enable this extra packet in order to correctly process paddle input data with these later firmwares. Signed-off-by:
Christopher Crockett <chaorace@gmail.com> Signed-off-by:
Pavel Rojtberg <rojtberg@gmail.com> Tested-by:
Bastien Nocera <hadess@hadess.net> Link: https://lore.kernel.org/r/20220818154411.510308-5-rojtberg@gmail.comSigned-off-by:
-
Santosh De Massari authored
Newer gamepads turn themselves off when the mode button is held down. For XBOX360W gamepads we must do this in the driver. Do not use BIT() macro for consistency within the file. Signed-off-by:
Santosh De Massari <s.demassari@gmail.com> Signed-off-by:
-
Cameron Gutman authored
Suspending and resuming the system can sometimes cause the out URB to get hung after a reset_resume. This causes LED setting and force feedback to break on resume. To avoid this, just drop the reset_resume callback so the USB core rebinds xpad to the wireless pads on resume if a reset happened. A nice side effect of this change is the LED ring on wireless controllers is now set correctly on system resume. Cc: stable@vger.kernel.org Fixes: 4220f7db ("Input: xpad - workaround dead irq_out after suspend/ resume") Signed-off-by:
Cameron Gutman <aicommander@gmail.com> Signed-off-by:
-
Pavel Rojtberg authored
This is based on multiple commits at https://github.com/paroj/xpad Cc: stable@vger.kernel.org Signed-off-by:
Jasper Poppe <jgpoppe@gmail.com> Signed-off-by:
Jeremy Palmer <jpalmer@linz.govt.nz> Signed-off-by:
Ruineka <ruinairas1992@gmail.com> Signed-off-by:
Cleber de Mattos Casali <clebercasali@gmail.com> Signed-off-by:
Kyle Gospodnetich <me@kylegospodneti.ch> Signed-off-by:
-
Francesco Dolcini authored
STMPE driver does not require a specific node name anymore, only the compatible is checked, update binding according to this. Signed-off-by:
Francesco Dolcini <francesco.dolcini@toradex.com> Acked-by:
-
- 03 Sep, 2022 3 commits
-
-
Dmitry Torokhov authored
The driver core now has the ability to handle the creation and removal of device-specific sysfs files, let's use it instead of registering and unregistering attributes by hand. Reviewed-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Link: https://lore.kernel.org/r/20220903051119.1332808-3-dmitry.torokhov@gmail.comSigned-off-by:
-
Dmitry Torokhov authored
The driver core now has the ability to handle the creation and removal of device-specific sysfs files, let's use it instead of registering and unregistering attributes by hand. Reviewed-by:
-
Dmitry Torokhov authored
The driver core now has the ability to handle the creation and removal of device-specific sysfs files, let's use it instead of registering and unregistering attributes by hand. Reviewed-by:
-
- 31 Aug, 2022 11 commits
-
-
ChiYuan Huang authored
Add RT5120 PMIC power key support. Signed-off-by:
ChiYuan Huang <cy_huang@richtek.com> Link: https://lore.kernel.org/r/1660100142-32493-4-git-send-email-u0084500@gmail.comSigned-off-by:
-
Max Krummenacher authored
Clarify properties definition, drop unused pinctrl-2 state 'gpio'. Signed-off-by:
Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by:
-
Max Krummenacher authored
Any IIO ADC can be used with the driver, so do not depend on VF610_ADC. Signed-off-by:
-
Nuno Sá authored
With the new PM macros (DEFINE_SIMPLE_DEV_PM_OPS() and pm_sleep_ptr()), the compiler has visibility to see that the functions are not used when !CONFIG_PM and hence, remove the dead code. As such, there's no need for '__maybe_unused'. Signed-off-by:
Nuno Sá <nuno.sa@analog.com> Reviewed-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Link: https://lore.kernel.org/r/20220829131553.690063-11-nuno.sa@analog.comSigned-off-by:
-
Nuno Sá authored
Support feeding VCC through a regulator. Signed-off-by:
-
Nuno Sá authored
Optionally reset the device during probe. Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Reviewed-by:
-
Nuno Sá authored
Just some code cleanup regarding coding style. With the introduction of the bits.h macros changes in the code are indeed introduced. Signed-off-by:
-
Nuno Sá authored
There's no need for an extra check for 'client-irq'. Just let it fail when calling 'request_irq()'. Signed-off-by:
-
Nuno Sá authored
Add device tree bindings for the adp5588-keys driver. Signed-off-by:
-
Nuno Sá authored
Use firmware properties (eg: OF) to get the device specific configuration. This change just replaces the platform data since there was no platform using it and so, it makes no sense having both. Special note to the PULL-UP disable setting that is now supported as part of the gpio subsystem (using 'set_config()' callback). Signed-off-by:
-
Nuno Sá authored
Don't continue in code paths after some error is found. It makes no sense to do any other device configuration if a previous one failed. Signed-off-by:
-
