From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: "Lazar, Lijo" <lijo.lazar@amd.com>, Jane Jian <Jane.Jian@amd.com>,
Haijun.Chang@amd.com, Victor.Zhao@amd.com
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/amdgpu: Add empty HDP flush function to JPEG v4.0.3
Date: Mon, 15 Jul 2024 17:30:26 +0200 [thread overview]
Message-ID: <d9d079fe-3368-4a58-b5af-2ae1f6b2b5f7@gmail.com> (raw)
In-Reply-To: <ac0f50d7-9133-45ac-8ba3-cd8567963f61@amd.com>
Am 15.07.24 um 17:08 schrieb Lazar, Lijo:
>
> On 7/15/2024 8:28 PM, Christian König wrote:
>>
>> Am 15.07.24 um 16:47 schrieb Jane Jian:
>>> From: Lijo Lazar <lijo.lazar@amd.com>
>>>
>>> JPEG v4.0.3 doesn't support HDP flush when RRMT is enabled. Instead,
>>> mmsch fw will do the flush.
>>>
>>> Signed-off-by: Lijo Lazar <lijo.lazar@amd.com>
>>> Signed-off-by: Jane Jian <Jane.Jian@amd.com>
>>> ---
>>> drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_3.c | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_3.c
>>> b/drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_3.c
>>> index 04d8966423de..ea601047dab0 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_3.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_3.c
>>> @@ -621,6 +621,14 @@ static uint64_t
>>> jpeg_v4_0_3_dec_ring_get_wptr(struct amdgpu_ring *ring)
>>> ring->pipe ? (0x40 * ring->pipe - 0xc80) : 0);
>>> }
>>> +static void jpeg_v4_0_3_ring_emit_hdp_flush(struct amdgpu_ring *ring)
>>> +{
>>> + /* VCN engine access for HDP flush doesn't work when RRMT is
>>> enabled.
>>> + * This is a workaround to avoid any HDP flush through VCN ring.
>>> Instead
>>> + * HDP flush will be done by driver while submitting doorbell.
>> I think that should read "HDP flush will be done by firmware ....".
>>
>> Or is it really the driver which should do this? In this case the patch
>> here would be wrong.
>>
> That's a copy-paste mistake. This comment was originally in the initial
> version of the patch.
Yeah thought so.
> Discussed with Jane and she'll be sending a revised version. Also, there
> is a third patch expected which does normalization of register offsets
> when submitted through ring.
Another question is if we have ever released JPEG/VCN firmware which
doesn't do the flush?
If yes then we need a version check here to provide backward
compatibility with already released firmware.
Regards,
Christian.
>
> Thanks,
> Lijo
>
>> Regards,
>> Christian.
>>
>>> + */
>>> +}
>>> +
>>> /**
>>> * jpeg_v4_0_3_dec_ring_set_wptr - set write pointer
>>> *
>>> @@ -1072,6 +1080,7 @@ static const struct amdgpu_ring_funcs
>>> jpeg_v4_0_3_dec_ring_vm_funcs = {
>>> .emit_ib = jpeg_v4_0_3_dec_ring_emit_ib,
>>> .emit_fence = jpeg_v4_0_3_dec_ring_emit_fence,
>>> .emit_vm_flush = jpeg_v4_0_3_dec_ring_emit_vm_flush,
>>> + .emit_hdp_flush = jpeg_v4_0_3_ring_emit_hdp_flush,
>>> .test_ring = amdgpu_jpeg_dec_ring_test_ring,
>>> .test_ib = amdgpu_jpeg_dec_ring_test_ib,
>>> .insert_nop = jpeg_v4_0_3_dec_ring_nop,
next prev parent reply other threads:[~2024-07-15 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:47 [PATCH 1/3] drm/amdgpu: Add empty HDP flush function to JPEG v4.0.3 Jane Jian
2024-07-15 14:58 ` Christian König
2024-07-15 15:08 ` Lazar, Lijo
2024-07-15 15:30 ` Christian König [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-16 7:59 Jane Jian
2024-07-18 6:12 ` Zhang, Hawking
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=d9d079fe-3368-4a58-b5af-2ae1f6b2b5f7@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Haijun.Chang@amd.com \
--cc=Jane.Jian@amd.com \
--cc=Victor.Zhao@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=lijo.lazar@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