GPIO Centralized Control Daemon

[Andrew Jeffery]

On Sat, 2017-09-16 at 21:22 -0700, Patrick Venture wrote:
> > > From a high level, the daemon will implement interfaces to export
> > or
> > > unexport GPIOs.  Each GPIO exported will exist on the dbus:
> > >
> > > /xyz/openbmc_project/gpio/53 and implement an interface with the
> > > following properties:
> > > value, direction, active_low, etc.
> > 
> > Just thinking out loud...are we sure a gpio is a useful
> > abstraction?
> > If applications all just use the chardev API what is the benefit of
> > having a dbus object, at the cost of API complexity.
> 
> As an alternative, perhaps a library would suffice.  My goal is to
> avoid multiple in-application implementations.  However, I felt it
> might be helpful to have some centralized daemon serving this
> information -- a simple dbus property access may be simpler than
> either implementing the ioctl in each application.  However, a
> library may also provide the necessary abstraction.
>  

If we do need a library, there's this:

    https://github.com/brgl/libgpiod

We should try to make use of that before doing something ourselves.

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/20170918/2e0fee5f/attachment.sig>