Extending phosphor-gpio-monitor to expose gpio objects on dbus

Andrew Jeffery andrew at aj.id.au
Mon Jul 18 10:36:29 AEST 2022

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:



More information about the openbmc mailing list