[FE training-materials-updates] kernel: i2c lab - backup commit

Michael Opdenacker michael.opdenacker at free-electrons.com
Sun Sep 29 16:20:10 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=4417adfa7297ed417dda7b2d0c4eac0ebad3b23d

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

commit 4417adfa7297ed417dda7b2d0c4eac0ebad3b23d
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Sun Sep 29 14:53:41 2013 +0200

    kernel: i2c lab - backup commit
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

4417adfa7297ed417dda7b2d0c4eac0ebad3b23d
 .../kernel-i2c-device-model.tex                    |   47 +++++++++++++++++++-
 1 file changed, 46 insertions(+), 1 deletion(-)

diff --git a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
index c1f586f..3735880 100644
--- a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
+++ b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
@@ -2,7 +2,7 @@
   and basic driver hooks called when this device is detected}
 
 Throughout the upcoming labs, we will implement a driver for an I2C
-device, which offers the functionality of an I2C nunchucks.
+device, which offers the functionality of an I2C nunchuks.
 
 After this lab, you will be able to:
 
@@ -12,3 +12,48 @@ After this lab, you will be able to:
 functions and make sure that they are called when such a device is added or removed.
 \end{itemize}
 
+\section{setup}
+
+Go to the \code{~/felabs/linux/src/linux} directory. Check out the
+\code{3.11.y-bbb} branch if needed. 
+
+Now create a new \code{nunchuk} branch starting from the
+\code{3.11.y-bbb} branch,  for your upcoming work on the nunchuk
+driver.  
+
+\section{Connecting the nunchuk}
+
+Take the nunchuk device provided by your instructor.
+
+Now let's identify the 4 pins of the nunchuk connector.
+
+\begin{itemize}
+\item The \code{ground} pin.
+\item The \code{power} pin.
+\item The \code{clock} pin.
+\item The \code{data} pin.
+\end{itemize}
+
+(TODO: give more details when we receive the final connectors)
+
+Open the System Reference Manual that you downloaded earlier,
+and look for "connector P9" in the table of contents, and then
+follow the link to the corresponding section. Look at the table listing
+the pinout of the P9 connector.
+
+Now connect the nunchuk pins:
+\begin{itemize}
+\item The \code{ground} pin to pins 1 or 2 (\code{GND})
+\item The \code{power} pin to pins 3 or 4 (\code{DC_3.3V})
+\item The \code{clock} pin to pin 17 (\code{I2C1_SCL})
+\item The \code{data} pin to pin 18 (\code{I2C1_SDA})
+\end{itemize}
+
+(TODO: add photos)
+
+\section{Update the board device tree}
+
+To let the Linux kernel handle a new device, the first thing is....
+
+
+



More information about the training-materials-updates mailing list