[FE training-materials-updates] MMIO and PIO: remove ioport_map and friends

Michael Opdenacker michael.opdenacker at free-electrons.com
Thu Oct 9 14:14:56 CEST 2014


Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=1b6592a01a3a7e308bca13578c988566ada68a6b

>---------------------------------------------------------------

commit 1b6592a01a3a7e308bca13578c988566ada68a6b
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Oct 9 14:13:02 2014 +0200

    MMIO and PIO: remove ioport_map and friends
    
    - This API never really took off, and it's use
      is about 1/10th of the regular one.
    
    - Probably not worth the time to describe it. Best to focus
      on more important things.
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


>---------------------------------------------------------------

1b6592a01a3a7e308bca13578c988566ada68a6b
 .../kernel-driver-development-io-memory.tex        | 23 ----------------------
 1 file changed, 23 deletions(-)

diff --git a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
index 78b6471..2c5aa42 100644
--- a/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
+++ b/slides/kernel-driver-development-io-memory/kernel-driver-development-io-memory.tex
@@ -221,29 +221,6 @@ __raw_writel(1 << KS8695_IRQ_UART_TX,
 \end{frame}
 
 \begin{frame}
-  \frametitle{New API for mixed accesses}
-  \begin{itemize}
-  \item A new API allows to write drivers that can work on either
-    devices accessed over PIO or MMIO. A few drivers use it, but there
-    doesn't seem to be a consensus in the kernel community around it.
-  \item Mapping
-    \begin{itemize}
-    \item For PIO: \kfunc{ioport_map} and \kfunc{ioport_unmap}. They
-      don't really map, but they return a special iomem cookie.
-    \item For MMIO: \kfunc{ioremap} and \kfunc{iounmap}. As usual.
-    \end{itemize}
-  \item Access, works both on addresses or cookies returned by
-    \kfunc{ioport_map} and \kfunc{ioremap}
-    \begin{itemize}
-    \item \code{ioread[8/16/32]()} and \code{iowrite[8/16/32]} for
-      single access
-    \item \code{ioread[8/16/32]_rep()} and
-      \code{iowrite[8/16/32]_rep()} for repeated accesses
-    \end{itemize}
-  \end{itemize}
-\end{frame}
-
-\begin{frame}
   \frametitle{Avoiding I/O access issues}
   \begin{itemize}
   \item Caching on I/O ports or memory already disabled



More information about the training-materials-updates mailing list