public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "PierreGondois" <pierre.gondois@arm.com>
To: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: devel@edk2.groups.io, Sami Mujawar <sami.mujawar@arm.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] [PATCH v2 01/11] ArmPkg/ArmScmiDxe: Rename PERFORMANCE_PROTOCOL_VERSION
Date: Fri, 10 Nov 2023 10:11:36 +0100	[thread overview]
Message-ID: <d2b790c3-6da0-413f-aef0-8cf3a179eb7c@arm.com> (raw)
In-Reply-To: <ab68952b-0bf1-4248-be9c-12f671a0ffd2@arm.com>

Hello Leif,

On 11/2/23 11:20, Pierre Gondois wrote:
> Hello Leif,
> Thanks for the review,
> 
> On 10/26/23 12:05, Leif Lindholm wrote:
>> On Wed, Oct 25, 2023 at 13:25:30 +0200, pierre.gondois@arm.com wrote:
>>> From: Pierre Gondois <pierre.gondois@arm.com>
>>>
>>> Rename PERFORMANCE_PROTOCOL_VERSION to reflect the different
>>> versions of the protocol. The macro is neither used in edk2 nor
>>> in edk2-platforms.
>>
>> OK, so slight nitpick, but mainly because it parses a bit weirdly...
>> *Will* it be used after this series is merged, or is this an update
>> for completeness?
> 
> The 'fast channels' were added in the v2.0 SCMI specification. This patch-set
> relies on this feature, so it is checked in:
>      [PATCH v2 10/11] DynamicTablesPkg: Add ArmScmiInfoLib
> that the underlying SCP is at least at this version.
> 
> ```
>      // FastChannels were added in SCMI v2.0 spec.
>      if (Version < PERFORMANCE_PROTOCOL_VERSION_V2) {
>        DEBUG ((DEBUG_ERROR, "ArmScmiInfoLib requires SCMI version > 2.0\n"));
>        return EFI_UNSUPPORTED;
>      }
> ```
> 
>>
>>> Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
>>> ---
>>>    ArmPkg/Include/Library/ArmLib.h                     |  1 +
>>>    .../Include/Protocol/ArmScmiPerformanceProtocol.h   | 13 ++++++++-----
>>>    2 files changed, 9 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/ArmPkg/Include/Library/ArmLib.h b/ArmPkg/Include/Library/ArmLib.h
>>> index 0169dbc1092c..7b2b2238fed9 100644
>>> --- a/ArmPkg/Include/Library/ArmLib.h
>>> +++ b/ArmPkg/Include/Library/ArmLib.h
>>> @@ -780,6 +780,7 @@ EFIAPI
>>>    ArmHasVhe (
>>>      VOID
>>>      );
>>> +
>>>    #endif // MDE_CPU_AARCH64
>>>    
>>>    #ifdef MDE_CPU_ARM
>>> diff --git a/ArmPkg/Include/Protocol/ArmScmiPerformanceProtocol.h b/ArmPkg/Include/Protocol/ArmScmiPerformanceProtocol.h
>>> index 7e548e4765c2..8e8e05d5a5f6 100644
>>> --- a/ArmPkg/Include/Protocol/ArmScmiPerformanceProtocol.h
>>> +++ b/ArmPkg/Include/Protocol/ArmScmiPerformanceProtocol.h
>>> @@ -1,12 +1,12 @@
>>>    /** @file
>>>    
>>> -  Copyright (c) 2017-2021, Arm Limited. All rights reserved.
>>> +  Copyright (c) 2017-2023, Arm Limited. All rights reserved.
>>>    
>>>      SPDX-License-Identifier: BSD-2-Clause-Patent
>>>    
>>> -  System Control and Management Interface V1.0
>>> -    http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/
>>> -    DEN0056A_System_Control_and_Management_Interface.pdf
>>> +  System Control and Management Interface, latest version:
>>
>> I see this as a pattern throughout the series.
>> But this statement will at some point become untrue; this
>> implementation is written against a specific version. I think this
>> version shold be reflected in the comment. (And that applies
>> throughout the series.)
>>
>>> +  - https://developer.arm.com/documentation/den0056/latest/
>>
>> But I think the above is the most useful link.

I was referring to this point I'm not sure I understood.

Regards,
Pierre

> 
> I am not sure I understand completely. Do you mean that the SCMI
> structures/interfaces defined in:
>      ArmPkg/Include/Protocol/ArmScmiPerformanceProtocol.h
> and that were written against the SCMI v1.0 specification should
> not be used as such for other SCMI specification version ?
> I.e. the same process as for the AcpiXX.h files
> (MdePkg/Include/IndustryStandard/Acpi65.h) should be used ?
> 
> Or do you mean that the _CPC object generation implies that the
> SCP should comply to the v2.0 version at least and this should be
> reflected in the commit messages ?
> 
> Regards,
> Pierre
> 
>>
>> /
>>       Leif
>>
>>> +
>>>    **/
>>>    
>>>    #ifndef ARM_SCMI_PERFORMANCE_PROTOCOL_H_
>>> @@ -14,7 +14,10 @@
>>>    
>>>    #include <Protocol/ArmScmi.h>
>>>    
>>> -#define PERFORMANCE_PROTOCOL_VERSION  0x10000
>>> +/// Arm Scmi performance protocol versions.
>>> +#define PERFORMANCE_PROTOCOL_VERSION_V1  0x10000
>>> +#define PERFORMANCE_PROTOCOL_VERSION_V2  0x20000
>>> +#define PERFORMANCE_PROTOCOL_VERSION_V3  0x30000
>>>    
>>>    #define ARM_SCMI_PERFORMANCE_PROTOCOL_GUID  { \
>>>      0x9b8ba84, 0x3dd3, 0x49a6, {0xa0, 0x5a, 0x31, 0x34, 0xa5, 0xf0, 0x7b, 0xad} \
>>> -- 
>>> 2.25.1
>>>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111025): https://edk2.groups.io/g/devel/message/111025
Mute This Topic: https://groups.io/mt/102175810/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2023-11-10  9:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 11:25 [edk2-devel] [PATCH v2 00/11] DynamicTablesPkg: Enable _PSD/_CPC generation using SCMI PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 01/11] ArmPkg/ArmScmiDxe: Rename PERFORMANCE_PROTOCOL_VERSION PierreGondois
2023-10-26 10:05   ` Leif Lindholm
2023-11-02 10:20     ` PierreGondois
2023-11-10  9:11       ` PierreGondois [this message]
2023-11-10 15:25         ` Leif Lindholm
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 02/11] ArmPkg/ArmScmiDxe: Add PERFORMANCE_DESCRIBE_FASTCHANNEL support PierreGondois
2023-10-26 10:37   ` Leif Lindholm
2023-11-02 10:19     ` PierreGondois
2023-11-02 13:32       ` Leif Lindholm
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 03/11] MdePkg/Acpi64: Add _PSD/_CPC/State Coordination Types macros PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 04/11] DynamicTablesPkg: Use new CPC revision macro PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 05/11] DynamicTablesPkg: Rename AmlCpcInfo.h to AcpiObjects.h PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 06/11] DynamicTablesPkg: Add CM_ARM_PSD_INFO object PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 07/11] DynamicTablesPkg: Add PsdToken field to CM_ARM_GICC_INFO object PierreGondois
2023-10-26 10:45   ` Leif Lindholm
2023-11-02 10:20     ` PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 08/11] DynamicTablesPkg: Add AmlCreatePsdNode() to generate _PSD PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 09/11] DynamicTablesPkg: Generate _PSD in SsdtCpuTopologyGenerator PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 10/11] DynamicTablesPkg: Add ArmScmiInfoLib PierreGondois
2023-10-26 11:03   ` Leif Lindholm
2023-11-02 10:20     ` PierreGondois
2023-11-09  9:58       ` PierreGondois
2023-11-09 11:26         ` Leif Lindholm
2023-11-10  9:11           ` PierreGondois
2023-10-25 11:25 ` [edk2-devel] [PATCH v2 11/11] DynamicTablesPkg: Remove check for _CPC field PierreGondois
2023-10-26 11:05   ` Leif Lindholm
2023-11-02 10:20     ` PierreGondois

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=d2b790c3-6da0-413f-aef0-8cf3a179eb7c@arm.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