From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-doc@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Haren Myneni <haren@linux.ibm.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Andrew Donnellan <ajd@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Akshay Gupta <akshay.gupta@amd.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
hans@jjverkuil.nl, laurent.pinchart@ideasonboard.com,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Lee Jones <lee@kernel.org>
Subject: [PATCH 0/2] Document Media Controller IOCTL number assignments
Date: Mon, 26 May 2025 14:17:30 +0300 [thread overview]
Message-ID: <20250526111732.487229-1-sakari.ailus@linux.intel.com> (raw)
Hello all,
The Media Controller uses IOCTL numbers with '|' type up to 0x81 but the
range from 0x80 upwards is documented to belong to samples. The samples,
however, are not currently using these values. Solve the problem by
bumping the top of the MC range and the samples allocation by 0x10.
Some sample code in samples/rust/rust_misc_device.rs also uses MC IOCTL
numbers below the current limit 0x80, it'd be nice to address that as well
as align with the changes in this patch.
Sakari Ailus (2):
Documentation: Bump media IOCTL reserved numbers
media: uapi: Document IOCTL number assignment
Documentation/userspace-api/ioctl/ioctl-number.rst | 4 ++--
include/uapi/linux/media.h | 4 ++++
2 files changed, 6 insertions(+), 2 deletions(-)
--
2.39.5
next reply other threads:[~2025-05-26 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-26 11:17 Sakari Ailus [this message]
2025-05-26 11:17 ` [PATCH 1/2] Documentation: Bump media IOCTL reserved numbers Sakari Ailus
2025-05-26 11:48 ` Laurent Pinchart
2025-05-26 13:24 ` Sakari Ailus
2025-05-26 11:17 ` [PATCH 2/2] media: uapi: Document IOCTL number assignment Sakari Ailus
2025-05-26 11:48 ` Laurent Pinchart
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=20250526111732.487229-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ajd@linux.ibm.com \
--cc=akshay.gupta@amd.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hans@jjverkuil.nl \
--cc=haren@linux.ibm.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mchehab+huawei@kernel.org \
--cc=mpe@ellerman.id.au \
/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