On the AM335X, writes to the padconf registers must be done in privileged
mode. To allow userspace drivers to dynamically change the padconf at
runtime, a kernel call has been added.
Change-Id: I4b25d2879399b1785a360912faa0e90b5c258533
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
General Purpose Input and Output
To make MINIX more usable on embedded hardware we need some way to access the
GPIO features of the system on chip’s. Generally System on Chips (SoC) designs
provide some way configure pads to perform basic Input/Output configuration on
selected ports. These ports are also usually grouped into a bank. The end
result is that you have a functional general input output block where you need
to configure some the following functions.
Functional requirements
We envision that the short term usage of the GPIO library will be booth input
and output handling. Input handling as we want to be able to listen to button
presses and genrate key events and output handling because we want to be able
to control leds.
GPIO required functionality
-Configure pins as input or output.
-Configure the impedance of the pins.
-Get or set the values of the pins(possibly in a single call).
-Configure interrupt levels for input pins.
Configure debouncing of pins.
Additional kernel requirements
-Manage the GPIO resources (who may access what)
-Access the GPIO pins from within driver (for the keyboard)
-Access the GPIO pins from within userland (for toggeling leds)
Usage:
You have to manualy mount the gpio fs using the following command
# mount -t gpio none /gpio
4593804bf0