All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacopo Mondi <jacopo+renesas@jmondi.org>
To: kieran.bingham+renesas@ideasonboard.com,
	laurent.pinchart+renesas@ideasonboard.com,
	niklas.soderlund+renesas@ragnatech.se
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
	linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Hyun Kwon <hyunk@xilinx.com>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: [PATCH v2 0/7] media: i2c: Add support for RDACM21 camera module
Date: Thu, 15 Oct 2020 20:27:03 +0200	[thread overview]
Message-ID: <20201015182710.54795-1-jacopo+renesas@jmondi.org> (raw)

Hello,
  v2 of support for RDACM21 camera module in this series.

Patch [1/7] introduces the camera module driver.
Only change compared to v1:
- Increase pixel clock to 55MHz

From [2/7] to [5/7] there's a proposal of a possible way to support
both RDACM20 and RDACM21 with the same deserializer driver.
See v1 cover letter for details:
https://www.spinics.net/lists/linux-renesas-soc/msg52886.html

I have tested on Eagle V3M with 4 RDACM21, but the whole point of
this series is to retain compatibility with RDACM20.

For this reason I have included 2 patches on top, not intended for merge
that re-propose DTS support for the MAXIM max9286 expansion board connected
to Salvator-X and add the newly introduced property to the DTS file.

Kieran, I know you have a working setup with RDACM20, the final two patches are
meant for ease your testing. Can you give this series a spin ?
For your convenience I pushed a branch
git://jmondi.org/linux #gmsl/jmondi/renesas-drivers-2020-10-13-v5.9/rdacm21_high-threshold

Series based on latest renesas-drivers tag: renesas-drivers-2020-10-13-v5.9

If I get a confirmation this setup works on Salvator-X, I'll submit the new
property for inclusion to devicetree people, which I have left out at the
moment.

Thanks
  j

Jacopo Mondi (6):
  media: i2c: Add driver for RDACM21 camera module
  dt-bindings: media: max9286: Document 'maxim,high-threshold'
  media: i2c: max9286: Break-out reverse channel setup
  media: i2c: max9286: Make channel amplitude programmable
  media: i2c: max9286: Configure reverse channel amplitude
  [DNI] arm64: dts: renesas: salvator-x-max9286: Use high-threshold

Laurent Pinchart (1):
  arm64: dts: renesas: salvator-x: Add MAX9286 expansion board

 .../bindings/media/i2c/maxim,max9286.yaml     |  15 +
 MAINTAINERS                                   |  12 +
 .../boot/dts/renesas/salvator-x-max9286.dtsi  | 396 +++++++++++++
 drivers/media/i2c/Kconfig                     |  13 +
 drivers/media/i2c/Makefile                    |   2 +
 drivers/media/i2c/max9286.c                   |  54 +-
 drivers/media/i2c/rdacm21.c                   | 538 ++++++++++++++++++
 7 files changed, 1020 insertions(+), 10 deletions(-)
 create mode 100644 arch/arm64/boot/dts/renesas/salvator-x-max9286.dtsi
 create mode 100644 drivers/media/i2c/rdacm21.c

--
2.28.0


             reply	other threads:[~2020-10-15 16:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15 18:27 Jacopo Mondi [this message]
2020-10-15 18:27 ` [PATCH v2 1/7] media: i2c: Add driver for RDACM21 camera module Jacopo Mondi
2020-10-15 18:27 ` [PATCH v2 2/7] dt-bindings: media: max9286: Document 'maxim,high-threshold' Jacopo Mondi
2020-10-15 18:27 ` [PATCH v2 3/7] media: i2c: max9286: Break-out reverse channel setup Jacopo Mondi
2020-10-15 19:53   ` Kieran Bingham
2020-10-15 18:27 ` [PATCH v2 4/7] media: i2c: max9286: Make channel amplitude programmable Jacopo Mondi
2020-10-15 20:00   ` Kieran Bingham
2020-10-16  8:08   ` Sergei Shtylyov
2020-10-15 18:27 ` [PATCH v2 5/7] media: i2c: max9286: Configure reverse channel amplitude Jacopo Mondi
2020-10-15 19:52   ` Kieran Bingham
2020-10-16  9:54     ` Jacopo Mondi
2020-10-15 18:27 ` [PATCH v2 6/7] [DNI] arm64: dts: renesas: salvator-x: Add MAX9286 expansion board Jacopo Mondi
2020-10-15 18:27 ` [PATCH v2 7/7] [DNI] arm64: dts: renesas: salvator-x-max9286: Use high-threshold 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=20201015182710.54795-1-jacopo+renesas@jmondi.org \
    --to=jacopo+renesas@jmondi.org \
    --cc=hyunk@xilinx.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    /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.