devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shunqian Zheng <zhengsq@rock-chips.com>
To: mchehab@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	ddl@rock-chips.com, tfiga@chromium.org,
	Shunqian Zheng <zhengsq@rock-chips.com>
Subject: [PATCH v4 0/5] Add supports for OV2685 and OV5695 sensors
Date: Tue,  9 Jan 2018 22:48:19 +0800	[thread overview]
Message-ID: <1515509304-15941-1-git-send-email-zhengsq@rock-chips.com> (raw)

This adds the OV2685 and OV5695 sensor supports.

Mainly changes of v4 are addressing the comments from Sakari,
including,
 - Put dt binding before driver in series
 - Add MAINTAINERS entries
 - Use regulator_bulk_*()
 - Fix the pm_runtime_* in probe()
 - Fix the typo of 2685 0x3008/0x3010 regs

Shunqian Zheng (5):
  dt-bindings: media: Add bindings for OV5695
  media: ov5695: add support for OV5695 sensor
  dt-bindings: media: Add bindings for OV2685
  media: ov2685: add support for OV2685 sensor
  [media] MAINTAINERS: add entries for OV2685/OV5695 sensor drivers

 .../devicetree/bindings/media/i2c/ov2685.txt       |   41 +
 .../devicetree/bindings/media/i2c/ov5695.txt       |   41 +
 MAINTAINERS                                        |   14 +
 drivers/media/i2c/Kconfig                          |   23 +
 drivers/media/i2c/Makefile                         |    2 +
 drivers/media/i2c/ov2685.c                         |  842 ++++++++++++
 drivers/media/i2c/ov5695.c                         | 1396 ++++++++++++++++++++
 7 files changed, 2359 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/media/i2c/ov2685.txt
 create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5695.txt
 create mode 100644 drivers/media/i2c/ov2685.c
 create mode 100644 drivers/media/i2c/ov5695.c

-- 
1.9.1

             reply	other threads:[~2018-01-09 14:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 14:48 Shunqian Zheng [this message]
     [not found] ` <1515509304-15941-1-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2018-01-09 14:48   ` [PATCH v4 1/5] dt-bindings: media: Add bindings for OV5695 Shunqian Zheng
2018-01-09 14:48   ` [PATCH v4 5/5] [media] MAINTAINERS: add entries for OV2685/OV5695 sensor drivers Shunqian Zheng
     [not found]     ` <1515509304-15941-6-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2018-01-09 22:33       ` Sakari Ailus
2018-01-12  1:52         ` Shunqian Zheng
     [not found]           ` <7e73473b-1c72-2fcd-4c55-e2c6c87550f6-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2018-01-12  7:30             ` Sakari Ailus
2018-01-09 14:48 ` [PATCH v4 2/5] media: ov5695: add support for OV5695 sensor Shunqian Zheng
     [not found]   ` <1515509304-15941-3-git-send-email-zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2018-01-09 16:54     ` Baruch Siach
2018-01-10  1:08       ` Shunqian Zheng
2018-01-09 14:48 ` [PATCH v4 3/5] dt-bindings: media: Add bindings for OV2685 Shunqian Zheng
2018-01-09 14:48 ` [PATCH v4 4/5] media: ov2685: add support for OV2685 sensor Shunqian Zheng

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=1515509304-15941-1-git-send-email-zhengsq@rock-chips.com \
    --to=zhengsq@rock-chips.com \
    --cc=ddl@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tfiga@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).