From: "Christian König" <christian.koenig@amd.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Alex Deucher <alexander.deucher@amd.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Xuefeng Li <lixuefeng@loongson.cn>,
Jianmin Lv <lvjianmin@loongson.cn>
Subject: Re: [PATCH] drm/radeon: Always call radeon_suspend_kms() in radeon_pci_shutdown()
Date: Mon, 7 Jun 2021 14:30:13 +0200 [thread overview]
Message-ID: <0d1b517f-797f-e87d-4edd-8474b16993ed@amd.com> (raw)
In-Reply-To: <1623068820-2479-1-git-send-email-yangtiezhu@loongson.cn>
Am 07.06.21 um 14:27 schrieb Tiezhu Yang:
> radeon_suspend_kms() puts the hw in the suspend state (all asics),
> it should always call radeon_suspend_kms() in radeon_pci_shutdown(),
> this is a normal cleanup process to avoid more operations on radeon,
> just remove #ifdef CONFIG_PPC64 and the related comments.
Well NAK.
Alex knows more about the details but suspending should not be part of
the pci shotdown process at all.
We just add that here to enforce a GPU reset on PPC64 boards for some
reason.
Regards,
Christian.
>
> Co-developed-by: Jianmin Lv <lvjianmin@loongson.cn>
> Signed-off-by: Jianmin Lv <lvjianmin@loongson.cn>
> Signed-off-by: Tiezhu Yang <yangtiezhu@loongson.cn>
> ---
> drivers/gpu/drm/radeon/radeon_drv.c | 9 ---------
> 1 file changed, 9 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_drv.c b/drivers/gpu/drm/radeon/radeon_drv.c
> index efeb115..0b1f43d 100644
> --- a/drivers/gpu/drm/radeon/radeon_drv.c
> +++ b/drivers/gpu/drm/radeon/radeon_drv.c
> @@ -386,16 +386,7 @@ radeon_pci_shutdown(struct pci_dev *pdev)
> if (radeon_device_is_virtual())
> radeon_pci_remove(pdev);
>
> -#ifdef CONFIG_PPC64
> - /*
> - * Some adapters need to be suspended before a
> - * shutdown occurs in order to prevent an error
> - * during kexec.
> - * Make this power specific becauase it breaks
> - * some non-power boards.
> - */
> radeon_suspend_kms(pci_get_drvdata(pdev), true, true, false);
> -#endif
> }
>
> static int radeon_pmops_suspend(struct device *dev)
next prev parent reply other threads:[~2021-06-07 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 12:27 Tiezhu Yang
2021-06-07 12:30 ` Christian König [this message]
2021-06-07 13:42 ` Alex Deucher
2021-06-08 2:24 ` Tiezhu Yang
2021-06-08 14:54 ` Alex Deucher
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=0d1b517f-797f-e87d-4edd-8474b16993ed@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@linux.ie \
--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=lixuefeng@loongson.cn \
--cc=lvjianmin@loongson.cn \
--cc=yangtiezhu@loongson.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
all inboxes | Powered by JetHome®