| | 43 | |
| | 44 | == GPIO Ownership |
| | 45 | |
| | 46 | There are some GPIO that Gateworks as defined as 'user' GPIO that can be used freely by the user. There are usually quantity two of these on a IO header somewhere on the SBC. However, there are many other GPIO in use on the board, some of which are owned by the system and not easily toggled by the user. |
| | 47 | |
| | 48 | Users may find that certain GPIO pins on the Gateworks SBC cannot be toggled directly from userspace via gpioset or sysfs. This is by design within the Linux Kernel architecture. |
| | 49 | |
| | 50 | When a GPIO is defined in the Device Tree and assigned to a specific kernel-level driver (such as those managing status LEDs, reset lines, or power regulators), the kernel reserves that pin to ensure system stability. Attempting to claim these pins from userspace will result in a Resource Busy error. To manipulate these functions, users should interact with the appropriate kernel subsystem API. |
| | 51 | |
| | 52 | To see different GPIOs in the device tree, see [wiki:linux/devicetree] |