public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: wangxiao.bj@inspur.com
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"tigerliu@zhaoxin.com" <tigerliu@zhaoxin.com>
Subject: 答复: [edk2-devel] question about PCI bridge's bus range window configure's save and restore
Date: Mon, 10 Aug 2020 11:54:51 +0000	[thread overview]
Message-ID: <0f1b74aaf0774f25bfd76d476a05b598@inspur.com> (raw)
In-Reply-To: <ca75900e3b974104874bf10194c30dde@zhaoxin.com>

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

It’s done by BIOS pei s3 resume code.  Restored register value saved  while BIOS normal POST BY BootScriptExecutor.  You can refer  gEfiPeiS3Resume2Ppi  usage

Thanks

发件人: devel@edk2.groups.io [mailto:devel@edk2.groups.io] 代表 Tiger Liu(BJ-RD)
发送时间: 2020年8月10日 17:32
收件人: devel@edk2.groups.io
主题: [edk2-devel] question about PCI bridge's bus range window configure's save and restore



Hi, Experts:

I have a question about PCI Bridge’s config space’s save and restore.



Pci bus driver configured PCI Bridges’ secondary bus number register and subordinate bus number register.



So, if system resumes from S3(Suspend to ram) state, who is responsible for restoring PCI Bridges’ secondary bus number / subordinate bus number registers’ content?



Will the OS be responsible for it?



Thanks





保密声明:

本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。

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: 8482 bytes --]

  reply	other threads:[~2020-08-10 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-10  9:31 [edk2-devel] question about PCI bridge's bus range window configure's save and restore Tiger Liu(BJ-RD)
2020-08-10 11:54 ` wangxiao.bj [this message]
2020-08-10 21:32   ` 答复: " Laszlo Ersek
2020-08-11  2:09     ` Feng Libo

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=0f1b74aaf0774f25bfd76d476a05b598@inspur.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