kernel-fxtec-pro1x/drivers/staging/nvec
Marc Dietrich ca250b6017 staging: nvec: re-enable the clock on resume
On resume the slave controller is reinitialized. The tegra i2c master
controller disables the clock at the end of the initialiation, propably
to save some power, and enables it again on each transfer. We don't
do this yet and also forgot to enable the clock on resume. Fix this
copy-paste error by not disabling the clock after initialization.

This didn't striked us yet because suspend/resume hasn't landed in mainline
yet, but will soon.

Signed-off-by: Marc Dietrich <marvin24@gmx.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-29 11:29:37 -07:00
..
Kconfig staging: nvec: allow modular build 2013-04-23 10:34:20 -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: re-enable the clock on resume 2013-07-29 11:29:37 -07:00
nvec.h staging: nvec: remove instantiating via platform device 2013-06-24 15:59:03 -07:00
nvec_kbd.c staging: nvec: Convert to use devm_input_allocate 2013-05-16 16:04:31 -07:00
nvec_paz00.c staging: nvec: remove use of __devexit 2012-11-21 14:23:51 -08:00
nvec_power.c staging: nvec: cleanup childs on remove 2013-05-14 07:07:50 -04:00
nvec_ps2.c staging: nvec: cleanup childs on remove 2013-05-14 07:07:50 -04:00
README
TODO staging: nvec: remove use of clk_get_sys 2013-01-28 11:19:33 -07:00

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