From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: [edk2-devel] [edk2platforms][PATCH v1 1/1] IntelSiliconPkg: Add IntelDieInfoProtocol
To: Chaganty, Rangasai V <rangasai.v.chaganty@intel.com>,devel@edk2.groups.io
From: "Maciej Czajkowski" <maciej.czajkowski@intel.com>
X-Originating-Location: Leixlip, Leinster, IE (192.198.151.52)
X-Originating-Platform: Windows Chrome 94
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Fri, 15 Oct 2021 04:27:51 -0700
References: <MW3PR11MB4602A2EA295C30EAEE3B67CBB6B89@MW3PR11MB4602.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4602A2EA295C30EAEE3B67CBB6B89@MW3PR11MB4602.namprd11.prod.outlook.com>
Message-ID: <7192.1634297271578856469@groups.io>
Content-Type: multipart/alternative; boundary="fKV22J6pAa3emprlPfs6"

--fKV22J6pAa3emprlPfs6
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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 gene=
ration and Die specific ID in a single UINT64?
Yes, in order to have a generic field regardless of the die type and per-ge=
neration changes it will be packed into a single UINT64. Protocol will be i=
nstalled by silicon code, and consumer will need to be aware of the encodin=
g 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

--fKV22J6pAa3emprlPfs6
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div><em>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 encodin=
g of generation and Die specific ID in a single UINT64?</em></div>
<div>Yes, in order to have a generic field regardless of the die type and p=
er-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 en=
coding and decode it. Same applies for stepping id.</div>
<div>&nbsp;</div>
<div><em>Any reason the die specific GUIDs are not declared in the .dec fil=
e?</em></div>
<div>I can't see any problems with that, they will be added in v2 changes.<=
br /><br />Regards,<br />Maciej</div>

--fKV22J6pAa3emprlPfs6--