From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, Benoit Parrot <bparrot@ti.com>
Subject: Re: [PATCH 2/2] media: i2c: Add OV1063x sensor driver
Date: Mon, 4 Jan 2021 14:47:00 +0200 [thread overview]
Message-ID: <20210104124700.GL11878@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20210104053945.12409-3-laurent.pinchart@ideasonboard.com>
Hi Laurent,
On Mon, Jan 04, 2021 at 07:39:45AM +0200, Laurent Pinchart wrote:
> diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig
> index 878f66ef2719..84a97989775e 100644
> --- a/drivers/media/i2c/Kconfig
> +++ b/drivers/media/i2c/Kconfig
> @@ -1050,6 +1050,18 @@ config VIDEO_OV9650
> This is a V4L2 sensor driver for the Omnivision
> OV9650 and OV9652 camera sensors.
>
> +config VIDEO_OV10633
> + tristate "OmniVision OV10633/OV10635 sensor support"
> + depends on I2C && VIDEO_V4L2
> + depends on GPIOLIB && OF
> + select MEDIA_CONTROLLER
> + select REGMAP_I2C
Should this be SCCB instead?
Likewise for the driver.
--
Sakari Ailus
next prev parent reply other threads:[~2021-01-04 12:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 5:39 [PATCH 0/2] media: Driver for OV1063x camera sensor Laurent Pinchart
2021-01-04 5:39 ` [PATCH 1/2] dt-bindings: media: Add bindings for OmniVision OV1063x sensors Laurent Pinchart
2021-01-05 17:49 ` Rob Herring
2021-01-12 9:31 ` Tomi Valkeinen
2021-01-04 5:39 ` [PATCH 2/2] media: i2c: Add OV1063x sensor driver Laurent Pinchart
2021-01-04 11:41 ` Sakari Ailus
2021-01-04 13:56 ` Laurent Pinchart
2021-12-06 22:23 ` Laurent Pinchart
2021-01-04 12:47 ` Sakari Ailus [this message]
2021-01-04 13:05 ` Laurent Pinchart
2021-01-04 13:55 ` Sakari Ailus
2021-01-12 13:32 ` Tomi Valkeinen
2021-01-14 5:32 ` Laurent Pinchart
2021-01-18 14:04 ` Tomi Valkeinen
2021-01-20 8:26 ` Laurent Pinchart
2021-01-20 11:52 ` Tomi Valkeinen
2021-02-08 14:18 ` Tomi Valkeinen
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=20210104124700.GL11878@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=bparrot@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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.