All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adriana Kobylak <anoo@linux.ibm.com>
To: Emily Shaffer <emilyshaffer@google.com>
Cc: James Feist <james.feist@linux.intel.com>, openbmc@lists.ozlabs.org
Subject: Re: Read-Only IPMI sensors
Date: Tue, 14 Aug 2018 09:14:26 -0500	[thread overview]
Message-ID: <14bcd1ed07cdff6e5cc2fb2c49852a81@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJoAoZnnt8qfH0H81phTZQdgwFM5KOZQjrrV6dQprWrD3-VgrQ@mail.gmail.com>

On 2018-08-13 19:03, Emily Shaffer wrote:
> host-ipmid also already supports read-only, in fact, adding writable
> support was a pretty big work item last year. When you say data-driven
> design do you mean the automatic discovery? I guess I'm a little
> confused as to what exactly is missing for you.
> 

Yeah, by data-driven I mean the 
phosphor-ipmi-sensor-inventory%/config.yaml files in the openbmc repo 
where a sensor is matched to a D-Bus object. For example if we create a 
property under the Settings D-Bus object for the derating factor sensor, 
and add this object to the ipmi config.yaml file, a Set Sensor would be 
able to change its value, unless the host-ipmid read-only support 
prevents this. What is the read-only support in ipmi?

> On Mon, Aug 13, 2018 at 11:32 AM James Feist
> <james.feist@linux.intel.com> wrote:
> 
>> sdbusplus-asio already has support for read-only properties that
>> you
>> might be interested in using / duplicating:
>> 
> https://github.com/openbmc/sdbusplus/blob/master/sdbusplus/asio/object_server.hpp#L123
>> [2]
>> 

Thanks, will take a look, since we want read-only properties in 
sdbusplus regardless if they'll be used by ipmi.

      reply	other threads:[~2018-08-14 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 18:33 Read-Only IPMI sensors Adriana Kobylak
2018-08-13 18:31 ` James Feist
2018-08-14  0:03   ` Emily Shaffer
2018-08-14 14:14     ` Adriana Kobylak [this message]

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=14bcd1ed07cdff6e5cc2fb2c49852a81@linux.vnet.ibm.com \
    --to=anoo@linux.ibm.com \
    --cc=emilyshaffer@google.com \
    --cc=james.feist@linux.intel.com \
    --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.