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

Documentation: gpio: driver: Format code blocks properly

This fixes a lot of Sphinx warnings, and makes the code blocks look nice
in HTML.
Signed-off-by: default avatarJonathan Neuschäfer <j.neuschaefer@gmx.net>
Signed-off-by: default avatarBartosz Golaszewski <bgolaszewski@baylibre.com>
parent bcc6d99a
...@@ -415,6 +415,8 @@ If you do this, the additional irq_chip will be set up by gpiolib at the ...@@ -415,6 +415,8 @@ If you do this, the additional irq_chip will be set up by gpiolib at the
same time as setting up the rest of the GPIO functionality. The following same time as setting up the rest of the GPIO functionality. The following
is a typical example of a cascaded interrupt handler using gpio_irq_chip: is a typical example of a cascaded interrupt handler using gpio_irq_chip:
.. code-block:: c
/* Typical state container with dynamic irqchip */ /* Typical state container with dynamic irqchip */
struct my_gpio { struct my_gpio {
struct gpio_chip gc; struct gpio_chip gc;
...@@ -450,6 +452,8 @@ is a typical example of a cascaded interrupt handler using gpio_irq_chip: ...@@ -450,6 +452,8 @@ is a typical example of a cascaded interrupt handler using gpio_irq_chip:
The helper support using hierarchical interrupt controllers as well. The helper support using hierarchical interrupt controllers as well.
In this case the typical set-up will look like this: In this case the typical set-up will look like this:
.. code-block:: c
/* Typical state container with dynamic irqchip */ /* Typical state container with dynamic irqchip */
struct my_gpio { struct my_gpio {
struct gpio_chip gc; struct gpio_chip gc;
......
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