adulau/aha
1
0
Fork 0
mirror of https://github.com/adulau/aha.git synced 2024-12-27 19:26:25 +00:00
Code Issues Projects Releases Packages Wiki Activity

i2c: Delete an outdated piece of documentation

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

Signed-off-by: Jean Delvare <khali@linux-fr.org>
This commit is contained in:
Jean Delvare 2007-12-12 13:45:24 +01:00 committed by Jean Delvare
parent 4af7565303
commit 45ccc6c50d
1 changed files with 4 additions and 41 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

45
Documentation/i2c/summary
View file

@ -1,5 +1,3 @@
This is an explanation of what i2c is, and what is supported in this package.
I2C and SMBus I2C and SMBus
============= =============
@ -33,52 +31,17 @@ When we talk about I2C, we use the following terms:
Client Client
An Algorithm driver contains general code that can be used for a whole class An Algorithm driver contains general code that can be used for a whole class
of I2C adapters. Each specific adapter driver depends on one algorithm of I2C adapters. Each specific adapter driver either depends on one algorithm
driver. driver, or includes its own implementation.
A Driver driver (yes, this sounds ridiculous, sorry) contains the general A Driver driver (yes, this sounds ridiculous, sorry) contains the general
code to access some type of device. Each detected device gets its own code to access some type of device. Each detected device gets its own
data in the Client structure. Usually, Driver and Client are more closely data in the Client structure. Usually, Driver and Client are more closely
integrated than Algorithm and Adapter. integrated than Algorithm and Adapter.
For a given configuration, you will need a driver for your I2C bus (usually For a given configuration, you will need a driver for your I2C bus, and
a separate Adapter and Algorithm driver), and drivers for your I2C devices drivers for your I2C devices (usually one driver for each device).
(usually one driver for each device). There are no I2C device drivers
in this package. See the lm_sensors project http://www.lm-sensors.nu
for device drivers.
At this time, Linux only operates I2C (or SMBus) in master mode; you can't At this time, Linux only operates I2C (or SMBus) in master mode; you can't
use these APIs to make a Linux system behave as a slave/device, either to use these APIs to make a Linux system behave as a slave/device, either to
speak a custom protocol or to emulate some other device. speak a custom protocol or to emulate some other device.
Included Bus Drivers
====================
Note that only stable drivers are patched into the kernel by 'mkpatch'.
Base modules
------------
i2c-core: The basic I2C code, including the /proc/bus/i2c* interface
i2c-dev: The /dev/i2c-* interface
i2c-proc: The /proc/sys/dev/sensors interface for device (client) drivers
Algorithm drivers
-----------------
i2c-algo-bit: A bit-banging algorithm
i2c-algo-pcf: A PCF 8584 style algorithm
i2c-algo-ibm_ocp: An algorithm for the I2C device in IBM 4xx processors (NOT BUILT BY DEFAULT)
Adapter drivers
---------------
i2c-elektor: Elektor ISA card (uses i2c-algo-pcf)
i2c-elv: ELV parallel port adapter (uses i2c-algo-bit)
i2c-pcf-epp: PCF8584 on a EPP parallel port (uses i2c-algo-pcf) (NOT mkpatched)
i2c-philips-par: Philips style parallel port adapter (uses i2c-algo-bit)
i2c-adap-ibm_ocp: IBM 4xx processor I2C device (uses i2c-algo-ibm_ocp) (NOT BUILT BY DEFAULT)
i2c-pport: Primitive parallel port adapter (uses i2c-algo-bit)
i2c-velleman: Velleman K8000 parallel port adapter (uses i2c-algo-bit)