All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Spencer Ku (古世瑜)" <Spencer.Ku@quantatw.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Question of Redfish PCIe
Date: Wed, 24 Mar 2021 08:45:19 +0000	[thread overview]
Message-ID: <HK0PR04MB3299350D35DE18CA5AA040CDE4639@HK0PR04MB3299.apcprd04.prod.outlook.com> (raw)

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

Hi All,
We are interested in how to get PCIe relative info via redfish, like PCIeDevice, PCIeSlot and so on.

In my opinion, package “peci-pcie” is used to collect the PCIe info and filled them into the PCIe D-bus, after that the bmcweb can get relative info through the D-bus.
Then I look into the gerrit’s active patches and find that the D-bus interface is changed, and here are some example:

Original interface implement by peci-pcie:
xyz.openbmc_project.PCIe.Device

Current interface used in the patches:
xyz.openbmc_project.Inventory.Item.PCIeDevice
xyz.openbmc_project.Inventory.Item.PCIeSlot

Does it means that peci-pcie will be updated to cover the D-bus changes or I need to add the D-bus by myself under the xyz.openbmc_project.Inventory.Item?
Just want to know the current status of redfish PCIe, thanks!

Sincerely,
Spencer Ku

[-- Attachment #2: Type: text/html, Size: 3835 bytes --]

             reply	other threads:[~2021-03-24  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  8:45 Spencer Ku (古世瑜) [this message]
2021-03-24 18:42 ` Question of Redfish PCIe Bills, Jason M
2021-03-25  8:50   ` Spencer Ku (古世瑜)

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=HK0PR04MB3299350D35DE18CA5AA040CDE4639@HK0PR04MB3299.apcprd04.prod.outlook.com \
    --to=spencer.ku@quantatw.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.