From: Hugues FRUCHET <hugues.fruchet@st.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
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" <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-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH v7 0/4] DCMI bridge support
Date: Tue, 20 Aug 2019 08:09:58 +0000 [thread overview]
Message-ID: <228dfbae-1e73-2a9c-f6f0-799a07cd31bc@st.com> (raw)
In-Reply-To: <5d36f437-0de5-1aa0-09bf-51d3a415ad2f@st.com>
Hi Sakari, Hans,
st-mipid02 changes are already merged, thanks Sakari and sorry for
disturbance.
Still remain the V4L2_CID_LINK_FREQ for OV5640.
On 8/19/19 11:13 AM, Hugues FRUCHET wrote:
> Hi Hans, Sakari,
>
> OK to push separately the 80 char fix.
>
> There was pending related changes on st-mipid02 and ov5640 (listed
> below), do you think it's possible to take them also ?
>
>
> media: st-mipid02: add support of V4L2_CID_LINK_FREQ
> https://patchwork.linuxtv.org/patch/56969/
> State Accepted
>
> [v2,1/3] media: st-mipid02: add support of RGB565
> https://patchwork.linuxtv.org/patch/56970/
> State Accepted
>
> [v2,2/3] media: st-mipid02: add support of YUYV8 and UYVY8
> https://patchwork.linuxtv.org/patch/56971/
> State Accepted
>
> [v2,3/3] media: st-mipid02: add support of JPEG
> https://patchwork.linuxtv.org/patch/56973/
> State Accepted
>
>
> [v2] media: ov5640: add support of V4L2_CID_LINK_FREQ
> https://patchwork.linuxtv.org/patch/57215/
> State Changes Requested
> => This change is needed to make it work the whole setup.
> => I don't know what to change here, even if this 384MHz fixed value
> seems strange, it works fine on my setup, on my opinion it's better than
> nothing. We could come back on this later on when other OV5640 CSI
> interfaces will require V4L2_CID_LINK_FREQ value.
>
> Sakari, what do you think about this ?
>
>
> BR,
> Hugues.
BR,
Hugues.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-08-20 8:10 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 ` [PATCH v7 0/4] DCMI bridge support Hans Verkuil
2019-08-19 9:13 ` Hugues FRUCHET
2019-08-20 8:09 ` Hugues FRUCHET [this message]
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=228dfbae-1e73-2a9c-f6f0-799a07cd31bc@st.com \
--to=hugues.fruchet@st.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=hverkuil@xs4all.nl \
--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