On 12/7/20 12:48 PM, Enrico Weigelt, metux IT consult
wrote:> Introducing new GPIO driver for virtual GPIO devices via virtio.
>
Oops, I missed one thing:
>
> diff --git a/Documentation/gpio/virtio-gpio.rst
b/Documentation/gpio/virtio-gpio.rst
> new file mode 100644
> index 000000000000..e7bf01ec1ce7
> --- /dev/null
> +++ b/Documentation/gpio/virtio-gpio.rst
> @@ -0,0 +1,176 @@
>
+"""""""""""""""""
> +Virtio-GPIO protocol specification
>
+"""""""""""""""""
In Documentation/doc-guide/sphinx.rst, it says to please use the
following heading adornments....
and """""...""""" is not one
of them.
Neither is "..........".
Also, only use an overline for the document title and not for
lower level headings.
Here are the expected heading adornments:
1. ``=`` with overline for document title::
============= Document title
=============
2. ``=`` for chapters::
Chapters
=======
3. ``-`` for sections::
Section
-------
4. ``~`` for subsections::
Subsection
~~~~~~~~~~
> +...........
> +Specification for virtio-based virtiual GPIO devices
> +...........
> +
> ++------------
> ++Version_ 1.0
> ++------------
> +
> +==================> +General
> +==================> +
> +The virtio-gpio protocol provides access to general purpose IO devices
> +to virtual machine guests. These virtualized GPIOs could be either
provided
> +by some simulator (eg. virtual HIL), routed to some external device or
> +routed to real GPIOs on the host (eg. virtualized embedded applications).
> +
> +Instead of simulating some existing real GPIO chip within an VMM, this
> +protocol provides an hardware independent interface between host and guest
> +that solely relies on an active virtio connection (no matter which
transport
> +actually used), no other buses or additional platform driver logic
required.
> +
> +==================> +Protocol layout
> +==================> +
> +----------------------
> +Configuration space
> +----------------------
thanks.
--
~Randy