From: Greg KH <gregkh@linuxfoundation.org>
To: Zhu Wang <wangzhu9@huawei.com>
Cc: harry.wentland@amd.com, sunpeng.li@amd.com,
Rodrigo.Siqueira@amd.com, alexander.deucher@amd.com,
christian.koenig@amd.com, airlied@linux.ie, daniel@ffwll.ch,
qingqing.zhuo@amd.com, stylon.wang@amd.com, Josip.Pavic@amd.com,
trix@redhat.com, cruise.hung@amd.com, Eric.Yang2@amd.com,
mario.limonciello@amd.com, alvin.lee2@amd.com, jun.lei@amd.com,
austin.zheng@amd.com, sunglee@amd.com, paul.hsieh@amd.com,
hanghong.ma@amd.com, JinZe.Xu@amd.com, lewis.huang@amd.com,
zhengzengkai@huawei.com, alex.hung@amd.com, syed.hassan@amd.com,
wayne.lin@amd.com, nicholas.kazlauskas@amd.com,
chiahsuan.chung@amd.com, aurabindo.pillai@amd.com,
aric.cyr@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6.6] drm/amd/display: Wake DMCUB before executing GPINT commands
Date: Tue, 16 Apr 2024 06:54:23 +0200 [thread overview]
Message-ID: <2024041658-imagines-unlatch-a9b6@gregkh> (raw)
In-Reply-To: <20240416035240.2450127-1-wangzhu9@huawei.com>
On Tue, Apr 16, 2024 at 03:52:40AM +0000, Zhu Wang wrote:
> From: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
>
> stable inclusion
> from stable-v6.7.3
> commit 2ef98c6d753a744e333b7e34b9cf687040fba57d
> category: bugfix
> bugzilla: https://gitee.com/src-openeuler/kernel/issues/I9BV4C
> CVE: CVE-2023-52624
>
> Reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2ef98c6d753a744e333b7e34b9cf687040fba57d
>
> --------------------------------
>
> [ Upstream commit e5ffd1263dd5b44929c676171802e7b6af483f21 ]
>
> [Why]
> DMCUB can be in idle when we attempt to interface with the HW through
> the GPINT mailbox resulting in a system hang.
>
> [How]
> Add dc_wake_and_execute_gpint() to wrap the wake, execute, sleep
> sequence.
>
> If the GPINT executes successfully then DMCUB will be put back into
> sleep after the optional response is returned.
>
> It functions similar to the inbox command interface.
>
> Cc: Mario Limonciello <mario.limonciello@amd.com>
> Cc: Alex Deucher <alexander.deucher@amd.com>
> Cc: stable@vger.kernel.org
> Reviewed-by: Hansen Dsouza <hansen.dsouza@amd.com>
> Acked-by: Wayne Lin <wayne.lin@amd.com>
> Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>
> This commit comes from following commits:
>
> 8774029f76b9 ("drm/amd/display: Add DCN35 CLK_MGR")
> 65138eb72e1f ("drm/amd/display: Add DCN35 DMUB")
> dc01c4b79bfe ("drm/amd/display: Update driver and IPS interop")
> 820c3870c491 ("drm/amd/display: Refactor DMCUB enter/exit idle interface")
> 2ef98c6d753a ("drm/amd/display: Wake DMCUB before executing GPINT commands")
Why are you putting multiple commits together and not just submitting
the individual ones? And what is this for?
confused,
greg k-h
next prev parent reply other threads:[~2024-04-16 4:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 3:52 Zhu Wang
2024-04-16 4:54 ` Greg KH [this message]
2024-04-18 1:51 ` 答复: " wangzhu
2024-04-18 1:58 ` Alex Deucher
2024-04-18 3:14 ` 答复: " wangzhu
2024-04-18 14:15 ` Alex Deucher
2024-04-18 4:37 ` 答复: " Greg KH
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=2024041658-imagines-unlatch-a9b6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Eric.Yang2@amd.com \
--cc=JinZe.Xu@amd.com \
--cc=Josip.Pavic@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=airlied@linux.ie \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alvin.lee2@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aric.cyr@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=austin.zheng@amd.com \
--cc=chiahsuan.chung@amd.com \
--cc=christian.koenig@amd.com \
--cc=cruise.hung@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hanghong.ma@amd.com \
--cc=harry.wentland@amd.com \
--cc=jun.lei@amd.com \
--cc=lewis.huang@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=paul.hsieh@amd.com \
--cc=qingqing.zhuo@amd.com \
--cc=stylon.wang@amd.com \
--cc=sunglee@amd.com \
--cc=sunpeng.li@amd.com \
--cc=syed.hassan@amd.com \
--cc=trix@redhat.com \
--cc=wangzhu9@huawei.com \
--cc=wayne.lin@amd.com \
--cc=zhengzengkai@huawei.com \
/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®