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>
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 0/2] DCMI bridge support
Date: Mon, 1 Apr 2019 13:10:21 +0200 [thread overview]
Message-ID: <158aa8b9-e607-3630-0e13-ad10759d3468@xs4all.nl> (raw)
In-Reply-To: <1554111076-31471-1-git-send-email-hugues.fruchet@st.com>
Hi Hugues,
On 4/1/19 11:31 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.
Can you post the output of v4l2-compliance -m /dev/mediaX ?
Thanks!
Hans
>
> [1] https://www.spinics.net/lists/devicetree/msg278002.html
>
> Hugues Fruchet (2):
> 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 | 213 ++++++++++++++++++++++++------
> 2 files changed, 177 insertions(+), 38 deletions(-)
>
next prev parent reply other threads:[~2019-04-01 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 9:31 [PATCH 0/2] DCMI bridge support Hugues Fruchet
2019-04-01 9:31 ` [PATCH 1/2] media: stm32-dcmi: add media controller support Hugues Fruchet
2019-04-01 9:31 ` [PATCH 2/2] media: stm32-dcmi: add support of several sub-devices Hugues Fruchet
2019-04-01 11:10 ` Hans Verkuil [this message]
2019-04-01 13:08 ` [PATCH 0/2] DCMI bridge support Hugues FRUCHET
2019-04-01 13:30 ` Hans Verkuil
2019-04-02 9:17 ` 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=158aa8b9-e607-3630-0e13-ad10759d3468@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=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).