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: Mickael GUENE <mickael.guene@st.com>,
linux-kernel@vger.kernel.org,
Philippe CORNU <philippe.cornu@st.com>,
Yannick Fertre <yannick.fertre@st.com>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v7 0/4] DCMI bridge support
Date: Mon, 19 Aug 2019 10:43:09 +0200 [thread overview]
Message-ID: <0cd073d9-3d25-9e22-f243-f72e395e9e96@xs4all.nl> (raw)
In-Reply-To: <1566204081-19051-1-git-send-email-hugues.fruchet@st.com>
On 8/19/19 10:41 AM, 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 7:
> - minor fix on 80 char trace message
v6 is already in a pending PR. I don't really want to make a new
PR just for a 80 char warning.
It can always be done in a follow-up patch.
Regards,
Hans
>
> version 6:
> - As per Sakari remark: add a FIXME explaining that this
> version only supports subdevices which expose RGB & YUV
> "parallel form" mbus code (_2X8)
> - Add some trace around subdev_call(s_fmt) error & format
> changes to debug subdev which only expose serial mbus code
> - Conform to "<name>":<pad index> when tracing subdev infos
>
> version 5:
> - Remove remaining Change-Id
> - Add Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
>
> 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 (4):
> media: stm32-dcmi: improve sensor subdev naming
> media: stm32-dcmi: trace the supported fourcc/mbus_code
> 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 | 318 +++++++++++++++++++++++++-----
> 2 files changed, 268 insertions(+), 52 deletions(-)
>
_______________________________________________
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:[~2019-08-19 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 8:41 [PATCH v7 0/4] DCMI bridge support Hugues Fruchet
2019-08-19 8:41 ` [PATCH v7 1/4] media: stm32-dcmi: improve sensor subdev naming Hugues Fruchet
2019-08-19 8:41 ` [PATCH v7 2/4] media: stm32-dcmi: trace the supported fourcc/mbus_code Hugues Fruchet
2019-08-19 8:41 ` [PATCH v7 3/4] media: stm32-dcmi: add media controller support Hugues Fruchet
2019-08-19 8:41 ` [PATCH v7 4/4] media: stm32-dcmi: add support of several sub-devices Hugues Fruchet
2019-08-19 8:43 ` Hans Verkuil [this message]
2019-08-19 9:13 ` [PATCH v7 0/4] DCMI bridge support Hugues FRUCHET
2019-08-20 8:09 ` 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=0cd073d9-3d25-9e22-f243-f72e395e9e96@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).