From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Samuel Bobrowicz <sam@elite-embedded.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Mylene Josserand <mylene.josserand@bootlin.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hugues Fruchet <hugues.fruchet@st.com>
Subject: Re: [PATCH v2 00/12] media: ov5640: Misc cleanup and improvements
Date: Tue, 17 Apr 2018 18:01:22 +0200 [thread overview]
Message-ID: <20180417160122.rfdlbdafmivgi5cd@flea> (raw)
In-Reply-To: <CAFwsNOF6t-AAXr8gEBLnCx2OF-PjAWALhsJRVYHSdnaP9hswWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Mon, Apr 16, 2018 at 04:22:39PM -0700, Samuel Bobrowicz wrote:
> I've been digging around the ov5640.c code for a few weeks now, these
> look like some solid improvements. I'll give them a shot and let you
> know how they work.
Great, thanks!
> On that note, I'm bringing up a module that uses dual lane MIPI with a
> 12MHz fixed oscillator for xclk (Digilent's Pcam 5c). The mainline
> version of the driver seems to only support xclk of 22MHz (or maybe
> 24MHz), despite allowing xclk values from 6-24MHz. Will any of these
> patches add support for a 12MHz xclk while in MIPI mode?
My setup has a 24MHz crystal, and work with a parallel bus so I
haven't been able to test yours. However, yeah, I guess my patches
will improve your situation a lot.
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-17 16:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 12:36 [PATCH v2 00/12] media: ov5640: Misc cleanup and improvements Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 01/12] media: ov5640: Add auto-focus feature Maxime Ripard
2018-04-19 10:36 ` Laurent Pinchart
2018-04-20 19:10 ` Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 02/12] media: ov5640: Add light frequency control Maxime Ripard
2018-04-19 9:44 ` Laurent Pinchart
2018-04-20 19:04 ` Maxime Ripard
2018-04-24 11:55 ` Sakari Ailus
2018-04-16 12:36 ` [PATCH v2 03/12] media: ov5640: Don't force the auto exposure state at start time Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 04/12] media: ov5640: Init properly the SCLK dividers Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 05/12] media: ov5640: Change horizontal and vertical resolutions name Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 06/12] media: ov5640: Add horizontal and vertical totals Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 07/12] media: ov5640: Program the visible resolution Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 08/12] media: ov5640: Adjust the clock based on the expected rate Maxime Ripard
2018-04-24 7:21 ` Sakari Ailus
2018-04-24 19:36 ` Maxime Ripard
2018-05-02 21:44 ` Sakari Ailus
2018-04-16 12:36 ` [PATCH v2 09/12] media: ov5640: Compute the clock rate at runtime Maxime Ripard
2018-04-16 12:36 ` [PATCH v2 10/12] media: ov5640: Enhance FPS handling Maxime Ripard
2018-04-16 12:37 ` [PATCH v2 11/12] media: ov5640: Add 60 fps support Maxime Ripard
2018-05-15 13:33 ` Hugues FRUCHET
2018-05-17 8:52 ` Maxime Ripard
2018-05-17 13:29 ` Hugues FRUCHET
2018-05-18 9:05 ` Maxime Ripard
2018-04-16 12:37 ` [PATCH v2 12/12] media: ov5640: Remove duplicate auto-exposure setup Maxime Ripard
2018-04-16 23:22 ` [PATCH v2 00/12] media: ov5640: Misc cleanup and improvements Samuel Bobrowicz
2018-04-17 16:01 ` Maxime Ripard [this message]
2018-04-18 23:39 ` Samuel Bobrowicz
2018-04-19 12:32 ` Maxime Ripard
2018-04-24 22:11 ` Sam Bobrowicz
2018-04-25 19:53 ` Maxime Ripard
2018-04-27 9:27 ` Laurent Pinchart
2018-05-02 18:11 ` Sam Bobrowicz
2018-05-03 15:16 ` Maxime Ripard
2018-05-04 10:01 ` Loic Poulain
2018-05-04 21:13 ` Sam Bobrowicz
2018-05-07 8:10 ` Maxime Ripard
2018-05-04 7:26 ` Loic Poulain
2018-05-04 21:26 ` Sam Bobrowicz
2018-05-08 1:00 ` Sam Bobrowicz
2018-05-17 8:50 ` Maxime Ripard
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=20180417160122.rfdlbdafmivgi5cd@flea \
--to=maxime.ripard@bootlin.com \
--cc=hans.verkuil@cisco.com \
--cc=hugues.fruchet@st.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mylene.josserand@bootlin.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sam@elite-embedded.com \
--cc=thomas.petazzoni@bootlin.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