linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacopo Mondi <jacopo+renesas@jmondi.org>
To: hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com,
	sakari.ailus@iki.fi, mchehab@kernel.org
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
	linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Renesas CEU: SH7724 ECOVEC + Aptina mt9t112
Date: Fri,  2 Mar 2018 17:35:36 +0100	[thread overview]
Message-ID: <1520008541-3961-1-git-send-email-jacopo+renesas@jmondi.org> (raw)

Hello,
   now that CEU has been picked up for inclusion in v4.17, we can start moving
users of old sh_mobile_ceu_camera driver to use the newly introduced one.

Migo-R has been first, now it's SH7724 ECOVEC board turn.

ECOVEC has a camera board with two MT9T112 image sensor and one TW9910 video
decoder input. This series moves the mt9t112 driver away from soc_camera
framework and remove dependencies on it in mach-ecovec board code.

As per Migo-R, memory for CEU is reserved using memblocks APIs and declared
as DMA-capable in board code, power up/down routines have been removed from
board code, and GPIOs lookup table registered for sensor drivers.

As in the previous series, still no code has been removed or changed in
drivers/media/i2c/soc_camera/ until we do not remove all dependencies on it
in all board files.

Hans, since you asked me to add frame rate interval support for ov772x I expect
to receive the same request for mt9t112. Unfortunately I do not have access to
register level documentation, nor can perform any testing as I don't have the
camera modules. For the same reason I cannot run any v4l2-compliance test on
that driver, but just make sure the ECOVEC boots cleanly with the new board
file. I'm in favour of moving the driver to staging if you think that's the case.

Series based on media-tree master, and as per Migo-R I would ask SH arch/
changes to go through media tree as SH maintainers are un-responsive.

Thanks
  j

Jacopo Mondi (5):
  media: i2c: Copy mt9t112 soc_camera sensor driver
  media: i2c: mt9t112: Remove soc_camera dependencies
  media: i2c: mt9t112: Fix code style issues
  arch: sh: ecovec: Use new renesas-ceu camera driver
  media: MAINTAINERS: Add entry for Aptina MT9T112

 MAINTAINERS                            |    7 +
 arch/sh/boards/mach-ecovec24/setup.c   |  338 +++++-----
 arch/sh/kernel/cpu/sh4a/clock-sh7724.c |    4 +-
 drivers/media/i2c/Kconfig              |   11 +
 drivers/media/i2c/Makefile             |    1 +
 drivers/media/i2c/mt9t112.c            | 1136 ++++++++++++++++++++++++++++++++
 include/media/i2c/mt9t112.h            |   17 +-
 7 files changed, 1333 insertions(+), 181 deletions(-)
 create mode 100644 drivers/media/i2c/mt9t112.c

--
2.7.4

             reply	other threads:[~2018-03-02 16:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 16:35 Jacopo Mondi [this message]
2018-03-02 16:35 ` [PATCH 1/5] media: i2c: Copy mt9t112 soc_camera sensor driver Jacopo Mondi
2018-03-02 16:35 ` [PATCH 2/5] media: i2c: mt9t112: Remove soc_camera dependencies Jacopo Mondi
2018-03-02 16:35 ` [PATCH 3/5] media: i2c: mt9t112: Fix code style issues Jacopo Mondi
2018-03-02 16:35 ` [PATCH 4/5] arch: sh: ecovec: Use new renesas-ceu camera driver Jacopo Mondi
2018-03-02 16:35 ` [PATCH 5/5] media: MAINTAINERS: Add entry for Aptina MT9T112 Jacopo Mondi
2018-03-11 20:15   ` Sakari Ailus
2018-03-12 12:02     ` jacopo mondi
2018-03-10 17:57 ` [PATCH 0/5] Renesas CEU: SH7724 ECOVEC + Aptina mt9t112 Hans Verkuil
2018-03-10 18:20   ` jacopo mondi

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=1520008541-3961-1-git-send-email-jacopo+renesas@jmondi.org \
    --to=jacopo+renesas@jmondi.org \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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).