mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Martin Hecht <mhecht73@gmail.com>
Cc: linux-media@vger.kernel.org, michael.roeder@avnet.eu,
	martin.hecht@avnet.eu, Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] add V4L2_CID_USER_ALVIUM_BASE and request space for up to 128 controls
Date: Sun, 11 Oct 2026 22:33:41 +0300	[thread overview]
Message-ID: <asvklbPb8PWcPp0W@kekkonen.localdomain> (raw)
In-Reply-To: <20261009173826.968402-1-mhecht73@gmail.com>

Hi Martin,

On Fri, Oct 09, 2026 at 07:38:24PM +0200, Martin Hecht wrote:
> That patch requests a continoous block of controls to enable various
> features of the Alvium camera family. There are many features like
> triggers, ROI for auto functions like AWB, auto gain and so on.
> 
> Signed-off-by: Martin Hecht <mhecht73@gmail.com>

Thanks for the patch.

Could you also include some patches for actual control definitions in the
same patchset?

> ---
>  include/uapi/linux/v4l2-controls.h | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/include/uapi/linux/v4l2-controls.h b/include/uapi/linux/v4l2-controls.h
> index d17e41d51d2e..5ed91c053617 100644
> --- a/include/uapi/linux/v4l2-controls.h
> +++ b/include/uapi/linux/v4l2-controls.h
> @@ -255,6 +255,12 @@ enum v4l2_colorfx {
>   */
>  #define V4L2_CID_USER_IT6625_BASE		(V4L2_CID_USER_BASE + 0x1250)
>  
> +/*
> + * The base for Alvium CSI2 driver controls.
> + * We reserve 128 controls for this driver.
> + */
> +#define V4L2_CID_USER_ALVIUM_BASE		(V4L2_CID_USER_BASE + 0x1260)
> +
>  /* MPEG-class control IDs */
>  /* The MPEG controls are applicable to all codec controls
>   * and the 'MPEG' part of the define is historical */

-- 
Kind regards,

Sakari Ailus

      reply	other threads:[~2026-10-11 19:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 17:38 Martin Hecht
2026-10-11 19:33 ` Sakari Ailus [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=asvklbPb8PWcPp0W@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=martin.hecht@avnet.eu \
    --cc=mchehab@kernel.org \
    --cc=mhecht73@gmail.com \
    --cc=michael.roeder@avnet.eu \
    /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®