On 12/2/2021 11:48 AM, Quan, Evan wrote:
[AMD Official Use Only]
-Original Message-
From: Lazar, Lijo
Sent: Thursday, December 2, 2021 1:12 PM
To: Quan, Evan ; amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Koenig, Christian
; Feng, Kenneth
Subject: Re: [PATCH V3 01/17]
[AMD Official Use Only]
> -Original Message-
> From: Lazar, Lijo
> Sent: Thursday, December 2, 2021 1:12 PM
> To: Quan, Evan ; amd-gfx@lists.freedesktop.org
> Cc: Deucher, Alexander ; Koenig, Christian
> ; Feng, Kenneth
> Subject: Re: [PATCH V3 01/17] drm/amd/pm: do not expose
On 12/2/2021 10:22 AM, Quan, Evan wrote:
[AMD Official Use Only]
-Original Message-
From: Lazar, Lijo
Sent: Thursday, December 2, 2021 12:13 PM
To: Quan, Evan ; amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Koenig, Christian
; Feng, Kenneth
Subject: Re: [PATCH V3 01/17]
[AMD Official Use Only]
> -Original Message-
> From: Lazar, Lijo
> Sent: Thursday, December 2, 2021 12:13 PM
> To: Quan, Evan ; amd-gfx@lists.freedesktop.org
> Cc: Deucher, Alexander ; Koenig, Christian
> ; Feng, Kenneth
> Subject: Re: [PATCH V3 01/17] drm/amd/pm: do not expose
On 12/2/2021 8:39 AM, Evan Quan wrote:
Those implementation details(whether swsmu supported, some ppt_funcs supported,
accessing internal statistics ...)should be kept internally. It's not a good
practice and even error prone to expose implementation details.
Signed-off-by: Evan Quan
Those implementation details(whether swsmu supported, some ppt_funcs supported,
accessing internal statistics ...)should be kept internally. It's not a good
practice and even error prone to expose implementation details.
Signed-off-by: Evan Quan
Change-Id:
