public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"tigerliu@zhaoxin.com" <tigerliu@zhaoxin.com>
Subject: Re: [edk2-devel] [edk2] Smbuslib and SmbusPpi
Date: Mon, 4 Nov 2019 03:30:55 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E536C38@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <564b09666ef142cd86e0fb605ea2c52b@zhaoxin.com>

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

SmbusPpi is defined in PI spec. SmbusLib is defined in Edk2 MdePkg.

Edk2 PEIM can base on SmBusLib. SmBusLib implementation wraps SmBusPpi.

Thanks
Liming
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Tiger Liu(BJ-RD)
Sent: Thursday, October 31, 2019 6:51 PM
To: devel@edk2.groups.io; Gao, Liming <liming.gao@intel.com>
Subject: [edk2-devel] [edk2] Smbuslib and SmbusPpi

Hi, Liming:
I have a question about smbus access during pei phase.

I found there was not smbus ppi reference implementation in edk2-platform code base.
And there was a SmbusLib reference implementation lib.

So, PEIMs usually use functions provided by SmbusLib?
Not use PeiSmbusPpi’s interface functions?

Thanks

Best wishes,

保密声明:
本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.


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

  reply	other threads:[~2019-11-04  3:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 10:51 [edk2-devel] [edk2] Smbuslib and SmbusPpi Tiger Liu(BJ-RD)
2019-11-04  3:30 ` Liming Gao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-04  5:03 Tiger Liu(BJ-RD)
2019-11-04  5:09 ` Liming Gao
2019-11-04  6:10 Tiger Liu(BJ-RD)

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-list 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E536C38@SHSMSX104.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox