[AMD Public Use]

Patch3: Acked-by: Feifei Xu <[email protected]>

Regards,
Feifei

From: amd-gfx <[email protected]> On Behalf Of Xu, Feifei
Sent: 2020年3月6日 9:54
To: Deucher, Alexander <[email protected]>; Alex Deucher 
<[email protected]>; amd-gfx list <[email protected]>
Cc: Tawfik, Aly <[email protected]>
Subject: RE: [PATCH 1/2] drm/amdgpu/display: fix pci revision id fetching


[AMD Public Use]

Patch1, Patch2 are :


Reviewed-by: Feifei Xu <[email protected]<mailto:[email protected]>>


From: Deucher, Alexander 
<[email protected]<mailto:[email protected]>>
Sent: 2020年3月6日 0:00
To: Xu, Feifei <[email protected]<mailto:[email protected]>>; Alex Deucher 
<[email protected]<mailto:[email protected]>>; amd-gfx list 
<[email protected]<mailto:[email protected]>>
Cc: Tawfik, Aly <[email protected]<mailto:[email protected]>>
Subject: Re: [PATCH 1/2] drm/amdgpu/display: fix pci revision id fetching


[AMD Public Use]

Is this for the series, or just this patch?  Thanks!

Alex
________________________________
From: Xu, Feifei <[email protected]<mailto:[email protected]>>
Sent: Thursday, March 5, 2020 12:24 AM
To: Alex Deucher <[email protected]<mailto:[email protected]>>; amd-gfx 
list <[email protected]<mailto:[email protected]>>
Cc: Deucher, Alexander 
<[email protected]<mailto:[email protected]>>; Tawfik, Aly 
<[email protected]<mailto:[email protected]>>
Subject: RE: [PATCH 1/2] drm/amdgpu/display: fix pci revision id fetching

[AMD Official Use Only - Internal Distribution Only]



Reviewed-by: Feifei Xu <[email protected]<mailto:[email protected]>>

-----Original Message-----
From: amd-gfx 
<[email protected]<mailto:[email protected]>>
 On Behalf Of Alex Deucher
Sent: 2020年3月5日 13:23
To: amd-gfx list 
<[email protected]<mailto:[email protected]>>
Cc: Deucher, Alexander 
<[email protected]<mailto:[email protected]>>; Tawfik, Aly 
<[email protected]<mailto:[email protected]>>
Subject: Re: [PATCH 1/2] drm/amdgpu/display: fix pci revision id fetching

Ping?

On Tue, Feb 25, 2020 at 3:32 PM Alex Deucher 
<[email protected]<mailto:[email protected]>> wrote:
>
> From: Aly-Tawfik <[email protected]<mailto:[email protected]>>
>
> Use the pci revision id rather than the asic silicon revision id.
>
> Signed-off-by: Aly-Tawfik <[email protected]<mailto:[email protected]>>
> Signed-off-by: Alex Deucher 
> <[email protected]<mailto:[email protected]>>
> ---
>  drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c 
> b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index 0c55d44c9d5b..92166150bf9f 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -902,7 +902,7 @@ static int amdgpu_dm_init(struct amdgpu_device *adev)
>
>         init_data.asic_id.chip_family = adev->family;
>
> -       init_data.asic_id.pci_revision_id = adev->rev_id;
> +       init_data.asic_id.pci_revision_id = adev->pdev->revision;
>         init_data.asic_id.hw_internal_rev = adev->external_rev_id;
>
>         init_data.asic_id.vram_width = adev->gmc.vram_width;
> --
> 2.24.1
>
_______________________________________________
amd-gfx mailing list
[email protected]<mailto:[email protected]>
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&amp;data=02%7C01%7CFeifei.Xu%40amd.com%7Cdd49232261ac4267a33f08d7c0c54ad8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637189825908683804&amp;sdata=sN%2BGSvrmnz5Qdrf4JR0sFUDWMWyu7tsOh6ZG9lb9I5Y%3D&amp;reserved=0<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Famd-gfx&data=02%7C01%7CFeifei.Xu%40amd.com%7Cdd57c60d9a094f71f0cd08d7c1713880%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637190564935585723&sdata=N79NoA72vZ9zZRYsS92VIY0foejZG6igq57bbx7DIsI%3D&reserved=0>
_______________________________________________
amd-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

Reply via email to