From: "Andrew Jeffery" <andrew@aj.id.au>
To: openbmc@lists.ozlabs.org
Subject: Re: Extending phosphor-gpio-monitor to expose gpio objects on dbus
Date: Mon, 18 Jul 2022 10:06:29 +0930 [thread overview]
Message-ID: <f7fe06ea-0c13-4047-8efa-e30aa6c377ad@www.fastmail.com> (raw)
In-Reply-To: <YtPrcDzaxXiM6vYJ@heinlein.stwcx.org.github.beta.tailscale.net>
On Sun, 17 Jul 2022, at 20:28, Patrick Williams wrote:
> On Thu, Jul 14, 2022 at 09:52:57PM +0000, Arvind Nandanahosur Ramesh wrote:
>> Hi Everyone,
>
> Hello Arvind,
>
>> We have been toying with the idea of extending the phosphor-gpio-monitor to expose the the gpio objects it manages on dbus in addition to its current functionality of executing a specified systemd target. This additional functionality can be enabled by an additional parameter in the phosphor-multi-gpio-monitor.json file. Before going down the path of implementing this and upstreaming the changes, I wanted to get a sense on if this is a good or a bad idea. Essentially this would be useful for other services to query the current GPIO value of input signals over dbus or react to changes in its value. What did you all think ?
>
> I'd say about every 6 months someone proposes a change to
> phosphor-dbus-interface with the addition of a "Generic GPIO interface"
> and it has always been rejected. This has gotten to be so regular that
> I should probably try to track them down in a list so the discussions
> there can be easily referred to.
I did a bit of digging and pushed this:
https://gerrit.openbmc.org/c/openbmc/docs/+/55422
Andrew
next prev parent reply other threads:[~2022-07-18 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 21:52 Extending phosphor-gpio-monitor to expose gpio objects on dbus Arvind Nandanahosur Ramesh
2022-07-17 10:58 ` Patrick Williams
2022-07-18 0:36 ` Andrew Jeffery [this message]
2022-07-18 10:10 ` Michael Richardson
2022-07-18 23:29 ` Andrew Jeffery
2022-07-20 3:40 ` Andrew Jeffery
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=f7fe06ea-0c13-4047-8efa-e30aa6c377ad@www.fastmail.com \
--to=andrew@aj.id.au \
--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.