From: Andrew Davis <afd@ti.com>
To: Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>, Randolph Sapp <rs@ti.com>,
<meta-arago@lists.yoctoproject.org>
Cc: Andrew Davis <afd@ti.com>
Subject: [meta-arago][master][PATCH 1/2] libdrm: Remove patch adding extra OMAP BO flags
Date: Thu, 5 Nov 2026 14:37:25 -0600 [thread overview]
Message-ID: <20261105203726.1306888-1-afd@ti.com> (raw)
These are not needed by any program currently built here, nor has any
recent TI kernel supported these in a long time. Changes to Linux UAPI
files should come from the Linux source currently in use. Remove these.
Signed-off-by: Andrew Davis <afd@ti.com>
---
.../recipes-graphics/drm/libdrm-arago.inc | 1 -
...BO-flags-to-affect-buffer-allocation.patch | 56 -------------------
2 files changed, 57 deletions(-)
delete mode 100644 meta-arago-distro/recipes-graphics/drm/libdrm/0002-omap-add-OMAP_BO-flags-to-affect-buffer-allocation.patch
diff --git a/meta-arago-distro/recipes-graphics/drm/libdrm-arago.inc b/meta-arago-distro/recipes-graphics/drm/libdrm-arago.inc
index 5b64677a..6703fd1d 100644
--- a/meta-arago-distro/recipes-graphics/drm/libdrm-arago.inc
+++ b/meta-arago-distro/recipes-graphics/drm/libdrm-arago.inc
@@ -2,7 +2,6 @@ FILESEXTRAPATHS:prepend := "${THISDIR}/libdrm:"
SRC_URI += " \
file://0001-Add-option-to-run-a-test-indefinitely.patch \
-file://0002-omap-add-OMAP_BO-flags-to-affect-buffer-allocation.patch \
"
PR:append = ".arago4"
diff --git a/meta-arago-distro/recipes-graphics/drm/libdrm/0002-omap-add-OMAP_BO-flags-to-affect-buffer-allocation.patch b/meta-arago-distro/recipes-graphics/drm/libdrm/0002-omap-add-OMAP_BO-flags-to-affect-buffer-allocation.patch
deleted file mode 100644
index 5daa9be2..00000000
--- a/meta-arago-distro/recipes-graphics/drm/libdrm/0002-omap-add-OMAP_BO-flags-to-affect-buffer-allocation.patch
+++ /dev/null
@@ -1,56 +0,0 @@
-From 9810d176a7947a6e8f432e1610da15937765fa06 Mon Sep 17 00:00:00 2001
-From: Tomi Valkeinen <tomi.valkeinen@ti.com>
-Date: Thu, 18 May 2017 10:37:11 +0300
-Subject: [PATCH] omap: add OMAP_BO flags to affect buffer allocation
-
-Import the kernel header changes from "drm/omap: add OMAP_BO flags to
-affect buffer allocation".
-
-On SoCs with TILER, we have to ways to allocate buffers: normal
-dma_alloc or via TILER (which basically functions as an IOMMU). TILER
-can map 128MB at a time, and we only map the TILER buffers when they are
-used (i.e. not at alloc time). If TILER is present, omapdrm always
-uses TILER.
-
-There are use cases that require lots of big buffers that are being used
-at the same time by different IPs. At the moment the userspace has a
-hard maximum of 128MB.
-
-This patch adds three new flags that can be used by the userspace to
-solve the situation:
-
-OMAP_BO_MEM_CONTIG: The driver will use dma_alloc to get the memory.
-This can be used to avoid TILER if the userspace knows it needs more
-than 128M of memory at the same time.
-
-OMAP_BO_MEM_TILER: The driver will use TILER to get the memory. There's
-nto much use for this flag at the moment, but it's here for
-completeness.
-
-OMAP_BO_MEM_PIN: The driver will pin the memory at alloc time, and keep
-it pinned. This can be used to 1) get an error at alloc time if TILER
-space is full, and 2) get rid of the constant pin/unpin operations which
-may have some effect on performance.
-
-If none of the flags are given, the behavior is the same as currently.
-
-Upstream-Status: Pending
-Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
----
- omap/omap_drm.h | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/omap/omap_drm.h b/omap/omap_drm.h
-index 9c6c0e4..d991b85 100644
---- a/omap/omap_drm.h
-+++ b/omap/omap_drm.h
-@@ -52,6 +52,9 @@ struct drm_omap_get_base {
- #define OMAP_BO_SCANOUT 0x00000001 /* scanout capable (phys contiguous) */
- #define OMAP_BO_CACHE_MASK 0x00000006 /* cache type mask, see cache modes */
- #define OMAP_BO_TILED_MASK 0x00000f00 /* tiled mapping mask, see tiled modes */
-+#define OMAP_BO_MEM_CONTIG 0x00000008 /* only use contiguous dma mem */
-+#define OMAP_BO_MEM_TILER 0x00000010 /* only use TILER mem */
-+#define OMAP_BO_MEM_PIN 0x00000020 /* pin the buffer when allocating */
-
- /* cache modes */
- #define OMAP_BO_CACHED 0x00000000 /* default */
--
2.43.0
next reply other threads:[~2026-11-05 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 20:37 Andrew Davis [this message]
2026-11-05 20:37 ` [meta-arago][master][PATCH 2/2] libdrm: Remove ltp-ddt test harness workaround Andrew Davis
2026-11-05 21:05 ` Randolph Sapp
2026-11-05 21:00 ` [meta-arago][master][PATCH 1/2] libdrm: Remove patch adding extra OMAP BO flags PRC Automation
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=20261105203726.1306888-1-afd@ti.com \
--to=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=reatmon@ti.com \
--cc=rs@ti.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.