Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kernel-source-code-drivers: add libgpiod for userspace driver #246

Merged
merged 1 commit into from
Oct 28, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -245,12 +245,12 @@ \subsection{Linux kernel source code}
\begin{frame}
\frametitle{User space device drivers 1/2}
\begin{itemize}
\item The kernel provides certain mechanisms to access hardware
directly from userspace:
\item The kernel provides some mechanisms to access hardware from userspace:
\begin{itemize}
\item USB devices with {\em libusb}, \url{https://libusb.info/}
\item SPI devices with {\em spidev}, \kdochtml{spi/spidev}
\item I2C devices with {\em i2cdev}, \kdochtml{i2c/dev-interface}
\item GPIOs with {\em libgpiod}, \url{https://libgpiod.readthedocs.io}
\item Memory-mapped devices with {\em UIO}, including interrupt
handling, \kdochtml{driver-api/uio-howto}
\end{itemize}
Expand All @@ -264,7 +264,7 @@ \subsection{Linux kernel source code}
\item Certain classes of devices like printers and scanners do not
have any kernel support, they have always been handled in user space
for historical reasons.
\item Otherwise this is *not* how the system should be
\item Otherwise this is {\bf \em not} how the system should be
architectured. Kernel drivers should always be preferred!
\end{itemize}
\end{frame}
Expand Down