From: "Maciej Czajkowski" <maciej.czajkowski@intel.com>
To: Chaganty,
Rangasai V <rangasai.v.chaganty@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [edk2platforms][PATCH v1 1/1] IntelSiliconPkg: Add IntelDieInfoProtocol
Date: Fri, 15 Oct 2021 04:27:51 -0700 [thread overview]
Message-ID: <7192.1634297271578856469@groups.io> (raw)
In-Reply-To: <MW3PR11MB4602A2EA295C30EAEE3B67CBB6B89@MW3PR11MB4602.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
Can you add some details on how a producer of this interface would know the values to be assigned here? Does this contain any sort of encoding of generation and Die specific ID in a single UINT64?
Yes, in order to have a generic field regardless of the die type and per-generation changes it will be packed into a single UINT64. Protocol will be installed by silicon code, and consumer will need to be aware of the encoding and decode it. Same applies for stepping id.
Any reason the die specific GUIDs are not declared in the .dec file?
I can't see any problems with that, they will be added in v2 changes.
Regards,
Maciej
[-- Attachment #2: Type: text/html, Size: 725 bytes --]
prev parent reply other threads:[~2021-10-15 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 15:24 [edk2platforms][PATCH v1 0/1] IntelSiliconPkg: Add IntelDieInfoProtocol maciej.czajkowski
2021-10-07 15:24 ` [edk2platforms][PATCH v1 1/1] " Maciej Czajkowski
2021-10-14 6:26 ` Ni, Ray
2021-10-15 11:21 ` [edk2-devel] " Maciej Czajkowski
2021-10-14 6:52 ` Chaganty, Rangasai V
2021-10-15 11:27 ` Maciej Czajkowski [this message]
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=7192.1634297271578856469@groups.io \
--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