[FE training-materials-updates] Corrections after previous commits (kernel interrupt slides)

Michael Opdenacker michael.opdenacker at free-electrons.com
Mon Dec 5 13:23:41 CET 2016

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=394f625ddb10816a24e41515a4d890817f2dd9c4


commit 394f625ddb10816a24e41515a4d890817f2dd9c4
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Mon Dec 5 13:23:41 2016 +0100

    Corrections after previous commits (kernel interrupt slides)
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


 .../kernel-driver-development-interrupts.tex                   | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex b/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex
index 707ca5d..766008e 100644
--- a/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex
+++ b/slides/kernel-driver-development-interrupts/kernel-driver-development-interrupts.tex
@@ -2,7 +2,7 @@
   \frametitle{Registering an interrupt handler 1/2}
-  When handling multiple devices, the {\em managed} API is preferred:
+  The {\em managed} API is recommended:
 int devm_request_irq(struct device *dev,
                      unsigned int irq,
@@ -123,9 +123,9 @@ Err:          0
   \item Return value
     \item \ksym{IRQ_HANDLED}: recognized and handled interrupt
-    \item \ksym{IRQ_NONE}: the interrupt was not triggered by a device
-     managed by this driver. Useful to share interrupt channels and/or
-     report spurious interrupts to the kernel.
+    \item \ksym{IRQ_NONE}: used by the kernel to detect spurious
+	interrupts, and disable the interrupt line if none of the
+	interrupt handlers has handled the interrupt.
@@ -226,7 +226,7 @@ int devm_request_threaded_irq(
     given tasklet is guaranteed to execute on a single CPU at a time.
   \item Tasklets are typically created with the \kfunc{tasklet_init}
     function, when your driver manages multiple devices, otherwise
-    statically with \kfunc{TASKLET_INIT}. A tasklet is simply
+    statically with \kfunc{DECLARE_TASKLET}. A tasklet is simply
     implemented as a function. Tasklets can easily
     be used by individual device drivers, as opposed to softirqs.
   \item The interrupt handler can schedule tasklet execution with:

More information about the training-materials-updates mailing list