From: Andrew Jeffery <andrew@aj.id.au>
To: Andres Oportus <andresoportus@google.com>, openbmc@lists.ozlabs.org
Subject: Re: Question on States monitoring
Date: Tue, 15 May 2018 08:46:40 +0930 [thread overview]
Message-ID: <1526339800.3484892.1372056960.17AECCFA@webmail.messagingengine.com> (raw)
In-Reply-To: <CAD5O4R24451=iRYh5M_Bokhj8wMAzPdGfj5XSzhU6CJ6cOqotA@mail.gmail.com>
Hi Andres,
On Tue, 15 May 2018, at 01:16, Andres Oportus wrote:
> Are there any ongoing efforts on expanding States (say provided by GPIOs)
> monitoring/management? I see that phosphor-state-manager has
> Chassis/Host/BMC states that are placed onto DBUS but not a more generic
> mechanism. On the GPIO specific side, I see that phosphor-gpio-monitor
> allows for interrupt driven GPIO monitoring (seemly only used under a
> gpio-keys driver with /dev/input for Power's checkstop monitoring?), but no
> generic GPIO setting/getting for those not allowing interrupt type
> monitoring (say output GPIOs).
It's not clear to me what you're looking for here. Are you hoping for something to expose the GPIOs on DBus? I don't think we have anything like that, which is more of a design philosophy thing (we should probably provide a higher-level capability on DBus, not just directly expose GPIOs).
Alternatively if you're looking to handle GPIOs from your application, I would recommend libgpiod:
https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/
Cheers,
Andrew
next prev parent reply other threads:[~2018-05-14 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 15:46 Question on States monitoring Andres Oportus
2018-05-14 23:16 ` Andrew Jeffery [this message]
2018-05-14 23:26 ` Andres Oportus
2018-05-15 1:49 ` Lei YU
2018-05-15 1:53 ` Andrew Jeffery
2018-05-15 1:57 ` Lei YU
2018-05-15 5:05 ` Andres Oportus
2018-05-15 12:32 ` Lei YU
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1526339800.3484892.1372056960.17AECCFA@webmail.messagingengine.com \
--to=andrew@aj.id.au \
--cc=andresoportus@google.com \
--cc=openbmc@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.