Linux Media Controller development
 help / color / mirror / Atom feed
From: Rishikesh Donadkar <r-donadkar@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	<libcamera-devel@lists.libcamera.org>,
	<linux-media@vger.kernel.org>
Subject: Re: [ANNOUNCEMENT] Camera & ISP at Linux Plumbers Conference
Date: Thu, 1 Oct 2026 11:49:17 +0530	[thread overview]
Message-ID: <22a0424b-c67d-4dcc-a31c-26acd764c653@ti.com> (raw)
In-Reply-To: <20260914233810.GA2796257@killaraus.ideasonboard.com>



On 15/09/26 05:08, Laurent Pinchart wrote:
> Hello,
> 
> As most of you already know, the Linux Plumbers Conference will host a
> Camera & ISP BoF in Prague in three weeks ([1]).
> 
> The initial proposal for a microconference has unfortunately been
> downgraded by the program committee to a 45 minutes BoF. We have
> therefore decided to limit the discussion to three topics at most. Two
> topics have been approved so far:
> 
> - RGB-IR support in V4L2 and libcamera
> 
>    by Rishikesh Donadkar and Devarsh Thakkar, Texas Instruments
> 
>    The Linux kernel V4L2 API does not support RGB-IR image sensors.
>    While building blocks necessary to handle those devices are slowly
>    being merged, RGB-IR support itself hasn't been tackled yet.
> 
>    Rishikesh and Devarsh will also present this topic at the OSS Europe
>    conference ([2]).

Hello everyone,

I have submitted an RFC for the OV2312 camera sensor driver[1]. This 
patch series proposes the use of array controls to facilitate setting 
controls for both the RGB and IR streams coming out of the camera 
subdevice.

I would greatly appreciate your feedback and thoughts on this approach.

[1] 
https://lore.kernel.org/all/20260925133001.2780868-1-r-donadkar@ti.com/#t

Regards,
Rishikesh

> 
> - Camera module identification
> 
>    by Stefan Klug, Ideas on Board
> 
>    Camera tuning and calibration depend not only on the image sensor, but
>    also on the lens and other characteristics of camera modules. While
>    Linux supports identifying image sensors, it completely lacks the
>    concept of camera modules.
> 
>    Identification of camera modules requires coordination between
>    platform firmware (DT or ACPI), the kernel and userspace. Discussions
>    will benefit from the presence of DT maintainers.
> 
> We can consider scheduling a third topic. Proposals are welcome.
> 
> Due to the 45 minutes BoF format, we will focus on discussions and won't
> be able to afford presentations. All topic leads are expected to
> circulate discussion materials on public mailing lists at least a week
> before the event to give attendees time to read through proposals. The
> materials should summarize the issue at hand and the ongoing work, and
> clearly state the questions that will be discussed during the BoF.
> Slides that support the discussions, if any, should also be submitted
> prior to the event.
> 
> If there is enough interest, I am considering booking a meeting room on
> Wednesday morning (location to be determined, likely outside of the LPC
> venue) to extend the BoF. We could continue discussions on the topics
> listed above, as well as schedule additional topics. We would overlap
> with the following LPC microconferences:
> 
> - Networking Track
> - Containers and checkpoint/restore MC
> - Rust MC
> - Scheduler and Real-Time MC
> - Build Systems MC
> 
> Please let me know if you would be interested in attending a Wednesday
> morning session by replying to this e-mail (publicly or privately). If
> you would like to propose additional topics, please do so publicly.
> 
> 
> [1] https://lpc.events/event/20/contributions/2364/
> [2] https://osselceu2026.sched.com/event/2RaZj/enabling-multi-stream-camera-sensors-in-linux-rgb+ir-streams-and-embedded-metadata-rishikesh-donadkar-devarsh-thakkar-texas-instruments
> 


  parent reply	other threads:[~2026-10-01  6:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <UzpC1s2YnBtZIaRCab_Y8AbCecyauDUO4OC7Nhd1-h4TE21aLSghbwDuOKgdwJQugvPMjM4foPHuL-UKnBLD6A==@protonmail.internalid>
2026-09-14 23:38 ` [ANNOUNCEMENT] Camera & ISP at Linux Plumbers Conference Laurent Pinchart
2026-09-17 13:47   ` Bryan O'Donoghue
2026-09-18  8:08     ` johannes.goede
2026-09-18  9:18     ` Laurent Pinchart
2026-09-19 21:45       ` Bryan O'Donoghue
2026-09-19 22:29         ` Laurent Pinchart
2026-09-21 11:52           ` Bryan O'Donoghue
2026-09-21 16:02             ` Nicolas Dufresne
2026-09-27  9:01   ` johannes.goede
2026-09-27  9:04   ` johannes.goede
2026-09-30 11:18   ` Stefan Klug
2026-09-30 22:01     ` Conor Dooley
2026-10-02 16:14       ` Stefan Klug
2026-10-03 14:56         ` Loic Poulain
2026-10-01 15:15     ` johannes.goede
2026-10-01 20:55       ` Laurent Pinchart
2026-10-02  6:56         ` Sakari Ailus
2026-10-02 18:31           ` Laurent Pinchart
2026-10-06 10:03             ` Sakari Ailus
     [not found]   ` <2e1d628f-8183-4446-9500-9886561f320b@mm-sol.com>
2026-09-30 23:23     ` Laurent Pinchart
2026-10-06  6:30       ` Gjorgji Rosikopulos
2026-10-01  6:19   ` Rishikesh Donadkar [this message]
2026-10-01 21:08     ` 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=22a0424b-c67d-4dcc-a31c-26acd764c653@ti.com \
    --to=r-donadkar@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=libcamera-devel@lists.libcamera.org \
    --cc=linux-media@vger.kernel.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