Doug / smarc-fsl-linux-kernel

Download as
Browse Code ยป

Commit 45ccc6c50dfd227b40122fea649b5fc887caa174

Authored by Jean Delvare
Committed by Jean Delvare
1 parent 4af7565303
Exists in master and in 7 other branches imx_3.0.35_4.1.0, imx_3.10.17_1.0.1_ga, imx_3.10.53_1.1.0_ga, imx_3.14.28_1.0.0_ga, smarc-imx_3.10.53_1.1.0_ga, smarc-imx_3.14.28_1.0.0_ga, smarc-l5.0.0_1.0.0-ga

i2c: Delete an outdated piece of documentation 

I'm amazed that this old piece of documentation managed to survive
until today.

Signed-off-by: Jean Delvare <khali@linux-fr.org>

Showing 1 changed file with 4 additions and 41 deletions Side-by-side Diff

Documentation/i2c/summary
Diff comments   View file @ 45ccc6c
1   -This is an explanation of what i2c is, and what is supported in this package.
2   -
3 1 I2C and SMBus
4 2 =============
5 3  
6 4  
7 5  
... ... @@ -33,52 +31,18 @@
33 31 Client
34 32  
35 33 An Algorithm driver contains general code that can be used for a whole class
36   -of I2C adapters. Each specific adapter driver depends on one algorithm
37   -driver.
  34 +of I2C adapters. Each specific adapter driver either depends on one algorithm
  35 +driver, or includes its own implementation.
38 36  
39 37 A Driver driver (yes, this sounds ridiculous, sorry) contains the general
40 38 code to access some type of device. Each detected device gets its own
41 39 data in the Client structure. Usually, Driver and Client are more closely
42 40 integrated than Algorithm and Adapter.
43 41  
44   -For a given configuration, you will need a driver for your I2C bus (usually
45   -a separate Adapter and Algorithm driver), and drivers for your I2C devices
46   -(usually one driver for each device). There are no I2C device drivers
47   -in this package. See the lm_sensors project http://www.lm-sensors.nu
48   -for device drivers.
  42 +For a given configuration, you will need a driver for your I2C bus, and
  43 +drivers for your I2C devices (usually one driver for each device).
49 44  
50 45 At this time, Linux only operates I2C (or SMBus) in master mode; you can't
51 46 use these APIs to make a Linux system behave as a slave/device, either to
52 47 speak a custom protocol or to emulate some other device.
53   -
54   -
55   -Included Bus Drivers
56   -====================
57   -Note that only stable drivers are patched into the kernel by 'mkpatch'.
58   -
59   -
60   -Base modules
61   -------------
62   -
63   -i2c-core: The basic I2C code, including the /proc/bus/i2c* interface
64   -i2c-dev: The /dev/i2c-* interface
65   -i2c-proc: The /proc/sys/dev/sensors interface for device (client) drivers
66   -
67   -Algorithm drivers
68   ------------------
69   -
70   -i2c-algo-bit: A bit-banging algorithm
71   -i2c-algo-pcf: A PCF 8584 style algorithm
72   -i2c-algo-ibm_ocp: An algorithm for the I2C device in IBM 4xx processors (NOT BUILT BY DEFAULT)
73   -
74   -Adapter drivers
75   ----------------
76   -
77   -i2c-elektor: Elektor ISA card (uses i2c-algo-pcf)
78   -i2c-elv: ELV parallel port adapter (uses i2c-algo-bit)
79   -i2c-pcf-epp: PCF8584 on a EPP parallel port (uses i2c-algo-pcf) (NOT mkpatched)
80   -i2c-philips-par: Philips style parallel port adapter (uses i2c-algo-bit)
81   -i2c-adap-ibm_ocp: IBM 4xx processor I2C device (uses i2c-algo-ibm_ocp) (NOT BUILT BY DEFAULT)
82   -i2c-pport: Primitive parallel port adapter (uses i2c-algo-bit)
83   -i2c-velleman: Velleman K8000 parallel port adapter (uses i2c-algo-bit)