linux

Files

Greg Kroah-Hartman 971bcfca1f staging: nvec: add SPDX identifier.

It's good to have SPDX identifiers in all files to make it easier to
audit the kernel tree for correct licenses.

Fix up the staging nvec driver to have a proper SPDX identifiers, based
on the license text in the file itself.  The SPDX identifier is a
legally binding shorthand, which can be used instead of the full boiler
plate text.

This work is based on a script and data from Thomas Gleixner, Philippe
Ombredanne, and Kate Stewart.

Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Kate Stewart <kstewart@linuxfoundation.org>
Cc: Philippe Ombredanne <pombredanne@nexb.com>
Cc: Marc Dietrich <marvin24@gmx.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

2018-01-15 16:03:45 +01:00

Kconfig

…

Makefile

License cleanup: add SPDX GPL-2.0 license identifier to files with no license

2017-11-02 11:10:55 +01:00

nvec_kbd.c

staging: nvec: add SPDX identifier.

2018-01-15 16:03:45 +01:00

nvec_paz00.c

staging: nvec: add SPDX identifier.

2018-01-15 16:03:45 +01:00

nvec_power.c

staging: nvec: add SPDX identifier.

2018-01-15 16:03:45 +01:00

nvec_ps2.c

staging: nvec: add SPDX identifier.

2018-01-15 16:03:45 +01:00

nvec-keytable.h

staging: nvec: add SPDX identifier.

2018-01-15 16:03:45 +01:00

nvec.c

staging: nvec: add SPDX identifier.

2018-01-15 16:03:45 +01:00

nvec.h

staging: nvec: add SPDX identifier.

2018-01-15 16:03:45 +01:00

README

…

TODO

Staging: nvec: Modify the nvec_write_sync method to return the error code

2016-02-14 16:52:15 -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