[bootlin/training-materials updates] master: labs/kernel-i2c-*: download the Nunchuk datasheet earlier (c2c96226)
Thomas Petazzoni
thomas.petazzoni at bootlin.com
Tue Oct 13 13:45:39 CEST 2020
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/c2c96226a74fdf78132ae6e61150ac00db661be8
>---------------------------------------------------------------
commit c2c96226a74fdf78132ae6e61150ac00db661be8
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date: Tue Oct 13 13:45:39 2020 +0200
labs/kernel-i2c-*: download the Nunchuk datasheet earlier
We make a reference to it in the "device model" lab... but only
instruct participants to download it in the following lab "i2c
communication", causing confusion.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
>---------------------------------------------------------------
c2c96226a74fdf78132ae6e61150ac00db661be8
labs/kernel-i2c-communication/kernel-i2c-communication.tex | 4 ----
labs/kernel-i2c-device-model/kernel-i2c-device-model.tex | 6 +++++-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/labs/kernel-i2c-communication/kernel-i2c-communication.tex b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
index b3345898..48883bba 100644
--- a/labs/kernel-i2c-communication/kernel-i2c-communication.tex
+++ b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
@@ -28,10 +28,6 @@ Take the nunchuk device provided by your instructor.
We will connect it to the second I2C port of the CPU (\code{i2c1}),
which pins are available on the \code{P9} connector.
-Download a useful document sharing useful details about the nunchuk
-and its connector:\\
-\url{https://bootlin.com/labs/doc/nunchuk.pdf}
-
Now we can identify the 4 pins of the nunchuk connector:
\begin{center}
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 5656b2fc..dcd56374 100644
--- a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
+++ b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
@@ -28,6 +28,10 @@ Nunchuk I2C device, but at this stage we won't need to connect
it yet, as we will enable I2C on the right board pins in the
next lab.
+Download a useful document sharing useful details about the nunchuk
+and its connector:\\
+\url{https://bootlin.com/labs/doc/nunchuk.pdf}
+
\section{Create a custom device tree}
To let the Linux kernel handle a new device, we need to add a
@@ -65,7 +69,7 @@ enough so far!
As a child node to the \code{i2c1} bus, now declare the \code{nunchuk}
device, choosing \code{nintendo,nunchuk} for its \code{compatible}
property. You will find the I2C slave address of the nunchuk on the
-nunckuk document that we have used earlier\footnote{This I2C slave
+nunckuk document that we have downloaded earlier\footnote{This I2C slave
addressed is enforced by the device itself. You can't change it.}.
\subsection{Checking the device tree on the running system}
More information about the training-materials-updates
mailing list