Yes, some embedded devices still use the i8042 controller. This patch set
enables the i8042 driver to get necessary information from Device Tree
instead of using specific headers with hardcoded addresses for each
specific machine. For example, vt8500 architecture has i8042.
v2:
-Changes in the documentation.
-Errors fixed in the initialization function.
-Redundant parameters removed from Device Tree bindings (init-reset, etc.).
v3:
-Reduced amount of 'ifdefs' in the i8042.c file. Initialization order
is now the same for all architectures.
Warning: the change in v3 is more controversial and needs more testing
since affects all architectures which use the driver. Please give
information regarding required steps to get this patch accepted. Would
be great to find testers to get additional tested-by records.
Roman Volkov (5):
i8042: intel-8042 DT documentation
i8042: Kernel configuration handling for DT support
i8042: Add OF match table
i8042: Prepare i8042 driver for DT support
i8042: Add i8042_dt.h glue for DT support
.../devicetree/bindings/input/intel-8042.txt | 26 ++++++
drivers/input/serio/i8042-dt.h | 104 +++++++++++++++++++++
drivers/input/serio/i8042.c | 56 ++++++-----
drivers/input/serio/i8042.h | 3 +
4 files changed, 168 insertions(+), 21 deletions(-)
create mode 100644 Documentation/devicetree/bindings/input/intel-8042.txt
create mode 100644 drivers/input/serio/i8042-dt.h
--
2.3.0
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
