Thanks Evan, I will add "{ }" before I check-in the code.
Best,
Jack
-Original Message-
From: Quan, Evan
Sent: Tuesday, December 3, 2019 10:45 AM
To: Zhang, Jack (Jian) ; amd-gfx@lists.freedesktop.org
Cc: Zhang, Jack (Jian)
Subject: RE: [PATCH] amd/amdgpu/sriov swSMU disable
> -Original Message-
> From: amd-gfx On Behalf Of Jack
> Zhang
> Sent: Monday, December 2, 2019 7:05 PM
> To: amd-gfx@lists.freedesktop.org
> Cc: Zhang, Jack (Jian)
> Subject: [PATCH] amd/amdgpu/sriov swSMU disable for sriov
>
> For boards greater tha
@lists.freedesktop.org
Cc: Zhang, Jack (Jian)
Subject: [PATCH] amd/amdgpu/sriov swSMU disable for sriov
For boards greater than ARCTURUS, and under sriov platform,
swSMU is not supported because smu ip block is commented at
guest driver.
Generally for sriov, initialization of smu is moved to host
Hi, Team,
Would you please help to review this patch?
Best,
Jack
-Original Message-
From: Jack Zhang
Sent: Monday, December 2, 2019 7:05 PM
To: amd-gfx@lists.freedesktop.org
Cc: Zhang, Jack (Jian)
Subject: [PATCH] amd/amdgpu/sriov swSMU disable for sriov
For boards greater than
For boards greater than ARCTURUS, and under sriov platform,
swSMU is not supported because smu ip block is commented at
guest driver.
Generally for sriov, initialization of smu is moved to host driver.
Thus, smu sw_init and hw_init will not be executed at guest driver.
Without sw structure being
