diff options
| author | Luca Ceresoli <luca@lucaceresoli.net> | 2020-01-29 16:19:50 +0100 |
|---|---|---|
| committer | Wolfram Sang <wsa@the-dreams.de> | 2020-01-29 22:01:59 +0100 |
| commit | 1ef0572296273b634339dd9c640c20ce1b8f436f (patch) | |
| tree | 938236395e15e757b808387e716a95a61461f141 | |
| parent | dfea2b16cc993ff00d0e1c137fd9b3e8f4badcd3 (diff) | |
| download | linux-1ef0572296273b634339dd9c640c20ce1b8f436f.tar.gz linux-1ef0572296273b634339dd9c640c20ce1b8f436f.tar.bz2 linux-1ef0572296273b634339dd9c640c20ce1b8f436f.zip | |
docs: i2c: old-module-parameters: use monospace instead of ""
Use a monospace (literal) formatting for better readability of sysfs
attributes and the "dummy" client name. This looks much more readable in
ReST-generated output.
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Reviewed-by: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
| -rw-r--r-- | Documentation/i2c/old-module-parameters.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/i2c/old-module-parameters.rst b/Documentation/i2c/old-module-parameters.rst index 92a403d21a62..3b93cb88eebc 100644 --- a/Documentation/i2c/old-module-parameters.rst +++ b/Documentation/i2c/old-module-parameters.rst @@ -10,9 +10,9 @@ I2C device driver binding control from user-space 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 -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). +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 binding model, it became clear that these per-module parameters were no @@ -47,8 +47,8 @@ New method (sysfs interface):: # echo dummy 0x2f > /sys/bus/i2c/devices/i2c-1/new_device # modprobe <driver> -Of course, it is important to instantiate the "dummy" device before loading +Of course, it is important to instantiate the ``dummy`` device before loading the driver. The dummy device will be handled by i2c-core itself, preventing other drivers from binding to it later on. If there is a real device at the problematic address, and you want another driver to bind to it, then simply -pass the name of the device in question instead of "dummy". +pass the name of the device in question instead of ``dummy``. |