From: Jacopo Mondi <jacopo@jmondi.org>
To: mchehab@kernel.org, laurent.pinchart@ideasonboard.com,
maxime.ripard@bootlin.com, sam@elite-embedded.com,
jagan@amarulasolutions.com, festevam@gmail.com,
pza@pengutronix.de, steve_longerbeam@mentor.com,
hugues.fruchet@st.com, loic.poulain@linaro.org,
daniel@zonque.org
Cc: Jacopo Mondi <jacopo@jmondi.org>, linux-media@vger.kernel.org
Subject: [PATCH 0/2] media: ov5640: Fix set_timings and auto-exposure
Date: Wed, 18 Jul 2018 13:19:01 +0200 [thread overview]
Message-ID: <1531912743-24767-1-git-send-email-jacopo@jmondi.org> (raw)
Hello,
the ov5640 driver has received a lot of attentions recently.
Maxime and Sam tackled the clock tree handling and I tried to fix the MIPI
capture on i.MX6 platforms, but none of those patches ever made it to inclusion.
Although a few fixes have been circulating around those series, and it's my
opinion it is worth including them before any other developments takes place.
I'm sending here a re-work of a patch from Sam and Maxime to fix timings setup,
and a small fix for auto-exposure enabling/disabling operations.
Each patch has a comment, on which I would like to have some feedback on.
[1/1] has already received several acks on the mailing list, but never a
formal Reviewed-by or Tested-by, while [2/2] is new.
Thanks
j
Jacopo Mondi (2):
media: ov5640: Fix timings setup code
media: ov5640: Fix auto-exposure disabling
drivers/media/i2c/ov5640.c | 75 ++++++++++++++++++++--------------------------
1 file changed, 32 insertions(+), 43 deletions(-)
--
2.7.4
next reply other threads:[~2018-07-18 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 11:19 Jacopo Mondi [this message]
2018-07-18 11:19 ` [PATCH 1/2] media: ov5640: Fix timings setup code Jacopo Mondi
2018-07-18 12:22 ` Maxime Ripard
2018-08-07 8:53 ` Hugues FRUCHET
2018-08-14 15:41 ` jacopo mondi
2018-07-18 11:19 ` [PATCH 2/2] media: ov5640: Fix auto-exposure disabling Jacopo Mondi
2018-07-18 13:04 ` jacopo mondi
2018-08-07 8:53 ` Hugues FRUCHET
2018-08-14 15:45 ` jacopo mondi
2018-09-06 17:08 ` Laurent Pinchart
2018-09-07 7:56 ` jacopo mondi
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=1531912743-24767-1-git-send-email-jacopo@jmondi.org \
--to=jacopo@jmondi.org \
--cc=daniel@zonque.org \
--cc=festevam@gmail.com \
--cc=hugues.fruchet@st.com \
--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.