From: jacopo mondi <jacopo@jmondi.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Sam Bobrowicz <sam@elite-embedded.com>,
jagan@amarulasolutions.com, festevam@gmail.com,
pza@pengutronix.de, steve_longerbeam@mentor.com,
Hugues Fruchet <hugues.fruchet@st.com>,
Daniel Mack <daniel@zonque.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v3 0/2] media: i2c: ov5640: Re-work MIPI startup sequence
Date: Wed, 29 Aug 2018 15:52:44 +0200 [thread overview]
Message-ID: <20180829135244.GI3566@w540> (raw)
In-Reply-To: <CAMZdPi9rdO88=m3BXtUZFUheAaS__Jx58NhYwi7L+sCmhx8apA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2201 bytes --]
Hello Loic,
On Tue, Aug 28, 2018 at 05:08:07PM +0200, Loic Poulain wrote:
> On 15 August 2018 at 12:28, Jacopo Mondi <jacopo+renesas@jmondi.org> wrote:
> > Hello ov5640 people,
> > this driver has received a lot of attention recently, and this series aims
> > to fix the CSI-2 interface startup on i.Mx6Q platforms.
> >
> > Please refer to the v2 cover letters for more background informations:
> > https://www.mail-archive.com/linux-media@vger.kernel.org/msg133420.html
> >
> > This two patches alone allows the MIPI interface to startup properly, but in
> > order to capture good images (good as in 'not completely black') exposure and
> > gain handling should be fixed too.
> > Hugues Fruchet has a series in review that fixes that issues:
> > [PATCH v2 0/5] Fix OV5640 exposure & gain
> >
> > And I have re-based it on top of this two fixes here:
> > git://jmondi.org/linux ov5640/timings_exposure
> >
> > Steve Longerbeam tested that branch on his I.MX6q SabreSD board and confirms he
> > can now capture frames (I added his Tested-by tag to this patches). I have
> > verified the same on Engicam iCore I.MX6q and an Intel Atom based board.
> >
> > Ideally I would like to have these two fixes merged, and Hugues' ones then
> > applied on top. Of course, more testing on other platforms using CSI-2 is very
> > welcome.
> >
> > Thanks
> > j
> >
> > v2 -> v3:
> > - patch [2/2] was originally sent in a different series, compared to v2 it
> > removes entries from the blob array instead of adding more.
> >
> > Jacopo Mondi (2):
> > media: ov5640: Re-work MIPI startup sequence
> > media: ov5640: Fix timings setup code
> >
> > drivers/media/i2c/ov5640.c | 141 +++++++++++++++++++++++++++++----------------
> > 1 file changed, 92 insertions(+), 49 deletions(-)
> >
> > --
> > 2.7.4
> >
>
> Thanks for this work.
> I've just tested this with a dragonboard-410c (MICPI/CSI) + OV5640 sensor.
> It works on my side for 1280*720, 1920*1080 and 2592*1944 formats.
>
> Tested-by: Loic Poulain <loic.poulain@linaro.org>
Thanks for testing!
Just out of curiosity, did the dragonboard-410c CSI-2 interface had
issues poperly starting up before this series like the i.MX6q did?
Thanks
j
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2018-08-29 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 10:28 [PATCH v3 0/2] media: i2c: ov5640: Re-work MIPI startup sequence Jacopo Mondi
2018-08-15 10:28 ` [PATCH v3 1/2] media: " Jacopo Mondi
2018-09-04 17:22 ` Loic Poulain
2018-09-06 7:48 ` jacopo mondi
2018-09-06 8:13 ` Loic Poulain
2018-09-06 8:48 ` jacopo mondi
2018-09-07 8:22 ` Loic Poulain
2018-09-14 9:38 ` jacopo mondi
2018-08-15 10:28 ` [PATCH v3 2/2] media: ov5640: Fix timings setup code Jacopo Mondi
2018-08-28 15:08 ` [PATCH v3 0/2] media: i2c: ov5640: Re-work MIPI startup sequence Loic Poulain
2018-08-29 13:52 ` jacopo mondi [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=20180829135244.GI3566@w540 \
--to=jacopo@jmondi.org \
--cc=daniel@zonque.org \
--cc=festevam@gmail.com \
--cc=hugues.fruchet@st.com \
--cc=jacopo+renesas@jmondi.org \
--cc=jagan@amarulasolutions.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab@kernel.org \
--cc=pza@pengutronix.de \
--cc=sam@elite-embedded.com \
--cc=steve_longerbeam@mentor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.