From: "Christian König" <christian.koenig@amd.com>
To: Leo Liu <leo.liu@amd.com>, Ruijing Dong <ruijing.dong@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: alexander.deucher@amd.com
Subject: Re: [PATCH v4] drm/amdgpu: add HW_IP_VCN_UNIFIED type
Date: Mon, 18 Jul 2022 15:54:14 +0200 [thread overview]
Message-ID: <4f91384a-bef6-b8da-77c1-0bd5f4e7b3c1@amd.com> (raw)
In-Reply-To: <7beb798d-73ba-7015-7b3d-441a5daef26f@amd.com>
Am 18.07.22 um 15:48 schrieb Leo Liu:
>
> On 2022-07-18 02:57, Christian König wrote:
>> Am 15.07.22 um 22:04 schrieb Ruijing Dong:
>>> From VCN4, AMDGPU_HW_IP_VCN_UNIFIED is used to support
>>> both encoding and decoding jobs, it re-uses the same
>>> queue number of AMDGPU_HW_IP_VCN_ENC.
>>>
>>> link:
>>> https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/245/commits
>>>
>>> Signed-off-by: Ruijing Dong <ruijing.dong@amd.com>
>>> ---
>>> include/uapi/drm/amdgpu_drm.h | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/include/uapi/drm/amdgpu_drm.h
>>> b/include/uapi/drm/amdgpu_drm.h
>>> index 18d3246d636e..e268cd3cdb12 100644
>>> --- a/include/uapi/drm/amdgpu_drm.h
>>> +++ b/include/uapi/drm/amdgpu_drm.h
>>> @@ -560,6 +560,12 @@ struct drm_amdgpu_gem_va {
>>> #define AMDGPU_HW_IP_UVD_ENC 5
>>> #define AMDGPU_HW_IP_VCN_DEC 6
>>> #define AMDGPU_HW_IP_VCN_ENC 7
>>> +/**
>>
>> Please don't use "/**" here, that is badly formated for a kerneldoc
>> comment.
>>
>>> + * From VCN4, AMDGPU_HW_IP_VCN_UNIFIED is used to support
>>> + * both encoding and decoding jobs, it re-uses the same
>>> + * queue number of AMDGPU_HW_IP_VCN_ENC.
>>> + */
>>> +#define AMDGPU_HW_IP_VCN_UNIFIED AMDGPU_HW_IP_VCN_ENC
>>
>> I'm still in doubt that adding another define with the same value as
>> AMDGPU_HW_IP_VCN_ENC is a good idea.
>
> Hi Christian,
>
> From VCN4, there is no VCN dec and enc ring type any more, the
> decode/encode will go through the unified queue, so using
> AMDGPU_HW_IP_VCN_ENC is no longer accurate . Keeping
> AMDGPU_HW_IP_VCN_ENC type is for legacy HW, and the new
> AMDGPU_HW_IP_VCN_UNIFIED just happen to use the same HW ring as legacy
> encode ring, so reuse the value, and that is the whole idea.
Yeah, I understand your reasoning I just don't see it this way.
What happened is that the encode ring was extended with decode
functionality. In other words we still use the same format for encoding,
we just added another one for decoding as well.
Renaming the enum and adding AMDGPU_HW_IP_VCN_UNIFIED suggests that this
is something completely new, which is not the case here. The encoding
commands stay the same, don't they?
So to sum it up my suggestion is to stick with AMDGPU_HW_IP_VCN_ENC and
just document on the definition that this is used for both encode as
well as decode starting with VCN4.
Regards,
Christian.
>
> Thanks,
>
> Leo
>
>
>>
>>
>> Instead we should just add the comment to AMDGPU_HW_IP_VCN_ENC.
>>
>> Regards,
>> Christian.
>>
>>> #define AMDGPU_HW_IP_VCN_JPEG 8
>>> #define AMDGPU_HW_IP_NUM 9
>>
next prev parent reply other threads:[~2022-07-18 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 20:04 [PATCH v4] drm/amdgpu: add HW_IP_VCN_UNIFIED type Ruijing Dong
2022-07-15 20:15 ` Liu, Leo
2022-07-18 6:57 ` Christian König
2022-07-18 13:48 ` Leo Liu
2022-07-18 13:54 ` Christian König [this message]
2022-07-18 14:14 ` Dong, Ruijing
2022-07-18 14:37 ` Christian König
2022-07-18 14:44 ` Dong, Ruijing
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=4f91384a-bef6-b8da-77c1-0bd5f4e7b3c1@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=leo.liu@amd.com \
--cc=ruijing.dong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.