linux-toradex.git/drivers/i2c, branch tegra-10.8.3

[arm/tegra]i2c:msg index should be valid for print error.

2010-07-09T17:09:52+00:00

The index for msg during printing the NvRmI2cTransaction() status
is out of the range. The msg index should be maximum of num -1
where num is number of messages.
Fixing this issue to print correctly.

Change-Id: I43841e3278e3041aae422ebe8bdef2dbd84b6084
Reviewed-on: http://git-master/r/3727
Reviewed-by: Gary King 
Tested-by: Gary King

i2c-tegra: memset all buffers to 0

2010-06-27T15:54:00+00:00

stack-allocated transaction & data buffers were not getting memset to 0,
resulting in invalid transactions getting sent to the RM

Change-Id: I8e16f0c90f74c31cf03b69cb098436e4e64e215e
Reviewed-on: http://git-master/r/3244
Reviewed-by: Gary King 
Tested-by: Gary King

[ARM/tegra] board-nvodm: register I2C devices for simple platforms

2010-05-28T04:41:01+00:00

on platforms which have simple configurations (specifically no pinmux
multiplexing for I2C controllers), implement a helper function in
board-nvodm to register all of the I2C master controllers on the system
based on the ODM kit-specified values.

the code will skip registering I2C slave controllers, which are currently
detected by the SMBUS GUID.

also, since board-generic is really intended to be only for NVIDIA
development boards, make the terminology in the file more clearly
NVIDIA-specific.

Change-Id: I115fb6bf68d93f62a548d65fa5bfdd2d00c13fbc

i2c: tegra: switch to using the NVIDIA RM-based I2C driver

2010-05-28T04:41:00+00:00

since the RM APIs are used by ODM kits prior to device initialization
(to read EEPROMs and the like), implementing the RM on top of Linux's
I2C API won't happen immediately

Change-Id: I8a97e13a7fda8bafaf74e2251e8bd1b0e32dc058

[ARM] tegra: i2c: Fix i2c driver behavior on timeout/nack

2010-05-22T03:01:40+00:00

Change-Id: Ib7c22898783fdc66fa626e06360bd5ca9637067e

i2c/tegra: add support for multiple-busses-per-controller

2010-05-06T03:25:21+00:00

by dynamically changing the pin mux programming, it is possible
to make a single I2C controller function as multiple busses

since this is highly platform-dependent, platform code is responsible
for providing the correct pin mux list for each pseudo-bus interface,
and the adapter programs this prior to performing a transfer; each
multiplexed configuration is added as a unique I2C adapter.

if multiplexing is used, pseudo-bus interface zero's mutex is used
to prevent multiple adapters from clobbering pin mux settings while
the same underlying controller is in-use

also, as a power-saving measure, place the active I2C interface
into tristate after each transfer completes

Change-Id: I343ecd7499abc8d8a0430066f5ec66a1f30180a4

dynamic tristate

Change-Id: Ib5032be15a15cfe7d2d159b7bff0cd27f12d74b3

[ARM] tegra: i2c: Disable clock when idle, fix dvc

2010-05-06T03:25:14+00:00

Change-Id: Idca4c392134640f611ccf10edfd28fea102742fb
Signed-off-by: Colin Cross

[ARM] tegra: Add i2c support

2010-04-23T21:38:22+00:00

Signed-off-by: Colin Cross

Merge commit 'v2.6.32.9' into android-2.6.32

2010-03-11T00:38:33+00:00

i2c-tiny-usb: Fix on big-endian systems

2010-02-23T15:37:48+00:00

commit 1c010ff8912cbc08d80e865aab9c32b6b00c527d upstream.

The functionality bit vector is always returned as a little-endian
32-bit number by the device, so it must be byte-swapped to the host
endianness.

On the other hand, the delay value is handled by the USB stack, so no
byte swapping is needed on our side.

This fixes bug #15105:
http://bugzilla.kernel.org/show_bug.cgi?id=15105

Reported-by: Jens Richter 
Signed-off-by: Jean Delvare 
Tested-by: Jens Richter 
Cc: Till Harbaum 
Signed-off-by: Greg Kroah-Hartman