[FE training-materials-updates] Minor corrections
Michael Opdenacker
michael.opdenacker at free-electrons.com
Fri Dec 11 08:47:28 CET 2015
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=cb9c2ffbac5afff984b95ae3667dce2a34e6c030
>---------------------------------------------------------------
commit cb9c2ffbac5afff984b95ae3667dce2a34e6c030
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Fri Dec 11 08:47:28 2015 +0100
Minor corrections
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
cb9c2ffbac5afff984b95ae3667dce2a34e6c030
slides/kernel-contribution/kernel-contribution.tex | 24 ++++-----
.../kernel-driver-development-dma.tex | 58 ++++++++++------------
.../kernel-driver-development-mmap.tex | 2 +-
3 files changed, 37 insertions(+), 47 deletions(-)
diff --git a/slides/kernel-contribution/kernel-contribution.tex b/slides/kernel-contribution/kernel-contribution.tex
index a77413a..685dd06 100644
--- a/slides/kernel-contribution/kernel-contribution.tex
+++ b/slides/kernel-contribution/kernel-contribution.tex
@@ -51,20 +51,18 @@
\begin{frame}
\frametitle{How to Become a Kernel Developer?}
+ Recommended resources
\begin{itemize}
- \item Recommended resources
- \begin{itemize}
- \item See \kerneldoc{SubmittingPatches} for guidelines
- and \url{http://kernelnewbies.org/UpstreamMerge} for very
- helpful advice to have your changes merged upstream (by Rik van
- Riel).
- \item Watch the \emph{Write and Submit your first Linux kernel
- Patch} talk by Greg. K.H:
- \url{http://www.youtube.com/watch?v=LLBrBBImJt4}
- \item How to Participate in the Linux Community (by Jonathan
- Corbet) A Guide To The Kernel Development Process
- \url{http://j.mp/tX2Ld6}
- \end{itemize}
+ \item See \kerneldoc{SubmittingPatches} for guidelines
+ and \url{http://kernelnewbies.org/UpstreamMerge} for very
+ helpful advice to have your changes merged upstream (by Rik van
+ Riel).
+ \item Watch the \emph{Write and Submit your first Linux kernel
+ Patch} talk by Greg. K.H:
+ \url{http://www.youtube.com/watch?v=LLBrBBImJt4}
+ \item How to Participate in the Linux Community (by Jonathan
+ Corbet) A Guide To The Kernel Development Process
+ \url{http://j.mp/tX2Ld6}
\end{itemize}
\end{frame}
diff --git a/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex b/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex
index 27d90fb..3c0d971 100644
--- a/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex
+++ b/slides/kernel-driver-development-dma/kernel-driver-development-dma.tex
@@ -67,41 +67,37 @@
\begin{frame}
\frametitle{Memory Synchronization Issues}
+ Memory caching could interfere with DMA
\begin{itemize}
- \item Memory caching could interfere with DMA
+ \item Before DMA to device
\begin{itemize}
- \item Before DMA to device
- \begin{itemize}
- \item Need to make sure that all writes to DMA buffer are
- committed.
- \end{itemize}
- \item After DMA from device
- \begin{itemize}
- \item Before drivers read from DMA buffer, need to make sure
- that memory caches are flushed.
- \end{itemize}
- \item Bidirectional DMA
- \begin{itemize}
- \item Need to flush caches before and after the DMA transfer.
- \end{itemize}
+ \item Need to make sure that all writes to DMA buffer are
+ committed.
+ \end{itemize}
+ \item After DMA from device
+ \begin{itemize}
+ \item Before drivers read from DMA buffer, need to make sure
+ that memory caches are flushed.
+ \end{itemize}
+ \item Bidirectional DMA
+ \begin{itemize}
+ \item Need to flush caches before and after the DMA transfer.
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}
\frametitle{Linux DMA API}
+ The kernel DMA utilities can take care of:
\begin{itemize}
- \item The kernel DMA utilities can take care of:
- \begin{itemize}
- \item Either allocating a buffer in a cache coherent area,
- \item Or making sure caches are flushed when required,
- \item Managing the DMA mappings and IOMMU (if any).
- \item See \kerneldoc{DMA-API.txt} for details about the
- Linux DMA generic API.
- \item Most subsystems (such as PCI or USB) supply their own DMA
- API, derived from the generic one. May be sufficient for most
- needs.
- \end{itemize}
+ \item Either allocating a buffer in a cache coherent area,
+ \item Or making sure caches are flushed when required,
+ \item Managing the DMA mappings and IOMMU (if any).
+ \item See \kerneldoc{DMA-API.txt} for details about the
+ Linux DMA generic API.
+ \item Most subsystems (such as PCI or USB) supply their own DMA
+ API, derived from the generic one. May be sufficient for most
+ needs.
\end{itemize}
\end{frame}
@@ -131,9 +127,7 @@
\begin{frame}[fragile]
\frametitle{Allocating Coherent Mappings}
- \begin{itemize}
- \item The kernel takes care of both buffer allocation and mapping
- \end{itemize}
+ The kernel takes care of both buffer allocation and mapping
\begin{minted}[fontsize=\small]{c}
#include <asm/dma-mapping.h>
@@ -152,9 +146,7 @@ void dma_free_coherent(struct device *dev,
\begin{frame}[fragile]
\frametitle{Setting up streaming mappings}
- \begin{itemize}
- \item Works on buffers already allocated by the driver
- \end{itemize}
+ Works on buffers already allocated by the driver
\begin{minted}[fontsize=\small]{c}
#include <linux/dmapool.h>
@@ -224,7 +216,7 @@ void dma_unmap_single(struct device *dev, dma_addr_t handdle,
\end{enumerate}
\item Of course, this needs to be done in addition to the DMA
mapping seen previously
- \item Some framework abstract it away from you, such as \code{SPI}
+ \item Some frameworks abstract it away from you, such as \code{SPI}
and \code{ASoC}
\end{itemize}
\end{frame}
diff --git a/slides/kernel-driver-development-mmap/kernel-driver-development-mmap.tex b/slides/kernel-driver-development-mmap/kernel-driver-development-mmap.tex
index 15f3d0b..6f424eb 100644
--- a/slides/kernel-driver-development-mmap/kernel-driver-development-mmap.tex
+++ b/slides/kernel-driver-development-mmap/kernel-driver-development-mmap.tex
@@ -107,7 +107,7 @@ int remap_pfn_range(
\end{frame}
\begin{frame}[fragile]
- \frametitle{Simple mmap Implementation}
+ \frametitle{Simple mmap implementation}
\begin{minted}[fontsize=\small]{c}
static int acme_mmap
(struct file * file, struct vm_area_struct *vma)
More information about the training-materials-updates
mailing list