From: Patrick Venture <venture@google.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
tomjoseph@in.ibm.com,
Vernon Mauery <vernon.mauery@linux.intel.com>,
Emily Shaffer <emilyshaffer@google.com>,
James Feist <james.feist@linux.intel.com>,
"Tanous, Ed" <ed.tanous@intel.com>,
Ofer Yehielli <ofery@google.com>, Kun Yi <kunyi@google.com>
Subject: phosphor-host-ipmid sensor SDRs on dbus
Date: Tue, 23 Jul 2019 13:40:20 -0700 [thread overview]
Message-ID: <CAO=notwC5_-wVBOONXrO9R0eoR0MDOjmt1ZAc_J9XJvvXd-G7g@mail.gmail.com> (raw)
I sent out an email indicating that we need to make sensors somewhat
dynamic in phosphor-host-ipmid, and either using json or dbus was a
reasonable approach. I think json would be easier, but, for those
using entity-manager, perhaps having the SDR information supported in
some way associated with the dbus output might be useful.
Idea: Given a sensor, read the SDR from dbus.
Problem: association of a sensor id with a sensor on dbus -- maybe
some search step is run once that caches everything and listens for
change (similar to what James did with phosphor-pid-control)...
I'm just throwing out ideas without full design changes because I want
to get a sense of where the preferences lie before really digging into
what changes are required.
It would support both types (like dbus configuration in phosphor-pid-control).
Patrick
next reply other threads:[~2019-07-23 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 20:40 Patrick Venture [this message]
2019-07-23 21:48 ` phosphor-host-ipmid sensor SDRs on dbus James Feist
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='CAO=notwC5_-wVBOONXrO9R0eoR0MDOjmt1ZAc_J9XJvvXd-G7g@mail.gmail.com' \
--to=venture@google.com \
--cc=ed.tanous@intel.com \
--cc=emilyshaffer@google.com \
--cc=james.feist@linux.intel.com \
--cc=kunyi@google.com \
--cc=ofery@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tomjoseph@in.ibm.com \
--cc=vernon.mauery@linux.intel.com \
/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.