From: Lang Yu <Lang.Yu@amd.com>
To: Juntong Deng <juntong.deng@outlook.com>
Cc: alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, airlied@gmail.com, daniel@ffwll.ch,
aurabindo.pillai@amd.com, shiwu.zhang@amd.com,
Bhawanpreet.Lakha@amd.com, harry.wentland@amd.com,
linux-kernel-mentees@lists.linuxfoundation.org,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Add description for AMD_IP_BLOCK_TYPE_VPE
Date: Mon, 25 Sep 2023 16:18:07 +0800 [thread overview]
Message-ID: <ZRFCP23GbTLjig5u@lang-desktop> (raw)
In-Reply-To: <VI1P193MB07528C2081A3A8BBDFAF2BED99FDA@VI1P193MB0752.EURP193.PROD.OUTLOOK.COM>
On 09/24/ , Juntong Deng wrote:
> AMD_IP_BLOCK_TYPE_VPE is a new IP BLOCK type for Video Processing Engine,
> but currently lacks description.
>
> Fix the documentation warning:
> warning: Enum value 'AMD_IP_BLOCK_TYPE_VPE' not described in
> enum 'amd_ip_block_type'
>
> Signed-off-by: Juntong Deng <juntong.deng@outlook.com>
Thanks!
Reviewed-by: Lang Yu <lang.yu@amd.com>
> ---
> drivers/gpu/drm/amd/include/amd_shared.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/amd/include/amd_shared.h b/drivers/gpu/drm/amd/include/amd_shared.h
> index 63e2153c00c4..314fd44ec018 100644
> --- a/drivers/gpu/drm/amd/include/amd_shared.h
> +++ b/drivers/gpu/drm/amd/include/amd_shared.h
> @@ -83,6 +83,7 @@ enum amd_apu_flags {
> * @AMD_IP_BLOCK_TYPE_VCN: Video Core/Codec Next
> * @AMD_IP_BLOCK_TYPE_MES: Micro-Engine Scheduler
> * @AMD_IP_BLOCK_TYPE_JPEG: JPEG Engine
> +* @AMD_IP_BLOCK_TYPE_VPE: Video Processing Engine
> * @AMD_IP_BLOCK_TYPE_UMSCH_MM: User Mode Schduler for Multimedia
> * @AMD_IP_BLOCK_TYPE_NUM: Total number of IP block types
> */
> --
> 2.39.2
>
next prev parent reply other threads:[~2023-09-25 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 20:00 [PATCH] drm/amdgpu: Add description for AMD_IP_BLOCK_TYPE_VPE Juntong Deng
2023-09-25 8:18 ` Lang Yu [this message]
2023-09-25 11:58 ` Christian König
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=ZRFCP23GbTLjig5u@lang-desktop \
--to=lang.yu@amd.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=juntong.deng@outlook.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shiwu.zhang@amd.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