Changes between Version 35 and Version 36 of gpio


Ignore:
Timestamp:
02/16/2024 10:57:57 PM (5 months ago)
Author:
Ryan Erbstoesser
Comment:

add chart and subtitle

Legend:

Unmodified
Added
Removed
Modified
  • gpio

    v35 v36  
    8383   - GSC_GPIO_P0![0-7]: gpio240-gpio247
    8484   - GSC_GPIO_P1![0-7]: gpio247-gpio255
    85   - additional i2c based GPIO port-expanders present on some boards would begin at gpio116
     85  - Additional i2c based GPIO port-expanders present on some boards would begin at gpio116
    8686
    8787Note that the Linux gpio mapping is not guaranteed to remain constant across kernel versions. Care should be taken to consult {{{/sys/kernel/debug/gpio}}} and {{{/sys/class/gpio}}} when changing kernel versions.
     88
     89''' Hardware to Linux Software Conversion '''
    8890
    8991When referring to [http://www.gateworks.com/usermanuals Gateworks board user hardware manuals] you will need to translate the hardware pin name to a gpio using the information above. Some examples:
     
    9193 * Ventana GPIO![1]:DIO16 is GPIO block 1 IO 16 thus maps to gpio0 + 16 (or 0*32+16) = gpio-16
    9294 * Ventana GPIO![2]:DIO9 is GPIO block 2 IO 9 thus maps to gpio32 + 9 (or 1*32+9) = gpio-41
    93  * Equation: Ventana GPIO<x>__IO<y> is GPIO block x IO y thus maps to: gpio-((x-1)*32)+y
     95 * Equation: Venice GPIO<x>__IO<y> is GPIO block x IO y thus maps to: gpio-((x-1)*32)+y
     96 * Example chart:
     97  * [[Image(gpio.png,300px')]]
    9498
    9599