From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Subject: [GIT PULL for 5.1] Sensor driver patches
Date: Thu, 10 Jan 2019 16:35:50 +0200 [thread overview]
Message-ID: <20190110143550.q5jpdyqugzjf6ohn@valkosipuli.retiisi.org.uk> (raw)
Hi Mauro,
Here's the usual set of sensor driver patches for 5.1. Most notably,
there's a driver for ov9640 (originally using SoC camera framework) as well
as fixes for a number of other drivers.
Please pull.
The following changes since commit 1e0d0a5fd38192f23304ea2fc2b531fea7c74247:
media: s5p-mfc: fix incorrect bus assignment in virtual child device (2019-01-07 14:39:36 -0500)
are available in the git repository at:
ssh://linuxtv.org/git/sailus/media_tree.git tags/for-5.1-1-sign
for you to fetch changes up to 5008af8f2733a998819f2143caa9be9556bb3d06:
ipu3-cio2, dw9714: Remove Jian Xu's e-mail (2019-01-10 00:25:56 +0200)
----------------------------------------------------------------
sensor driver stuff for 5.1
----------------------------------------------------------------
Akinobu Mita (3):
media: ov2640: set default window and format code at probe time
media: ov2640: make VIDIOC_SUBDEV_G_FMT ioctl work with V4L2_SUBDEV_FORMAT_TRY
media: ov2640: set all mbus format field when G_FMT and S_FMT ioctls
Chen-Yu Tsai (2):
media: dt-bindings: media: sun6i: Separate H3 compatible from A31
media: sun6i: Add H3 compatible
Jacopo Mondi (1):
v4l2: i2c: ov7670: Fix PLL bypass register values
Loic Poulain (1):
media: ov5640: Add RAW bayer format support
Luca Ceresoli (1):
media: imx274: fix wrong order in test pattern menus
Manivannan Sadhasivam (2):
dt-bindings: media: i2c: Fix external clock frequency for OV5645
dt-bindings: media: i2c: Fix i2c address for OV5645 camera sensor
Petr Cvek (8):
media: soc_camera: ov9640: move ov9640 out of soc_camera
media: i2c: ov9640: drop soc_camera code and switch to v4l2_async
MAINTAINERS: add Petr Cvek as a maintainer for the ov9640 driver
media: i2c: ov9640: add missing SPDX identifiers
media: i2c: ov9640: change array index or length variables to unsigned
media: i2c: ov9640: add space before return for better clarity
media: i2c: ov9640: make array of supported formats constant
media: i2c: ov9640: fix missing error handling in probe
Sakari Ailus (4):
ipu3-cio2: Allow probe to succeed if there are no sensors connected
ov9640: Wrap long and unwrap short lines, align wrapped lines correctly
MAINTAINERS: Update reviewers for ipu3-cio2
ipu3-cio2, dw9714: Remove Jian Xu's e-mail
.../devicetree/bindings/media/i2c/ov5645.txt | 6 +-
.../devicetree/bindings/media/sun6i-csi.txt | 2 +-
MAINTAINERS | 7 +-
drivers/media/i2c/Kconfig | 7 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/dw9714.c | 2 +-
drivers/media/i2c/imx274.c | 2 +-
drivers/media/i2c/ov2640.c | 45 +-
drivers/media/i2c/ov5640.c | 58 +-
drivers/media/i2c/ov7670.c | 16 +-
drivers/media/i2c/ov9640.c | 777 +++++++++++++++++++++
drivers/media/i2c/ov9640.h | 207 ++++++
drivers/media/i2c/soc_camera/Kconfig | 6 +-
drivers/media/pci/intel/ipu3/ipu3-cio2.c | 5 +-
drivers/media/platform/sunxi/sun6i-csi/sun6i_csi.c | 1 +
15 files changed, 1103 insertions(+), 39 deletions(-)
create mode 100644 drivers/media/i2c/ov9640.c
create mode 100644 drivers/media/i2c/ov9640.h
--
Sakari Ailus
reply other threads:[~2019-01-10 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190110143550.q5jpdyqugzjf6ohn@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--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.