From: Rui Miguel Silva <rui.silva@linaro.org>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Rui Miguel Silva <rui.silva@linaro.org>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil@xs4all.nl, linux-media@vger.kernel.org,
Fabio Estevam <fabio.estevam@nxp.com>,
Ryan Harkin <ryan.harkin@linaro.org>
Subject: Re: [PATCH v7 2/2] media: ov2680: Add Omnivision OV2680 sensor driver
Date: Fri, 27 Jul 2018 13:20:21 +0100 [thread overview]
Message-ID: <m3r2jouayi.fsf@linaro.org> (raw)
In-Reply-To: <20180725141140.4n6ooxtqlnoeyqgs@valkosipuli.retiisi.org.uk>
Hi Sakari,
On Wed 25 Jul 2018 at 15:11, Sakari Ailus wrote:
> On Tue, Jul 03, 2018 at 03:08:03PM +0100, Rui Miguel Silva
> wrote:
>> This patch adds V4L2 sub-device driver for OV2680 image sensor.
>> The OV2680 is a 1/5" CMOS color sensor from Omnivision.
>> Supports output format: 10-bit Raw RGB.
>> The OV2680 has a single lane MIPI interface.
>>
>> The driver exposes following V4L2 controls:
>> - auto/manual exposure,
>> - exposure,
>> - auto/manual gain,
>> - gain,
>> - horizontal/vertical flip,
>> - test pattern menu.
>> Supported resolution are only: QUXGA, 720P, UXGA.
>>
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>
> Hi Rui,
>
> Could you provide a MAINTAINERS entry patch for the driver as
> well as the
> DT bindings? I'll squash that to the first one.
Sure, will send it and you can squash it after.
---
Cheers,
Rui
prev parent reply other threads:[~2018-07-27 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 14:08 [PATCH v7 0/2] media: Introduce Omnivision OV2680 driver Rui Miguel Silva
2018-07-03 14:08 ` [PATCH v7 1/2] media: ov2680: dt: Add bindings for OV2680 Rui Miguel Silva
2018-07-03 16:27 ` Rob Herring
2018-07-04 8:58 ` jacopo mondi
2018-07-04 15:51 ` Rui Miguel Silva
2018-07-05 20:11 ` Rob Herring
2018-07-03 14:08 ` [PATCH v7 2/2] media: ov2680: Add Omnivision OV2680 sensor driver Rui Miguel Silva
2018-07-25 14:11 ` Sakari Ailus
2018-07-27 12:20 ` Rui Miguel Silva [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=m3r2jouayi.fsf@linaro.org \
--to=rui.silva@linaro.org \
--cc=fabio.estevam@nxp.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ryan.harkin@linaro.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.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.