From: Hans Verkuil <hverkuil@xs4all.nl>
To: Hugues Fruchet <hugues.fruchet@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Yannick Fertre <yannick.fertre@st.com>,
Philippe CORNU <philippe.cornu@st.com>,
Mickael GUENE <mickael.guene@st.com>
Subject: Re: [PATCH v4 0/3] DCMI bridge support
Date: Wed, 7 Aug 2019 12:15:59 +0200 [thread overview]
Message-ID: <28a2a9ac-d5b9-a312-616a-620e0385cf66@xs4all.nl> (raw)
In-Reply-To: <1564577783-18627-1-git-send-email-hugues.fruchet@st.com>
Hi Hugues,
Can you provide the output of the most recent v4l2-compliance?
Use 'v4l2-compliance -s'.
Also, just to confirm, with this v4 there are no /dev/mediaX or
/dev/v4l-subdevX devices created anymore, right?
This v4 looks good to me, I just want to have these final checks
done.
Regards,
Hans
On 7/31/19 2:56 PM, Hugues Fruchet wrote:
> This patch serie allows to connect non-parallel camera sensor to
> DCMI thanks to a bridge connected in between such as STMIPID02 [1].
>
> Media controller support is introduced first, then support of
> several sub-devices within pipeline with dynamic linking
> between them.
> In order to keep backward compatibility with applications
> relying on V4L2 interface only, format set on video node
> is propagated to all sub-devices connected to camera interface.
>
> [1] https://www.spinics.net/lists/devicetree/msg278002.html
>
> ===========
> = history =
> ===========
> version 4:
> - Also drop subdev nodes registry as suggested by Hans:
> https://www.spinics.net/lists/arm-kernel/msg743375.html
>
> version 3:
> - Drop media device registry to not expose media controller
> interface to userspace as per Laurent' suggestion:
> https://www.spinics.net/lists/linux-media/msg153417.html
> - Prefer "source" instead of "sensor" and keep it in
> dcmi_graph_entity struct, move asd as first member
> of struct as per Sakari' suggestion:
> https://www.spinics.net/lists/linux-media/msg153119.html
> - Drop dcmi_graph_deinit() as per Sakari' suggestion:
> https://www.spinics.net/lists/linux-media/msg153417.html
>
> version 2:
> - Fix bus_info not consistent between media and V4L:
> https://www.spinics.net/lists/arm-kernel/msg717676.html
> - Propagation of format set on video node to the sub-devices
> chain connected on camera interface
>
> version 1:
> - Initial submission
>
> Hugues Fruchet (3):
> media: stm32-dcmi: improve sensor subdev naming
> media: stm32-dcmi: add media controller support
> media: stm32-dcmi: add support of several sub-devices
>
> drivers/media/platform/Kconfig | 2 +-
> drivers/media/platform/stm32/stm32-dcmi.c | 283 +++++++++++++++++++++++++-----
> 2 files changed, 236 insertions(+), 49 deletions(-)
>
next prev parent reply other threads:[~2019-08-07 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 12:56 [PATCH v4 0/3] DCMI bridge support Hugues Fruchet
2019-07-31 12:56 ` [PATCH v4 1/3] media: stm32-dcmi: improve sensor subdev naming Hugues Fruchet
2019-08-09 16:01 ` Sakari Ailus
2019-08-12 7:55 ` Hugues FRUCHET
2019-08-14 14:17 ` Hugues FRUCHET
2019-07-31 12:56 ` [PATCH v4 2/3] media: stm32-dcmi: add media controller support Hugues Fruchet
2019-07-31 12:56 ` [PATCH v4 3/3] media: stm32-dcmi: add support of several sub-devices Hugues Fruchet
2019-08-07 10:15 ` Hans Verkuil [this message]
2019-08-08 9:38 ` [PATCH v4 0/3] DCMI bridge support Hugues FRUCHET
2019-08-08 9:41 ` Hans Verkuil
2019-08-08 10:40 ` 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=28a2a9ac-d5b9-a312-616a-620e0385cf66@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=hugues.fruchet@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mchehab@kernel.org \
--cc=mickael.guene@st.com \
--cc=philippe.cornu@st.com \
--cc=sakari.ailus@linux.intel.com \
--cc=yannick.fertre@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;
as well as URLs for NNTP newsgroup(s).