Commit e1d4d663 authored by Jonathan Neuschäfer's avatar Jonathan Neuschäfer Committed by Bartosz Golaszewski

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: default avatarJonathan Neuschäfer <j.neuschaefer@gmx.net>
Signed-off-by: default avatarBartosz Golaszewski <bgolaszewski@baylibre.com>
parent db63c095
...@@ -106,11 +106,11 @@ don't. When you need open drain signaling but your hardware doesn't directly ...@@ -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
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment