[FE training-materials-updates] kernel slides: rework chapter hierarchy

Michael Opdenacker michael.opdenacker at free-electrons.com
Sun Sep 29 17:18:50 CEST 2013

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

On branch  : kernel-ng
Link       : http://git.free-electrons.com/training-materials/commit/?id=69701196b52d9d641c4da44ae6ce87d1f74b6707


commit 69701196b52d9d641c4da44ae6ce87d1f74b6707
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Sun Sep 29 17:17:04 2013 +0200

    kernel slides: rework chapter hierarchy
    - Fixing the assignment of chapters and subchapters.
      Otherwise, the "kernel frameworks" section has an
      "Introduction to pin muxing" title
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


 slides/kernel-device-model/kernel-device-model.tex |    2 +-
 slides/kernel-i2c/kernel-i2c.tex                   |    2 +-
 .../kernel-misc-subsystem.tex                      |    2 +-
 slides/kernel-pinmuxing/kernel-pinmuxing.tex       |   10 +++++-----
 .../kernel-porting-title/kernel-porting-title.tex  |    2 +-
 .../kernel-power-management-title.tex              |    2 +-
 6 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/slides/kernel-device-model/kernel-device-model.tex b/slides/kernel-device-model/kernel-device-model.tex
index 48b42be..003ec12 100644
--- a/slides/kernel-device-model/kernel-device-model.tex
+++ b/slides/kernel-device-model/kernel-device-model.tex
@@ -1,4 +1,4 @@
-\section{Linux device and driver model}
+\subsection{Linux device and driver model}
 \begin{frame}{The need for a device model?}
diff --git a/slides/kernel-i2c/kernel-i2c.tex b/slides/kernel-i2c/kernel-i2c.tex
index 84d96a1..26f253c 100644
--- a/slides/kernel-i2c/kernel-i2c.tex
+++ b/slides/kernel-i2c/kernel-i2c.tex
@@ -1,4 +1,4 @@
-\section{Introduction to the I2C subsystem}
+\subsection{Introduction to the I2C subsystem}
 \begin{frame}{What is I2C?}
diff --git a/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex b/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
index c2c05a3..5d8e456 100644
--- a/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
+++ b/slides/kernel-misc-subsystem/kernel-misc-subsystem.tex
@@ -1,4 +1,4 @@
-\section{The misc subsystem}
+\subsection{The misc subsystem}
 \begin{frame}{Why a {\em misc} subsystem?}
diff --git a/slides/kernel-pinmuxing/kernel-pinmuxing.tex b/slides/kernel-pinmuxing/kernel-pinmuxing.tex
index c63e4e7..43f42b3 100644
--- a/slides/kernel-pinmuxing/kernel-pinmuxing.tex
+++ b/slides/kernel-pinmuxing/kernel-pinmuxing.tex
@@ -1,8 +1,8 @@
-\section{Introduction to pin muxing}
+\subsection{Introduction to pin muxing}
 \begin{frame}{What is pin muxing?}
-  \item The modern System-on-chip include more and more hardware
+  \item Modern SoCs (System on Chip) include more and more hardware
     blocks, many of which need to interface with the outside world
     using {\em pins}.
   \item However, the physical size of the chips remains small, and
@@ -10,7 +10,7 @@
   \item For this reason, not all of the internal hardware block
     features can be exposed on the pins simultaneously.
   \item The pins are {\bf multiplexed}: they expose either the
-    functionality of an hardware block A {\bf or} the functionality of
+    functionality of hardware block A {\bf or} the functionality of
     hardware block B.
   \item This {\em multiplexing} is usually software configurable.
@@ -35,7 +35,7 @@
   \item Most {\em pinctrl} drivers provide a Device Tree binding, and
     the pin muxing must be described in the Device Tree.
-    \item The exact Device Tree binding depends for each driver. Each
+    \item The exact Device Tree binding depends on each driver. Each
       binding is documented in
@@ -87,7 +87,7 @@ i2c at 11000 {
       that are board specific.
   \item The \code{pinctrl-<x>} property of the consumer device points,
-    through a DT {\em phandle} to the pin configuration it needs.
+    to the pin configuration it needs through a DT {\em phandle}.
   \item The description of the configurations is specific to each {\em
       pinctrl driver}. See
     \code{Documentation/devicetree/bindings/pinctrl} for the DT
diff --git a/slides/kernel-porting-title/kernel-porting-title.tex b/slides/kernel-porting-title/kernel-porting-title.tex
index 43fc126..6ffada4 100644
--- a/slides/kernel-porting-title/kernel-porting-title.tex
+++ b/slides/kernel-porting-title/kernel-porting-title.tex
@@ -1 +1 @@
-\section{Porting the Linux Kernel to an ARM Board}
+\subsection{Porting the Linux Kernel to an ARM Board}
diff --git a/slides/kernel-power-management-title/kernel-power-management-title.tex b/slides/kernel-power-management-title/kernel-power-management-title.tex
index ee19448..8218aac 100644
--- a/slides/kernel-power-management-title/kernel-power-management-title.tex
+++ b/slides/kernel-power-management-title/kernel-power-management-title.tex
@@ -1 +1 @@
-\section{Power Management}
+\subsection{Power Management}

More information about the training-materials-updates mailing list