[bootlin/training-materials updates] master: labs/sysdev-thirdparty-beagleplay: improve libgpiod instructions (91c36ad3)

Michael Opdenacker michael.opdenacker at bootlin.com
Mon Aug 7 16:25:55 CEST 2023


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

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

commit 91c36ad325ea85d5d1825000972e8e9115e18f6d
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Aug 7 15:19:34 2023 +0200

    labs/sysdev-thirdparty-beagleplay: improve libgpiod instructions
    
    - The logic of identifying gpiochip2 was unclear
    - Remove a legacy mention of "GPIOE", which is for another board.
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

91c36ad325ea85d5d1825000972e8e9115e18f6d
 .../sysdev-thirdparty-beagleplay.tex                             | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex b/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex
index 113d1b91..bf9e5f1a 100644
--- a/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex
+++ b/labs/sysdev-thirdparty-beagleplay/sysdev-thirdparty-beagleplay.tex
@@ -693,12 +693,9 @@ gpiochip2 [601000.gpio] (52 lines)
 \end{bashinput}
 
 But how can we know which gpiochip is actually driving our \code{INT} gpio ?
-To do so, different methods can be used. We can look at the device tree of the
-BeaglePlay and see that the controller driving the \code{GPIO1_9} pin has 52 I/O.
-Therefore we can assume that the controller is the \code{gpiochip2}.
-
-We can then get details on GPIOE GPIOs by running \code{gpioinfo
-gpiochip2} or on all GPIOs by simply running \code{gpioinfo}.
+The easiest way to do this in our case is to run the \code{gpioinfo}
+command and look for \code{GPIO1_9} in its output. That's how you'll
+find that \code{GPIO1_9} is line \code{9} on \code{gpiochip2}.
 
 You can now read the state of \code{GPIO1_9}:
 




More information about the training-materials-updates mailing list