From: "chunhui.jia" <chunhui.jia@linux.intel.com>
To: "Patrick Williams" <patrick@stwcx.xyz>,
"Supreeth Venkatesh" <supreeth.venkatesh@amd.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Re: Progress Codes in BMC
Date: Mon, 25 Jan 2021 10:24:25 +0800 [thread overview]
Message-ID: <600E2BD6.8060408@linux.intel.com> (raw)
In-Reply-To: <YArmnhlS33TpVo63@heinlein>
[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]
Patrick, Deepak,
Current post code is stored as 64bits although data from HW is 8bits. It should be enough to host. With said, we don't need to extend as it is already 64bits.
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/State/Boot/Raw.interface.yaml#L6
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/State/Boot/PostCode.interface.yaml#L45
2021-01-25
chunhui.jia
发件人:Patrick Williams <patrick@stwcx.xyz>
发送时间:2021-01-22 22:52
主题:Re: Progress Codes in BMC
收件人:"Supreeth Venkatesh"<supreeth.venkatesh@amd.com>
抄送:"openbmc"<openbmc@lists.ozlabs.org>
On Fri, Jan 22, 2021 at 08:18:29AM -0600, Supreeth Venkatesh wrote:
> On 1/22/21 6:32 AM, Deepak Kodihalli wrote:
> > On Fri, Jan 22, 2021 at 5:25 PM manoj kiran <manojkiran.eda@gmail.com> wrote:
> > Maybe some of the apps I pointed above can be extended for this
> > purpose, but I'm yet to take a closer look.
> One of the deviations on AMD platforms is that POST code is usually 32 bit code.
> I did extend phosphor-host-postd to read 32 bit codes and added experimental associated driver in Linux, as LPC ports supported is only two.
> However, it is far from production quality code at this point. We can definitely collaborate on this to arrive at a generic solution.
I was also going to point to the postcode daemons as a good starting
point. On Intel platforms, the postcodes are typically 1 byte. The
previous postcode daemon got its data from the LPC "port 80" mechanism,
but Facebook/HCL recently extended it to support multi-host and to be
able to consume postcodes from an IPMB end-point (which is how we talk
to our per-host microcontroller).
I think it should be fairly straight-forward to add a new mechanism to
pick up data from PLDM or whatever your path is on Power. The daemons
in question here already support keeping a history as well. I think the
only think you'd need to do is extend it to be 32-bit or 64-bit progress
codes instead of just 8-bit, but I see no reason why that shouldn't be
acceptable. It sounds like Supreeth might even have some code as a
starting point?
(Supreeth maybe you can throw up anything you've done to the postcode
daemons into Gerrit as a starting point?)
--
Patrick Williams
[-- Attachment #2: Type: text/html, Size: 6087 bytes --]
next prev parent reply other threads:[~2021-01-25 2:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 11:53 Progress Codes in BMC manoj kiran
2021-01-22 12:32 ` Deepak Kodihalli
2021-01-22 14:18 ` Supreeth Venkatesh
2021-01-22 14:52 ` Patrick Williams
2021-01-25 2:24 ` chunhui.jia [this message]
2021-01-25 5:29 ` Venkatesh, Supreeth
2021-01-26 4:05 ` chunhui.jia
2021-01-28 1:05 ` Brad Bishop
2021-01-30 14:31 ` Patrick Williams
2021-02-02 0:21 ` Brad Bishop
2021-02-02 0:49 ` Ed Tanous
2021-02-02 1:08 ` Brad Bishop
2021-02-02 1:44 ` Ed Tanous
2021-02-02 2:45 ` Patrick Williams
2021-02-04 8:47 ` manoj kiran
2021-02-04 9:34 ` Deepak Kodihalli
2021-02-04 10:22 ` manoj kiran
2021-02-04 12:17 ` Deepak Kodihalli
2021-01-28 18:03 ` Benjamin Fair
2021-01-28 18:17 ` Supreeth Venkatesh
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=600E2BD6.8060408@linux.intel.com \
--to=chunhui.jia@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--cc=supreeth.venkatesh@amd.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.