From: James Feist <james.feist@linux.intel.com>
To: Patrick Venture <venture@google.com>
Cc: Kun Yi <kunyi@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
"Tanous, Ed" <ed.tanous@intel.com>
Subject: Re: entity-manager exposing eeproms
Date: Wed, 31 Jul 2019 09:33:55 -0700 [thread overview]
Message-ID: <401cb4b9-4f2b-0722-af80-106cf538fe37@linux.intel.com> (raw)
In-Reply-To: <CAO=notyvYn5-VTKys86NVzXXturPh=Q-5DFsR_ZvGeoJs=P0PQ@mail.gmail.com>
On 7/29/19 10:55 AM, Patrick Venture wrote:
> Hi;
>
> Sorry to flood with questions, but I'm hoping I won't be the only
> person asking and in the future, other machines starting to use
> entity-manager will find these useful.
>
> I've added the following configuration:
>
> cat configurations/semitruck.json
> {
> "Exposes": [
> {
> "Address": "0x50",
> "Bus": 14,
> "Name": "Aberdeen",
> "Type": "24C64"
> },
> {
> "Address": "0x50",
> "Bus": 15,
> "Name": "Energia",
> "Type": "24C64"
> }
> ],
> "Name": "Aberdeen Baseboard",
> "Probe" : "TRUE",
> "Type": "Board"
> }
>
> And I see:
> i2c i2c-14: new_device: Instantiated device 24c64 at 0x50
> i2c i2c-15: new_device: Instantiated device 24c64 at 0x50
>
> And I see:
> Service xyz.openbmc_project.EntityManager:
> `-/xyz
> `-/xyz/openbmc_project
> |-/xyz/openbmc_project/EntityManager
> `-/xyz/openbmc_project/inventory
> `-/xyz/openbmc_project/inventory/system
> `-/xyz/openbmc_project/inventory/system/board
> |-/xyz/openbmc_project/inventory/system/board/Aberdeen_Baseboard
>
> busctl introspect xyz.openbmc_project.EntityManager
> /xyz/openbmc_project/inventory/system/board/Aberdeen_Baseboard
> --no-pager
> NAME TYPE SIGNATURE
> RESULT/VALUE FLAGS
> org.freedesktop.DBus.Introspectable interface - -
> -
> .Introspect method - s
> -
> org.freedesktop.DBus.Peer interface - -
> -
> .GetMachineId method - s
> -
> .Ping method - -
> -
> org.freedesktop.DBus.Properties interface - -
> -
> .Get method ss v
> -
> .GetAll method s a{sv}
> -
> .Set method ssv -
> -
> .PropertiesChanged signal sa{sv}as -
> -
> xyz.openbmc_project.AddObject interface - -
> -
> .AddObject method a{sv} -
> -
> xyz.openbmc_project.Inventory.Item.Board interface - -
> -
> .Name property s "Aberdeen
> Baseboard" emits-change
> .Probe property s "TRUE"
> emits-change
> .Type property s "Board"
> emits-change
>
> For the two eeproms listed, neither are currently supported by
> FruDevice. It's my understanding that entity-manager "exposes"
> things, and I see it adding the eeproms successfully -- but then
> doesn't populate them to dbus. It populates a configuration space for
> the sensors, so I expected the same for eeproms.
FruDevice != Entity manager. They were kept completely separate, so the
fru device doesn't know anything about the Entity Manager. The Entity
Manager simply looks for any interface in it's probe statement to add
devices. In theory you could create a probe that looked like
xyz.openbmc_project.Sensor.Value('Value':'20'). Entity manager is adding
sysfs devices, and some happen to be eeproms.
>
> Am I missing something, or?
>
> Thanks,
> Patrick
>
next prev parent reply other threads:[~2019-07-31 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 17:55 entity-manager exposing eeproms Patrick Venture
2019-07-31 16:33 ` James Feist [this message]
2019-07-31 17:38 ` Patrick Venture
2019-07-31 17:42 ` Patrick Venture
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=401cb4b9-4f2b-0722-af80-106cf538fe37@linux.intel.com \
--to=james.feist@linux.intel.com \
--cc=ed.tanous@intel.com \
--cc=kunyi@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.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.