From: Marek Vasut <marex@denx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Alain Volmat <alain.volmat@foss.st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Amelie DELAUNAY <amelie.delaunay@foss.st.com>,
Hugues FRUCHET <hugues.fruchet@foss.st.com>,
Philippe CORNU <philippe.cornu@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] media: stm32: dcmi: Register V4L2 subdev nodes
Date: Sun, 19 Jun 2022 02:28:55 +0200 [thread overview]
Message-ID: <4dc7b39c-35cd-663a-98f8-6034693df3c8@denx.de> (raw)
In-Reply-To: <Yq5dtc3MHz5gp5BK@pendragon.ideasonboard.com>
On 6/19/22 01:20, Laurent Pinchart wrote:
> Hi Marek,
>
> Thank you for the patch.
>
> On Sun, Jun 19, 2022 at 12:23:35AM +0200, Marek Vasut wrote:
>> Unless the V4L2 device calls v4l2_device_register_subdev_nodes(),
>> the /dev/v4l-subdev* sub-device nodes are not registered and thus
>> not created. Add the missing call.
>
> This driver configures the subdevs internally. Exposing the subdev nodes
> to userspace would conflict with driver operation.
>
> If you need the subdev nodes only to query subdev information, you can
> use v4l2_device_register_ro_subdev_nodes(). Ideally I'd prefer this
> driver to expose subdev nodes to userspace and stop propagating formats
> internally, but that may break applications :-(
I need those subdevs to configure e.g. test pattern on the sensor side.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-19 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 22:23 [PATCH] media: stm32: dcmi: Register V4L2 subdev nodes Marek Vasut
2022-06-18 23:20 ` Laurent Pinchart
2022-06-19 0:28 ` Marek Vasut [this message]
2022-06-19 0:33 ` Laurent Pinchart
2022-06-19 0:43 ` Marek Vasut
2022-06-27 8:52 ` Hugues FRUCHET
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=4dc7b39c-35cd-663a-98f8-6034693df3c8@denx.de \
--to=marex@denx.de \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=hugues.fruchet@foss.st.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=philippe.cornu@foss.st.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