All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Ryan Eatmon <reatmon@ti.com>
Cc: gehariprasath@ti.com, afd@ti.com, praneeth@ti.com,
	denys@konsulko.com, meta-ti@lists.yoctoproject.org,
	s-kapoor@ti.com, p-gupta5@ti.com, u-kumar1@ti.com
Subject: Re: [meta-ti][scarthgap][PATCH v3] ti-vendor-kernel-headers: add recipe for TI-only dma-heap.h ioctl
Date: Sat, 29 Aug 2026 16:04:40 -0400	[thread overview]
Message-ID: <20260829200440.GL19759@denix.org> (raw)
In-Reply-To: <f12fc893-5928-45e0-ad9d-3966d3bbbf87@ti.com>

On Fri, Aug 28, 2026 at 03:54:00PM -0500, Ryan Eatmon wrote:
> 
> 
> On 8/28/2026 12:44 PM, Denys Dmytriyenko wrote:
> >On Fri, Aug 28, 2026 at 08:28:34PM +0530, Hari Prasath via lists.yoctoproject.org wrote:
> >>The TI vendor kernel's dma-heap.h carries DMA_HEAP_IOCTL_EXPORT in
> >>downstream. The standard header provided by linux-libc-headers' wouldn't
> >>have the custom changes.Copy it straight from the kernel's staged
> >>source tree (STAGING_KERNEL_DIR) into a separate /usr/include/ti/linux
> >>path instead, for userspace code that needs it.
> >>
> >>Signed-off-by: Hari Prasath Gujulan Elango <gehariprasath@ti.com>
> >>---
> >>	v1->v2: Address review comments in commit message and recipe description
> >>	v2->v3: Fix the patch subject prefix
> >>
> >>  .../ti-vendor-kernel-headers_1.0.bb             | 17 +++++++++++++++++
> >>  1 file changed, 17 insertions(+)
> >>  create mode 100644 meta-ti-bsp/recipes-kernel/ti-vendor-kernel-headers/ti-vendor-kernel-headers_1.0.bb
> >>
> >>diff --git a/meta-ti-bsp/recipes-kernel/ti-vendor-kernel-headers/ti-vendor-kernel-headers_1.0.bb b/meta-ti-bsp/recipes-kernel/ti-vendor-kernel-headers/ti-vendor-kernel-headers_1.0.bb
> >>new file mode 100644
> >>index 000000000..5d570689a
> >>--- /dev/null
> >>+++ b/meta-ti-bsp/recipes-kernel/ti-vendor-kernel-headers/ti-vendor-kernel-headers_1.0.bb
> >>@@ -0,0 +1,17 @@
> >>+SUMMARY = "TI vendor kernel uapi headers not present in mainline linux-libc-headers"
> >>+DESCRIPTION = "Copies select UAPI headers straight from the TI vendor kernel source \
> >>+tree into a TI-specific include path (/usr/include/ti/linux), for userspace code \
> >>+that needs them but can't rely on linux-libc-headers carrying TI-only additions."
> >>+LICENSE = "GPL-2.0-only"
> >>+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0-only;md5=801f80980d171dd6425610833a22dbe6"
> >>+
> >>+PACKAGE_ARCH = "${MACHINE_ARCH}"
> >>+
> >>+do_configure[depends] += "virtual/kernel:do_shared_workdir"
> >
> >Why do you need this dependency for do_configure? Moreover, since you don't
> >have do_configure nor do_compile, you might want to mark them as "noexec"
> >
> >
> >>+do_install[depends] += "virtual/kernel:do_shared_workdir"
> >
> >How do you ensure that virtual/kernel is the TI vendor kernel? If it's not,
> >you'll be copying the original unmodified header into the ti/linux location.
> 
> 
> Should this just be part of the linux-ti-staging recipes?  That way
> we can correctly only include it in the versions that have this
> file?

Yeah, probably the easiest and cleanest approach...


> >>+
> >>+do_install() {
> >>+    install -d ${D}${includedir}/ti/linux
> >>+    install -m 0644 ${STAGING_KERNEL_DIR}/include/uapi/linux/dma-heap.h ${D}${includedir}/ti/linux/dma-heap.h
> >>+}
> >>+
> >>-- 
> >>2.34.1


  reply	other threads:[~2026-08-29 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 14:58 [meta-ti][scarthgap][PATCH v3] ti-vendor-kernel-headers: add recipe for TI-only dma-heap.h ioctl Hari Prasath Gujulan Elango
2026-08-28 15:07 ` PRC Automation
2026-08-28 17:44 ` Denys Dmytriyenko
2026-08-28 20:54   ` Ryan Eatmon
2026-08-29 20:04     ` Denys Dmytriyenko [this message]
2026-08-30 16:28       ` Hari Prasath G E
     [not found]     ` <18D05F5A209FB29A.873310@lists.yoctoproject.org>
2026-08-29 20:18       ` Denys Dmytriyenko
2026-08-29  8:08   ` Hari Prasath G E

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=20260829200440.GL19759@denix.org \
    --to=denis@denix.org \
    --cc=afd@ti.com \
    --cc=denys@konsulko.com \
    --cc=gehariprasath@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=p-gupta5@ti.com \
    --cc=praneeth@ti.com \
    --cc=reatmon@ti.com \
    --cc=s-kapoor@ti.com \
    --cc=u-kumar1@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.