Discussion on GPIO monitoring and design thoughts.

[Andrew Jeffery]

On Thu, 2017-04-13 at 16:24 -0700, Kun Yi wrote:
> What about applications that need to monitor and set GPIOs rather than
> monitoring them only?

The proposed approach isn't great for that as we have the inconsistent
interfaces, but we do have functional debouncing. Ideally we would be
able to set GPIO pin configurations through the chardev interface, but
we can't do that (yet).

>  gpio-keys won't be suitable, and new cdev
> interface doesn't support writing to GPIOs yet.

Writing GPIOs through the chardev interface is supported as of v4.8-
rc1, so moving to 4.10 will enable it.

> Also could someone point me to 'libgpio' interfaces mentioned here?

From my conversations with Vishwa what he meant here was the chardev
interface, and there is no actual 'libgpio'.

Cheers,

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170418/86dfb036/attachment.sig>