All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: "openbmc\@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Extending phosphor-gpio-monitor to expose gpio objects on dbus
Date: Mon, 18 Jul 2022 06:10:49 -0400	[thread overview]
Message-ID: <1234822.1658139049@dooku> (raw)
In-Reply-To: <YtPrcDzaxXiM6vYJ@heinlein.stwcx.org.github.beta.tailscale.net>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]


Patrick Williams <patrick@stwcx.xyz> wrote:
    > 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.

So, clearly some developers think that they need this :-)

I read:
   https://gerrit.openbmc.org/c/openbmc/docs/+/55422

and this is good, but is little too abstract to be useful I think.

I would like to suggest three things.
1) link to some situations where this has been proposed, and then a smarter
resolution via another method might be good.  Is there a link to the
host-power on code as a clear commit?

2) I wonder about situations where developers are trying to get access to
some kind of debug info into the field, and that's why they look this.  That
is, there isn't a way to wrap it up into something abstract, because the
point is to allow for deeper examination.

3) maybe link to situations where dbus has failed to be fast enough.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2022-07-18 10:17 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
2022-07-18 10:10   ` Michael Richardson [this message]
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=1234822.1658139049@dooku \
    --to=mcr@sandelman.ca \
    --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.