remarkable-linux

History

Tejun Heo eb1e40a4dd staging: nvec: use system_nrt_wq instead of custom one There isn't much reason to use custom workqueue in nvec. It can use system_nrt_wq instead and cancel the two work items on removal. Signed-off-by: Tejun Heo <tj@kernel.org> Signed-off-by: Marc Dietrich <marvin24@gmx.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2012-09-04 13:18:15 -07:00
..
Kconfig	staging: nvec: do not depend on MACH_PAZ00	2012-09-04 13:18:15 -07:00
Makefile	staging: nvec: rename led driver to board specific paz00 driver	2012-06-25 10:55:38 -07:00
nvec-keytable.h
nvec.c	staging: nvec: use system_nrt_wq instead of custom one	2012-09-04 13:18:15 -07:00
nvec.h
nvec_kbd.c	staging: nvec: add remove function to nvec childs	2012-06-25 10:55:38 -07:00
nvec_paz00.c	staging: nvec: rename led driver to board specific paz00 driver	2012-06-25 10:55:38 -07:00
nvec_power.c	staging: nvec: add remove function to nvec childs	2012-06-25 10:55:38 -07:00
nvec_ps2.c	staging: nvec: add remove function to nvec childs	2012-06-25 10:55:38 -07:00
README
TODO

README

NVEC: An NVidia compliant Embedded Controller Protocol Implemenation

This is an implementation of the NVEC protocol used to communicate with an
embedded controller (EC) via I2C bus. The EC is an I2C master while the host
processor is the I2C slave. Requests from the host processor to the EC are
started by triggering a gpio line.

There is no written documentation of the protocol available to the public,
but the source code[1] of the published nvec reference drivers can be a guide.
This driver is currently only used by the AC100 project[2], but it is likely,
that other Tegra boards (not yet mainlined, if ever) also use it.

[1] e.g. http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=tree;f=arch/arm/mach-tegra/nvec;hb=android-tegra-2.6.32
[2] http://gitorious.org/ac100, http://launchpad.net/ac100