[bootlin/training-materials updates] master: Kernel labs: add Elixir links (686544c7)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/686544c705f826f493758652f48c98bbb4d0a1ae

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

commit 686544c705f826f493758652f48c98bbb4d0a1ae
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Wed Feb 10 09:20:48 2021 +0100

    Kernel labs: add Elixir links
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

686544c705f826f493758652f48c98bbb4d0a1ae
 labs/kernel-serial-interrupt/kernel-serial-interrupt.tex | 6 +++---
 labs/kernel-serial-iomem/kernel-serial-iomem.tex         | 8 ++++----
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
index e6225884..131b2248 100644
--- a/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
+++ b/labs/kernel-serial-interrupt/kernel-serial-interrupt.tex
@@ -51,12 +51,12 @@ Then, pass the interrupt number to \kfunc{devm_request_irq} along
 with the interrupt handler to register your interrupt in the kernel.
 
 Then, in the interrupt handler, just print a message and return
-\code{IRQ_HANDLED} (to tell the kernel that we have handled the
+\ksym{IRQ_HANDLED} (to tell the kernel that we have handled the
 interrupt).
 
 You'll also need to enable interrupts.
 To do so, in the \code{probe()} function, write
-\code{UART_IER_RDI} to the \code{UART_IER} register.
+\ksym{UART_IER_RDI} to the \ksym{UART_IER} register.
 
 Compile and load your module. Send a character on the serial link (just
 type something in the corresponding \code{picocom} terminal, and
@@ -74,7 +74,7 @@ experienced here is called an \code{interrupt flood}.
 
 Now, in our interrupt handler, we want to acknowledge the
 interrupt. On the UART controllers that we drive, it's done simply by
-reading the contents of the \code{UART_RX} register, which holds the
+reading the contents of the \ksym{UART_RX} register, which holds the
 next character received. You can display the value you read to see
 that the driver will receive whatever character you sent.
 
diff --git a/labs/kernel-serial-iomem/kernel-serial-iomem.tex b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
index 1a80df56..9f768879 100644
--- a/labs/kernel-serial-iomem/kernel-serial-iomem.tex
+++ b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
@@ -60,7 +60,7 @@ Then, declare the corresponding devices:
 
 This is a good example of how we can override definitions in the Device
 Tree. \code{uart2} and \code{uart4} are already defined in
-\code{arch/arm/boot/dts/am33xx.dtsi}. In the above code, we just
+\kfile{arch/arm/boot/dts/am33xx.dtsi}. In the above code, we just
 override a few properties and add missing ones:
 duplicate the valid ones:
 
@@ -239,11 +239,11 @@ structure and one character as parameters, and writing
 this character to the serial port, using the following steps:
 
 \begin{enumerate}
-\item Wait until the \code{UART_LSR_THRE} bit gets set in the
-  \code{UART_LSR} register.  You can busy-wait for this condition to happen.
+\item Wait until the \ksym{UART_LSR_THRE} bit gets set in the
+  \ksym{UART_LSR} register.  You can busy-wait for this condition to happen.
   In the busy-wait loop, you can call the \kfunc{cpu_relax} kernel function
   to ensure the compiler won't optimise away this loop.
-\item Write the character to the \code{UART_TX} register.
+\item Write the character to the \ksym{UART_TX} register.
 \end{enumerate}
 
 Add a call to this routine from your module \code{probe()} function,