From: Lei YU <mine260309@gmail.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Andres Oportus <andresoportus@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Question on States monitoring
Date: Tue, 15 May 2018 09:57:57 +0800 [thread overview]
Message-ID: <CAARXrtkc86rh2WDbK9nAnfY0PPJS2BpSeQSJTLFf3Ccxzc3edQ@mail.gmail.com> (raw)
In-Reply-To: <1526349203.3522551.1372178312.7B38A3F9@webmail.messagingengine.com>
On Tue, May 15, 2018 at 9:53 AM, Andrew Jeffery <andrew@aj.id.au> wrote:
> Hi Lei,
>
> On Tue, 15 May 2018, at 11:19, Lei YU wrote:
>> Hi Andres,
>>
>> The existing [phosphor-gpio-monitor][1] contains two services, one is for
>> monitor gpio interrupts, the other is "phosphor-gpio-presence" that checks a
>> gpio output and let it be some state on DBus.
>>
>> I guess the "presence" service is what you are looking for, that maps a
>> gpio output to a Dbus object.
>>
>> The existing use case is:
>> 1. Witherspoon checks if power supply is connected and create dbus object
>> /inventory/system/chassis/motherboard/powersupplyX, it also is able to
>> bind the kernel driver when it is attached.
>> 2. Zaius checks if a PCIE card is connected on E2B and create dbus object
>> /inventory/system/chassis/pcie_card_e2b
>>
>> You can see a little detailed explanation at
>> https://github.com/mine260309/openbmc-intro/blob/master/Porting_Guide.md#gpio-presence
>
> That porting guide looks like it has some interesting info, and I feel like we should probably make it part of the docs repository. Did you have any plans on integrating it?
Yup, I will submit to openbmc/doc (when it's somehow ready).
This doc is my attempt to help system vendors to know OpenBMC and get it
ported on their machine.
And for now I have sent this to 2 or 3 vendors and ask for feedback.
It's not completed yet as I need to add one more page for some development
tips, e.g. how to quickly modify a code and get it tested.
>
> Cheers,
>
> Andrew
next prev parent reply other threads:[~2018-05-15 1:57 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
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 [this message]
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=CAARXrtkc86rh2WDbK9nAnfY0PPJS2BpSeQSJTLFf3Ccxzc3edQ@mail.gmail.com \
--to=mine260309@gmail.com \
--cc=andresoportus@google.com \
--cc=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.