From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Michael Riesch <michael.riesch@collabora.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Maxime Ripard <mripard@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 2/5] media: v4l2-subdev: Add new ioctl for connection status
Date: Fri, 02 Oct 2026 10:53:21 +0200 [thread overview]
Message-ID: <xhkdb5wzkv5z2.fsf@mkorpers-koolstof.csb> (raw)
In-Reply-To: <ar9ZgBPEGxzNTSzU@kekkonen.localdomain>
Hi Sakari,
On Fri, Oct 02, 2026 at 10:13, Sakari Ailus <sakari.ailus@linux.intel.com> wrote:
> Hi Mattijs,
>
> On Thu, Oct 01, 2026 at 02:55:20PM +0200, Mattijs Korpershoek wrote:
>> The V4L2 framework has historically assumed that every component of the
>> camera pipeline is always present. This is a reasonable assumption for
>> integrated cameras in laptops or phones. However, in automotive systems,
>> cameras (e.g. rear-view or surround-view) can be damaged or
>> disconnected.
>>
>> When a camera gets disconnected, userspace cannot detect this and thus
>> cannot react (for example, by disabling streaming on a faulty camera).
>>
>> Add a new v4l2-subdev ioctl (VIDIOC_SUBDEV_G_CONNECTION_STATUS) that
>> drivers can implement to report their connection status.
>>
>> Signed-off-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
>
> Have you considered using V4L2 controls for this?
I have not considered it.
I think I initially wanted to make this a control but I ended up making
it an ioctl.
From patch 5/5 in this thread, it seems that you believe that a control
is more appropriate. I will look into that for v2.
Thanks for the suggestion!
Mattijs
>
> --
> Regards,
>
> Sakari Ailus
next prev parent reply other threads:[~2026-10-02 8:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 12:55 [PATCH RFC 0/5] media: Fault-Tolerant V4L2 Mattijs Korpershoek
2026-10-01 12:55 ` [PATCH RFC 1/5] media: imx219: Move LP-11 state switch to power_on() Mattijs Korpershoek
2026-10-01 17:03 ` Dave Stevenson
2026-10-01 12:55 ` [PATCH RFC 2/5] media: v4l2-subdev: Add new ioctl for connection status Mattijs Korpershoek
2026-10-02 7:13 ` Sakari Ailus
2026-10-02 8:53 ` Mattijs Korpershoek [this message]
2026-10-01 12:55 ` [PATCH RFC 3/5] media: imx219: Allow driver probe with missing sensor Mattijs Korpershoek
2026-10-01 16:50 ` Dave Stevenson
2026-10-01 17:35 ` Dave Stevenson
2026-10-01 12:55 ` [PATCH RFC 4/5] media: imx219: Implement .detect() sensor operation Mattijs Korpershoek
2026-10-01 12:55 ` [PATCH RFC 5/5] media: imx219: Add status polling using .detect() Mattijs Korpershoek
2026-10-01 15:58 ` Dave Stevenson
2026-10-01 17:26 ` Dave Stevenson
2026-10-02 8:39 ` Mattijs Korpershoek
2026-10-02 7:21 ` Sakari Ailus
2026-10-02 8:45 ` Mattijs Korpershoek
2026-10-02 8:32 ` Mattijs Korpershoek
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=xhkdb5wzkv5z2.fsf@mkorpers-koolstof.csb \
--to=mkorpershoek@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michael.riesch@collabora.com \
--cc=mripard@kernel.org \
--cc=sakari.ailus@linux.intel.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 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®