WSL2-Linux-Kernel

История

Philipp Zabel 5d5272a517 staging: nvec: explicitly request exclusive reset control Commit `a53e35db70` ("reset: Ensure drivers are explicit when requesting reset lines") started to transition the reset control request API calls to explicitly state whether the driver needs exclusive or shared reset control behavior. Convert all drivers requesting exclusive resets to the explicit API call so the temporary transition helpers can be removed. No functional changes. Cc: Marc Dietrich <marvin24@gmx.de> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: linux-tegra@vger.kernel.org Cc: devel@driverdev.osuosl.org Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2017-07-30 08:28:21 -07:00
..
Kconfig	…
Makefile	…
README	…
TODO	Staging: nvec: Modify the nvec_write_sync method to return the error code	2016-02-14 16:52:15 -08:00
nvec-keytable.h	Staging: nvec: Remove FSF's mailing address	2017-04-08 12:55:25 +02:00
nvec.c	staging: nvec: explicitly request exclusive reset control	2017-07-30 08:28:21 -07:00
nvec.h	staging: nvec: Fix incorrect type of i2c address	2017-02-14 09:14:28 -08:00
nvec_kbd.c	staging: nvec: Remove unnecessary cast on void pointer	2017-03-09 17:38:55 +01:00
nvec_paz00.c	staging: nvec: Remove blank lines before a close brace	2016-03-11 22:09:09 -08:00
nvec_power.c	staging: nvec: fix indent issue in nvec_power.c	2017-01-03 15:22:30 +01:00
nvec_ps2.c	staging:nvec:nvec_ps2.c: Prefering kzalloc(sizeof(*ser_dev)...) over kzalloc(sizeof(struct serio)...)	2017-02-14 09:26:26 -08:00

README

NVEC: An NVidia compliant Embedded Controller Protocol Implementation

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