summaryrefslogtreecommitdiff
path: root/Documentation/i2c/old-module-parameters.rst
diff options
context:
space:
mode:
authorLuca Ceresoli <luca@lucaceresoli.net>2020-01-29 16:19:29 +0100
committerWolfram Sang <wsa@the-dreams.de>2020-01-29 22:01:24 +0100
commit2f07c05f14a8bf5ee815e159a451d580d9113db9 (patch)
tree8a9d9df29daec1392238314a34b681354ba1f569 /Documentation/i2c/old-module-parameters.rst
parent020bc5b9296af6d3e0b255cff3a2674191287624 (diff)
docs: i2c: call it "I2C" consistently
Uppercase "I2C" is used almost everywhere in the docs, but the lowercase version "i2c" is used somewhere. Use the uppercase form consistently. Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Acked-by: Peter Rosin <peda@axentia.se> Reviewed-by: Jean Delvare <jdelvare@suse.de> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'Documentation/i2c/old-module-parameters.rst')
-rw-r--r--Documentation/i2c/old-module-parameters.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/i2c/old-module-parameters.rst b/Documentation/i2c/old-module-parameters.rst
index a1939512ad66..78a6950e5763 100644
--- a/Documentation/i2c/old-module-parameters.rst
+++ b/Documentation/i2c/old-module-parameters.rst
@@ -2,14 +2,14 @@
I2C device driver binding control from user-space
=================================================
-Up to kernel 2.6.32, many i2c drivers used helper macros provided by
+Up to kernel 2.6.32, many I2C drivers used helper macros provided by
<linux/i2c.h> which created standard module parameters to let the user
-control how the driver would probe i2c buses and attach to devices. These
+control how the driver would probe I2C buses and attach to devices. These
parameters were known as "probe" (to let the driver probe for an extra
address), "force" (to forcibly attach the driver to a given device) and
"ignore" (to prevent a driver from probing a given address).
-With the conversion of the i2c subsystem to the standard device driver
+With the conversion of the I2C subsystem to the standard device driver
binding model, it became clear that these per-module parameters were no
longer needed, and that a centralized implementation was possible. The new,
sysfs-based interface is described in the documentation file