Skip to content

Commit

Permalink
virtio-gpio: Maintain gpio device spec in separate directory
Browse files Browse the repository at this point in the history
Place device specification, its driver and device
conformance into its own directory to have self contained device
specification.

Fixes: #153

Acked-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Parav Pandit <parav@nvidia.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
  • Loading branch information
paravmellanox authored and cohuck committed Jan 30, 2023
1 parent 674489b commit 6c9c04d
Show file tree
Hide file tree
Showing 5 changed files with 21 additions and 22 deletions.
22 changes: 2 additions & 20 deletions conformance.tex
Original file line number Diff line number Diff line change
Expand Up @@ -150,16 +150,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\input{device-types/mem/driver-conformance.tex}
\input{device-types/i2c/driver-conformance.tex}
\input{device-types/scmi/driver-conformance.tex}

\conformance{\subsection}{GPIO Driver Conformance}\label{sec:Conformance / Driver Conformance / GPIO Driver Conformance}

A General Purpose Input/Output (GPIO) driver MUST conform to the following
normative statements:

\begin{itemize}
\item \ref{drivernormative:Device Types / GPIO Device / requestq Operation}
\item \ref{drivernormative:Device Types / GPIO Device / eventq Operation}
\end{itemize}
\input{device-types/gpio/driver-conformance.tex}

\conformance{\subsection}{PMEM Driver Conformance}\label{sec:Conformance / Driver Conformance / PMEM Driver Conformance}

Expand Down Expand Up @@ -252,16 +243,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
\input{device-types/mem/device-conformance.tex}
\input{device-types/i2c/device-conformance.tex}
\input{device-types/scmi/device-conformance.tex}

\conformance{\subsection}{GPIO Device Conformance}\label{sec:Conformance / Device Conformance / GPIO Device Conformance}

A General Purpose Input/Output (GPIO) device MUST conform to the following
normative statements:

\begin{itemize}
\item \ref{devicenormative:Device Types / GPIO Device / requestq Operation}
\item \ref{devicenormative:Device Types / GPIO Device / eventq Operation}
\end{itemize}
\input{device-types/gpio/device-conformance.tex}

\conformance{\subsection}{PMEM Device Conformance}\label{sec:Conformance / Device Conformance / PMEM Device Conformance}

Expand Down
3 changes: 1 addition & 2 deletions content.tex
Original file line number Diff line number Diff line change
Expand Up @@ -3020,8 +3020,7 @@ \chapter{Device Types}\label{sec:Device Types}
\input{device-types/mem/description.tex}
\input{device-types/i2c/description.tex}
\input{device-types/scmi/description.tex}
\input{virtio-gpio.tex}
\input{virtio-pmem.tex}
\input{device-types/gpio/description.tex}

\chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}

Expand Down
File renamed without changes.
9 changes: 9 additions & 0 deletions device-types/gpio/device-conformance.tex
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
\conformance{\subsection}{GPIO Device Conformance}\label{sec:Conformance / Device Conformance / GPIO Device Conformance}

A General Purpose Input/Output (GPIO) device MUST conform to the following
normative statements:

\begin{itemize}
\item \ref{devicenormative:Device Types / GPIO Device / requestq Operation}
\item \ref{devicenormative:Device Types / GPIO Device / eventq Operation}
\end{itemize}
9 changes: 9 additions & 0 deletions device-types/gpio/driver-conformance.tex
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
\conformance{\subsection}{GPIO Driver Conformance}\label{sec:Conformance / Driver Conformance / GPIO Driver Conformance}

A General Purpose Input/Output (GPIO) driver MUST conform to the following
normative statements:

\begin{itemize}
\item \ref{drivernormative:Device Types / GPIO Device / requestq Operation}
\item \ref{drivernormative:Device Types / GPIO Device / eventq Operation}
\end{itemize}

0 comments on commit 6c9c04d

Please sign in to comment.