From: "Christian König" <christian.koenig@amd.com>
To: Zhenneng Li <lizhenneng@kylinos.cn>,
Alex Deucher <alexander.deucher@amd.com>
Cc: Xinhui.Pan@amd.com, David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: add mb for si
Date: Fri, 18 Nov 2022 09:01:44 +0100 [thread overview]
Message-ID: <ecd9d251-8941-b2db-71b2-e4ac06f860a3@amd.com> (raw)
In-Reply-To: <20221118074810.380368-1-lizhenneng@kylinos.cn>
Am 18.11.22 um 08:48 schrieb Zhenneng Li:
> During reboot test on arm64 platform, it may failure on boot,
> so add this mb in smc.
>
> The error message are as follows:
> [ 6.996395][ 7] [ T295] [drm:amdgpu_device_ip_late_init [amdgpu]] *ERROR*
> late_init of IP block <si_dpm> failed -22
> [ 7.006919][ 7] [ T295] amdgpu 0000:04:00.0: amdgpu_device_ip_late_init failed
> [ 7.014224][ 7] [ T295] amdgpu 0000:04:00.0: Fatal error during GPU init
Memory barries are not supposed to be sprinkled around like this, you
need to give a detailed explanation why this is necessary.
Regards,
Christian.
>
> Signed-off-by: Zhenneng Li <lizhenneng@kylinos.cn>
> ---
> drivers/gpu/drm/amd/pm/legacy-dpm/si_smc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/pm/legacy-dpm/si_smc.c b/drivers/gpu/drm/amd/pm/legacy-dpm/si_smc.c
> index 8f994ffa9cd1..c7656f22278d 100644
> --- a/drivers/gpu/drm/amd/pm/legacy-dpm/si_smc.c
> +++ b/drivers/gpu/drm/amd/pm/legacy-dpm/si_smc.c
> @@ -155,6 +155,8 @@ bool amdgpu_si_is_smc_running(struct amdgpu_device *adev)
> u32 rst = RREG32_SMC(SMC_SYSCON_RESET_CNTL);
> u32 clk = RREG32_SMC(SMC_SYSCON_CLOCK_CNTL_0);
>
> + mb();
> +
> if (!(rst & RST_REG) && !(clk & CK_DISABLE))
> return true;
>
next prev parent reply other threads:[~2022-11-18 8:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 7:48 [PATCH] drm/amdgpu: add mb for si Zhenneng Li
2022-11-18 8:01 ` Christian König [this message]
2022-11-18 9:18 ` Michel Dänzer
2022-11-18 9:24 ` 李真能
2022-11-24 10:04 ` Quan, Evan
2022-11-24 10:06 ` Christian König
2022-11-25 2:06 ` Quan, Evan
2022-11-24 10:41 ` Lazar, Lijo
2022-11-24 10:49 ` Lazar, Lijo
2022-11-25 2:13 ` Quan, Evan
2022-11-25 6:12 ` Lazar, Lijo
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-all 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=ecd9d251-8941-b2db-71b2-e4ac06f860a3@amd.com \
--to=christian.koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhenneng@kylinos.cn \
/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