Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
kernel-fxtec-pro1x/drivers/staging/nvec
History
Marc Dietrich 3ec698816a staging: nvec: specify a platform-device base id 
commit 6e3f62f079 (mfd: core: Fix platform-device id generation) modified
the computation of the mfd cell id. Negative numbers forbit the specification
of cell ids as we do. Fix this for now by specifying a base of 0 instead. In
the long run, this may be changed to automatic cell ids (base -2).

Reported-by: Misha Komarovskiy <zombah@gmail.com>
Signed-off-by: Marc Dietrich <marvin24@gmx.de>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
2015-01-21 10:31:09 +08:00
..
Kconfig drivers/staging/nvec/Kconfig: remove trailing whitespace 2013-10-30 09:24:40 -07:00
Makefile staging: nvec: rename led driver to board specific paz00 driver 2012-06-25 10:55:38 -07:00
nvec-keytable.h staging: nvec: coding style fixes / add copyright notice 2011-09-29 17:40:37 -07:00
nvec.c staging: nvec: specify a platform-device base id 2015-01-21 10:31:09 +08:00
nvec.h staging: nvec: use reset framework 2013-12-11 16:44:10 -07:00
nvec_kbd.c staging: nvec: drop owner assignment from platform_drivers 2014-10-20 16:21:41 +02:00
nvec_paz00.c staging: nvec: drop owner assignment from platform_drivers 2014-10-20 16:21:41 +02:00
nvec_power.c staging: nvec: drop owner assignment from platform_drivers 2014-10-20 16:21:41 +02:00
nvec_ps2.c staging: nvec: drop owner assignment from platform_drivers 2014-10-20 16:21:41 +02:00
README
TODO staging: nvec: remove use of clk_get_sys 2013-01-28 11:19:33 -07:00

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