diff options
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/i2c/busses/i2c-viapro | 6 | ||||
-rw-r--r-- | Documentation/i2c/muxes/i2c-mux-gpio | 18 |
2 files changed, 23 insertions, 1 deletions
diff --git a/Documentation/i2c/busses/i2c-viapro b/Documentation/i2c/busses/i2c-viapro index 2e758b0e9456..b88f91ae580e 100644 --- a/Documentation/i2c/busses/i2c-viapro +++ b/Documentation/i2c/busses/i2c-viapro | |||
@@ -20,7 +20,10 @@ Supported adapters: | |||
20 | Datasheet: available on http://linux.via.com.tw | 20 | Datasheet: available on http://linux.via.com.tw |
21 | 21 | ||
22 | * VIA Technologies, Inc. VX855/VX875 | 22 | * VIA Technologies, Inc. VX855/VX875 |
23 | Datasheet: Availability unknown | 23 | Datasheet: available on http://linux.via.com.tw |
24 | |||
25 | * VIA Technologies, Inc. VX900 | ||
26 | Datasheet: available on http://linux.via.com.tw | ||
24 | 27 | ||
25 | Authors: | 28 | Authors: |
26 | Kyösti Mälkki <kmalkki@cc.hut.fi>, | 29 | Kyösti Mälkki <kmalkki@cc.hut.fi>, |
@@ -57,6 +60,7 @@ Your lspci -n listing must show one of these : | |||
57 | device 1106:8324 (CX700) | 60 | device 1106:8324 (CX700) |
58 | device 1106:8353 (VX800/VX820) | 61 | device 1106:8353 (VX800/VX820) |
59 | device 1106:8409 (VX855/VX875) | 62 | device 1106:8409 (VX855/VX875) |
63 | device 1106:8410 (VX900) | ||
60 | 64 | ||
61 | If none of these show up, you should look in the BIOS for settings like | 65 | If none of these show up, you should look in the BIOS for settings like |
62 | enable ACPI / SMBus or even USB. | 66 | enable ACPI / SMBus or even USB. |
diff --git a/Documentation/i2c/muxes/i2c-mux-gpio b/Documentation/i2c/muxes/i2c-mux-gpio index bd9b2299b739..d4d91a53fc39 100644 --- a/Documentation/i2c/muxes/i2c-mux-gpio +++ b/Documentation/i2c/muxes/i2c-mux-gpio | |||
@@ -63,3 +63,21 @@ static struct platform_device myboard_i2cmux = { | |||
63 | .platform_data = &myboard_i2cmux_data, | 63 | .platform_data = &myboard_i2cmux_data, |
64 | }, | 64 | }, |
65 | }; | 65 | }; |
66 | |||
67 | If you don't know the absolute GPIO pin numbers at registration time, | ||
68 | you can instead provide a chip name (.chip_name) and relative GPIO pin | ||
69 | numbers, and the i2c-gpio-mux driver will do the work for you, | ||
70 | including deferred probing if the GPIO chip isn't immediately | ||
71 | available. | ||
72 | |||
73 | Device Registration | ||
74 | ------------------- | ||
75 | |||
76 | When registering your i2c-gpio-mux device, you should pass the number | ||
77 | of any GPIO pin it uses as the device ID. This guarantees that every | ||
78 | instance has a different ID. | ||
79 | |||
80 | Alternatively, if you don't need a stable device name, you can simply | ||
81 | pass PLATFORM_DEVID_AUTO as the device ID, and the platform core will | ||
82 | assign a dynamic ID to your device. If you do not know the absolute | ||
83 | GPIO pin numbers at registration time, this is even the only option. | ||