From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
sumit.semwal@linaro.org, christian.koenig@amd.com
Cc: openpvrsgx-devgroup@letux.org, merlijn@wizzup.org,
philipp@uvos.xyz, airlied@linux.ie, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] drm: omapdrm: Fix implicit dma_buf fencing
Date: Thu, 6 Jan 2022 18:26:22 +0200 [thread overview]
Message-ID: <e55b3d0f-2217-c949-f166-63ca738b44f6@gmail.com> (raw)
In-Reply-To: <0ba4b947-57e0-8a80-68d6-a481d5145ab4@ideasonboard.com>
Hi,
On 6.01.22 г. 15:43 ч., Tomi Valkeinen wrote:
> Hi,
>
> On 05/01/2022 17:36, Ivaylo Dimitrov wrote:
>> Currently omapdrm driver does not initialize dma_buf_export_info resv
>> member, which leads to a new dma_resv being allocated and attached to
>> the exported dma_buf. This leads to the issue that fences created on
>> dma_buf objects imported by other drivers are ignored by omapdrm, as only
>> fences in gem object resv are waited on. This leads to various issues
>> like
>> displaying incomplete frames.
>>
>> Fix that by initializing dma_buf resv to the resv of the gem object being
>> exported.
>>
>> Signed-off-by: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
>> ---
>> drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c
>> b/drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c
>> index f1f93cabb61e..a111e5c91925 100644
>> --- a/drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c
>> +++ b/drivers/gpu/drm/omapdrm/omap_gem_dmabuf.c
>> @@ -88,6 +88,7 @@ struct dma_buf *omap_gem_prime_export(struct
>> drm_gem_object *obj, int flags)
>> exp_info.size = omap_gem_mmap_size(obj);
>> exp_info.flags = flags;
>> exp_info.priv = obj;
>> + exp_info.resv = obj->resv;
>> return drm_gem_dmabuf_export(obj->dev, &exp_info);
>> }
>
> Thanks! Pushed to drm-misc-next.
>
Thanks,
I think lts kernels shall get that fix too, but I have no idea how :) .
Ivo.
prev parent reply other threads:[~2022-01-06 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 15:36 Ivaylo Dimitrov
2022-01-06 9:45 ` [Openpvrsgx-devgroup] " Tony Lindgren
2022-01-06 12:51 ` Merlijn Wajer
2022-01-06 13:43 ` Tomi Valkeinen
2022-01-06 16:26 ` Ivaylo Dimitrov [this message]
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=e55b3d0f-2217-c949-f166-63ca738b44f6@gmail.com \
--to=ivo.g.dimitrov.75@gmail.com \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=openpvrsgx-devgroup@letux.org \
--cc=philipp@uvos.xyz \
--cc=sumit.semwal@linaro.org \
--cc=tomi.valkeinen@ideasonboard.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®