From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Yongqin Liu <yongqin.liu@linaro.org>, Andrew Davis <afd@ti.com>
Cc: "Bajjuri, Praneeth" <praneeth@ti.com>,
airlied@linux.ie,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
merlijn@wizzup.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, tony@atomide.com,
linux-omap@vger.kernel.org,
Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: [PATCH 3/3] drm: omapdrm: Do no allocate non-scanout GEMs through DMM/TILER
Date: Tue, 30 Aug 2022 21:23:28 +0300 [thread overview]
Message-ID: <db245ada-2f2e-c65d-ef14-35ea4adda123@ideasonboard.com> (raw)
In-Reply-To: <0eb026d9-faaa-68cb-cdcd-7d031acfbb03@gmail.com>
On 30/08/2022 21:08, Ivaylo Dimitrov wrote:
>>> flags &= ~OMAP_BO_TILED_MASK;
>>> flags |= 0x00000008;
>>> flags |= OMAP_BO_WC;
>>>
>>> bo = omap_bo_new(dev, size, flags);
>>>
>>> As you can see we use 0x00000008 (OMAP_BO_MEM_CONTIG) unconditionally.
>>> This was a hack added since even non-scanout buffers sometimes need
>>> to be contiguous (video decoder surfaces), but we had no way back
>
> Hmm, why would video decoder need linear memory? No MMU?
Not sure about this case, but many/most IPs don't have MMU. E.g. CSI-2
or parallel capture.
>>> If you tell me what the code should look like, I can rebuild the
>>> lib and post a copy.
>>>
>>> Long term, I'd like to start using DMA-BUF Heaps for CMA memory
>>> allocations in gralloc and elsewhere, then drop out the DMM/TILER
>>> support from OMAPDRM, since it never really belonged there in
>>> the first place (being a IOMMU unrelated to the display/GPU).
>>>
>
> Umm, how will we rotate scanout buffers then?
Didn't we discuss this earlier in this thread. Or some other thread.
Related to VRFB... I'm not sure =).
Anyway, neither VRFB nor DMM/TILER are part of the DSS. They're part of
the memory subsystem. They can be used without DSS being in the setup.
Thus the code for VRFB and DMM/TILER should not be in the DSS driver.
The DSS driver should still, of course, support DMM/TILER (and maybe
VRFB some day) in the "use" sense, i.e. so that DSS can use the
DMM/TILER provided from another driver.
But how exactly that's to be implemented, I don't know.
Tomi
next prev parent reply other threads:[~2022-08-30 18:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 10:23 [PATCH 0/3] drm: omapdrm: Fix excessive GEM buffers DMM/CMA usage Ivaylo Dimitrov
2022-01-19 10:23 ` [PATCH 1/3] drm: omapdrm: simplify omap_gem_pin Ivaylo Dimitrov
2022-01-19 10:23 ` [PATCH 2/3] drm: omapdrm: Support exporting of non-contiguous GEM BOs Ivaylo Dimitrov
2022-01-19 10:23 ` [PATCH 3/3] drm: omapdrm: Do no allocate non-scanout GEMs through DMM/TILER Ivaylo Dimitrov
2022-02-17 12:46 ` Tomi Valkeinen
2022-02-17 15:29 ` Ivaylo Dimitrov
2022-08-12 4:35 ` Yongqin Liu
2022-08-13 6:58 ` Ivaylo Dimitrov
2022-08-14 14:27 ` Yongqin Liu
2022-08-15 6:23 ` Ivaylo Dimitrov
2022-08-17 4:52 ` Yongqin Liu
2022-08-18 10:23 ` Ivaylo Dimitrov
2022-08-29 2:51 ` Yongqin Liu
2022-08-29 13:24 ` Ivaylo Dimitrov
2022-08-29 14:36 ` Andrew Davis
2022-08-30 15:08 ` Yongqin Liu
2022-08-30 18:08 ` Ivaylo Dimitrov
2022-08-30 18:23 ` Tomi Valkeinen [this message]
2022-09-02 14:13 ` Ivaylo Dimitrov
2022-10-30 22:08 ` H. Nikolaus Schaller
2022-10-31 7:05 ` Ivaylo Dimitrov
2022-10-31 7:44 ` H. Nikolaus Schaller
2022-10-31 7:57 ` H. Nikolaus Schaller
2022-10-31 9:58 ` Ivaylo Dimitrov
2022-10-31 10:07 ` H. Nikolaus Schaller
2022-10-31 10:13 ` Tony Lindgren
2022-10-31 10:30 ` Ivaylo Dimitrov
2022-10-31 11:14 ` Ivaylo Dimitrov
2022-02-14 7:08 ` [PATCH 0/3] drm: omapdrm: Fix excessive GEM buffers DMM/CMA usage Ivaylo Dimitrov
2022-02-16 8:10 ` Thomas Zimmermann
2022-02-17 13:03 ` Tomi Valkeinen
2022-02-17 16:21 ` Ivaylo Dimitrov
2022-03-08 8:51 ` Tomi Valkeinen
2022-03-28 9:46 ` Tomi Valkeinen
2022-03-28 15:30 ` Ivaylo Dimitrov
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=db245ada-2f2e-c65d-ef14-35ea4adda123@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=afd@ti.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=praneeth@ti.com \
--cc=sumit.semwal@linaro.org \
--cc=tony@atomide.com \
--cc=yongqin.liu@linaro.org \
/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®