All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Chiranjeevi Rapolu <chiranjeevi.rapolu@intel.com>
Cc: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	jian.xu.zheng@intel.com, rajmohan.mani@intel.com,
	hyungwoo.yang@intel.com
Subject: Re: [PATCH] ov5670: Add Omnivision OV5670 5M sensor support
Date: Thu, 4 May 2017 11:50:22 +0300	[thread overview]
Message-ID: <20170504085021.GU7456@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <20170504084850.GT7456@valkosipuli.retiisi.org.uk>

On Thu, May 04, 2017 at 11:48:51AM +0300, Sakari Ailus wrote:
> On Wed, May 03, 2017 at 03:06:52PM -0700, Chiranjeevi Rapolu wrote:
> > Provides single source pad with up to 2576x1936 pixels at 10-bit raw
> > bayer format over MIPI CSI2 two lanes at 640Mbps/lane.
> > Supports up to 30fps at 5M pixels, up to 60fps at 1080p.
> > 
> > Signed-off-by: Chiranjeevi Rapolu <chiranjeevi.rapolu@intel.com>
> > ---
> >  drivers/media/i2c/Kconfig  |   11 +
> >  drivers/media/i2c/Makefile |    1 +
> >  drivers/media/i2c/ov5670.c | 3890 ++++++++++++++++++++++++++++++++++++++++++++
> >  3 files changed, 3902 insertions(+)
> >  create mode 100644 drivers/media/i2c/ov5670.c
> > 
> > diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig
> > index cee1dae..ded8485 100644
> > --- a/drivers/media/i2c/Kconfig
> > +++ b/drivers/media/i2c/Kconfig
> > @@ -531,6 +531,17 @@ config VIDEO_OV2659
> >  	  To compile this driver as a module, choose M here: the
> >  	  module will be called ov2659.
> >  
> > +config VIDEO_OV5670
> > +	tristate "OmniVision OV5670 sensor support"
> > +	depends on I2C && VIDEO_V4L2
> > +	depends on MEDIA_CAMERA_SUPPORT

select V4L2_FWNODE

-- 
Sakari Ailus
e-mail: sakari.ailus@iki.fi	XMPP: sailus@retiisi.org.uk

  reply	other threads:[~2017-05-04  8:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 22:06 [PATCH] ov5670: Add Omnivision OV5670 5M sensor support Chiranjeevi Rapolu
2017-05-04  8:48 ` Sakari Ailus
2017-05-04  8:50   ` Sakari Ailus [this message]
2017-05-26  1:21     ` Rapolu, Chiranjeevi
2017-05-26  1:19   ` Rapolu, Chiranjeevi
2017-05-26  8:29     ` Sakari Ailus
2017-06-14 18:27       ` Rapolu, Chiranjeevi
2017-05-25 22:42 ` [PATCH v2 1/1] [media] i2c: " chiranjeevi.rapolu
2017-05-26  6:42   ` kbuild test robot
2017-06-14  1:39   ` [PATCH v3 1/1] " chiranjeevi.rapolu
2017-06-14 13:47     ` [PATCH] i2c: fix platform_no_drv_owner.cocci warnings kbuild test robot
2017-06-14 13:47     ` [PATCH v3 1/1] i2c: Add Omnivision OV5670 5M sensor support kbuild test robot
2017-06-14 13:47     ` [PATCH] i2c: fix semicolon.cocci warnings kbuild test robot
2017-06-14 23:00     ` [PATCH v3 1/1] i2c: Add Omnivision OV5670 5M sensor support Sakari Ailus
2017-07-01 22:31       ` Rapolu, Chiranjeevi
2017-07-01 20:49     ` [PATCH v4 " chiranjeevi.rapolu
2017-07-07 22:24       ` Sakari Ailus
2017-07-14  4:35         ` Rapolu, Chiranjeevi
2017-07-07 22:48       ` Mani, Rajmohan
2017-07-14  4:36         ` Rapolu, Chiranjeevi
2017-07-14  1:51     ` [PATCH v5 " Chiranjeevi Rapolu
2017-07-14 10:43       ` Sakari Ailus
2021-07-08  8:10       ` Laurent Pinchart

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=20170504085021.GU7456@valkosipuli.retiisi.org.uk \
    --to=sakari.ailus@iki.fi \
    --cc=chiranjeevi.rapolu@intel.com \
    --cc=hyungwoo.yang@intel.com \
    --cc=jian.xu.zheng@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=rajmohan.mani@intel.com \
    --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.