public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Benjamin Doron" <benjamin.doron00@gmail.com>
To: devel@edk2.groups.io
Cc: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
	 Michael Kubacki <Michael.Kubacki@microsoft.com>
Subject: Re: GSoC 2022: Add S3 resume support to MinPlatform
Date: Tue, 5 Apr 2022 14:14:13 -0400	[thread overview]
Message-ID: <CAONYkK_3XZu_t6Ovm06=zm2aHMRGnheSDzRHK0duJDyTQrvXbQ@mail.gmail.com> (raw)
In-Reply-To: <CAONYkK9daNGMqTypAk8xa08zpMJkNjMc9jnQqUFa2AvbB570bA@mail.gmail.com>

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

Hi,
I'm looking for feedback on a proposal for a large project. I intend to
implement S3 resume for MinPlatform (medium project) and develop closed
chassis debug over an HDMI cable as an additional project to assist the
bringup work. Commonly, serial ports in laptops are either difficult to
access or missing entirely. As Nate has previously addressed (
https://github.com/nate-desimone/Bus_Pirate#closed-chassis-debug-over-hdmi),
HDMI's DDC pins offer a connection to an I2C controller available early in
the boot process, making it a good candidate as early, accessible debug
port.

On Intel chipsets, the GMBUS implements the I2C controller. It has
registers inside the iGFX MMIO and is documented in Intel's iGFX PRMs. I
plan to use the register definitions and the documentation of EDID access,
along with the I2C specification, to develop this project.

Would this make for a good project proposal? I'd appreciate any feedback.
Thanks.

Best regards,
Benjamin


On Tue, 22 Mar 2022 at 17:14, Benjamin Doron <benjamin.doron00@gmail.com>
wrote:

> Hi all,
> I'm Benjamin Doron. Last year, I worked on a board port to MinPlatform.
> This year, I hope to pick up where I left off and help improve MinPlatform
> by adding support for S3 resume (time permitting and if my skills are
> sufficient, etc). Previously, I worked a little on coreboot (mainly a board
> port), and a fork with some improvements for UefiPayloadPkg.
>
> I'm a little apprehensive reading the task proposal, but I really don't
> think that I would have to design the S3 architecture; the easiest part is
> adding the module stack. It's some of the deviations from the regular
> boot-flow in related areas like memory and CPU init (complicated by
> preparing the data structures and the adjacent FSP) that I have to worry
> about, as I understand (which I began looking at last year and discussed
> with Nate and Michael).
>
> Before, code analysis gave me some hints and I found issues to address,
> but I want to consider actual possibilities for debugging. I've looked at
> the S3 boot-flow and from early PEI to the S3Resume2 PPI, the boot script
> and SMM, there are a lot of things to verify. Analysing code at each step
> to resolve issues might take a while. Some ideas I had:
>
>    - Realistically, the SPI flash console or an accessible serial port.
>    - Simics, or other simulator/emulator: Would be helpful, if the
>    architecture of SimicsOpenBoardPkg weren't so different from MinPlatform.
>    - System debug with DCI: Would be great, but my laptop has
>    disconnected CPU<->PCH JTAG pins. Fixing this would presumably be very
>    risky. (I now also have a Tigerlake system, where DCI might work, but I
>    haven't tried and I don't have a port yet.)
>
> I should mention that I'll almost certainly be taking at least one course,
> but no more than two.
>
> Looking forward to working with you all!
>
> Best regards,
> Benjamin
>

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

  reply	other threads:[~2022-04-05 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 21:14 GSoC 2022: Add S3 resume support to MinPlatform Benjamin Doron
2022-04-05 18:14 ` Benjamin Doron [this message]
2022-04-07 21:46   ` [edk2-devel] " Nate DeSimone
2022-04-08 18:33     ` Benjamin Doron
2022-04-14  0:49       ` Nate DeSimone

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='CAONYkK_3XZu_t6Ovm06=zm2aHMRGnheSDzRHK0duJDyTQrvXbQ@mail.gmail.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