openkylin
/
linux
mirror of https://gitee.com/openkylin/linux.git
9
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: gpio: intro: Improve HTML formatting 

Currently the HTML output for Documentation/driver-api/gpio/intro.rst
doesn't look right. The lines that start with LOW or HIGH are formatted
in bold, while the next line after each is not bold.

With this patch, the HTML looks better.

Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
This commit is contained in:
Jonathan Neuschäfer 2021-01-01 21:43:25 +01:00 committed by Bartosz Golaszewski
parent db63c0953c
commit e1d4d66338
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/driver-api/gpio/intro.rst
View File

@ -106,11 +106,11 @@ don't. When you need open drain signaling but your hardware doesn't directly
support it, there's a common idiom you can use to emulate it with any GPIO pin support it, there's a common idiom you can use to emulate it with any GPIO pin
that can be used as either an input or an output: that can be used as either an input or an output:
LOW: gpiod_direction_output(gpio, 0) ... this drives the signal and overrides **LOW**: ``gpiod_direction_output(gpio, 0)`` ... this drives the signal and
the pullup. overrides the pullup.
HIGH: gpiod_direction_input(gpio) ... this turns off the output, so the pullup **HIGH**: ``gpiod_direction_input(gpio)`` ... this turns off the output, so
(or some other device) controls the signal. the pullup (or some other device) controls the signal.
The same logic can be applied to emulate open source signaling, by driving the The same logic can be applied to emulate open source signaling, by driving the
high signal and configuring the GPIO as input for low. This open drain/open high signal and configuring the GPIO as input for low. This open drain/open