Skip to content

Most visited

Recently visited




public interface GpioDriver
implements Gpio

GPIO user driver. A GpioDriver must implement all Gpio functions, but additionally this class provides an open() function that will be called whenever a process obtains ownership of the GPIO, to match the existing close() function.


Inherited constants

From interface

Public methods

abstract void close()

Closes the GPIO pin.

default String getName()

Returns null.

abstract void open()

Opens the GPIO pin.

abstract void registerGpioCallback(GpioCallback callback, Handler handler)

Registers a callback for GPIO edge interrupts.

abstract void unregisterGpioCallback(GpioCallback callback)

Unregisters an interrupt callback.

Inherited methods

From interface
From interface
From interface java.lang.AutoCloseable

Public methods


void close ()

Closes the GPIO pin. This will be called when the GPIO is closed by its owner. Any resources that need to be cleaned up should be done so here. This method may throw IOException to indicate I/O failure, but the GPIO will still be considered closed and may attempt to be re-opened in the future.

IOException on I/O failure; the driver will still be considered closed.


String getName ()

Returns null. I/O user drivers can be registered under any name so this returns null by default. Child classes may override this if other behavior is desired.



void open ()

Opens the GPIO pin. This will be called when ownership of a GPIO is obtained. The driver should do any initialization needed to configure the GPIO pin for use here.

IOException on I/O failure; the driver will remain closed.


void registerGpioCallback (GpioCallback callback, 
                Handler handler)

Registers a callback for GPIO edge interrupts. This API is shared with a standard Gpio, but for a GpioDriver some simplifying assumptions can be made:

  • Only one GpioCallback will ever be registered at a time.
  • The Gpio argument to the GpioCallback methods are not needed, so any value (or null) may be provided when making callbacks.
  • The return value from onGpioEdge(Gpio) will always be true and can be safely ignored.
  • The driver is allowed but not required to post callbacks on the provided Handler.
  • Currently the error value passed to onGpioError(Gpio, int) is ignored and OsConstants.ENODEV is always used instead.
Example: Shared GPIO interrupt line
This is common with I2C-to-GPIO expanders, where a bank of GPIOs will share one common interrupt line. The idea is that the GpioDriver receives the common interrupt signal, figures out which of the expander's GPIOs it actually came from, and then dispatch the interrupt to that particular GpioDriver.
 // Implements a single GPIO on the expander.
 public class SharedInterruptGpioDriver implements GpioDriver {
     // The underlying GPIO shared between the whole GPIO bank.
     private Gpio mInterruptGpio;

     // Our callback implementation to handle shared GPIO interrupts.
     private SharedGpioCallback mSharedCallback;

     public void registerGpioCallback(GpioCallback callback, Handler handler)
             throws IOException {
         mSharedCallback = new SharedGpioCallback(callback);
         mInterruptGpio.registerGpioCallback(mSharedCallback, handler);

     public void unregisterGpioCallback(GpioCallback callback) {
         mSharedCallback = null;

     // Intercept the shared GPIO callback and if it was meant for us, dispatch to the
     // user-facing callback.
     private class SharedGpioCallback implements GpioCallback {
         // The callback registers on this GPIO driver that we dispatch events to.
         private final GpioCallback mRegisteredCallback;

         public SharedGpioCallback(GpioCallback registeredCallback) {
             mRegisteredCallback = registeredCallback;

         public boolean onGpioEdge(Gpio gpio) {
             // Do any checking necessary to determine if this is the GPIO that fired.
             // This is for example purposes only and may be inefficient since each GPIO
             // checks the interrupt - better would be a single interrupt handler which
             // dispatches to the proper GPIO driver.
             if (thisGpioHadInterrupt()) {
                 return mRegisteredCallback.onGpioEdge(gpio);

             // If it wasn't meant for this GPIO, do nothing and return true to keep
             // listening for events.
             return true;

         public void onGpioError(Gpio gpio, int error) {
             // The underlying interrupt GPIO failed, we won't get any more callbacks.
             mRegisteredCallback.onGpioError(gpio, error);

callback GpioCallback: GpioCallback to register; only one will ever be registered at a time.
handler Handler: Handler to optionally run callbacks on. Provided as a convenience if needed, but it's not required to execute callbacks on this.
IOException if this GPIO doesn't support interrupts.


void unregisterGpioCallback (GpioCallback callback)

Unregisters an interrupt callback. Will only be called if a GpioCallback has been previously registered.

callback GpioCallback: GpioCallback to unregister.

See also:

This site uses cookies to store your preferences for site-specific language and display options.

Get the latest Android developer news and tips that will help you find success on Google Play.

* Required Fields


Follow Google Developers on WeChat

Browse this site in ?

You requested a page in , but your language preference for this site is .

Would you like to change your language preference and browse this site in ? If you want to change your language preference later, use the language menu at the bottom of each page.

This class requires API level or higher

This doc is hidden because your selected API level for the documentation is . You can change the documentation API level with the selector above the left navigation.

For more information about specifying the API level your app requires, read Supporting Different Platform Versions.

Take a short survey?
Help us improve the Android developer experience. (Dec 2017 Android Platform & Tools Survey)