linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacopo Mondi <jacopo+renesas@jmondi.org>
To: "Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
	"Rob Herring" <robh+dt@kernel.org>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
	linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/8] arm64: dts: renesas: Enable GMSL on Eagle and Condor
Date: Thu, 22 Jul 2021 11:12:31 +0200	[thread overview]
Message-ID: <20210722091239.26451-1-jacopo+renesas@jmondi.org> (raw)

Hello,
   here we go again with the attempt to try enable GMSL for Eagle and this time
also Condor board.

v5 highlighted an issue with the integration of RDACM20 which shown failures at
start streaming time due to conflicts with i2c writes performed by the embedded
microcontroller. A new patch
- media: i2c: rdacm20: Re-program chip address earlier
is aimed to fix the issue by reducing the collision window by re-programming the
chip address earlier. All capture session I've run seems stable now.

Compared to v5 integration for the Condor board is now included.

Condor has 2 GMSL channels, something the current version of the MAX9286 driver
does not support. However the DTS integration can be upstreamed but a single
channel can be used at a time.

Support for Condor required a reword of what was called eagle-gmsl.dtsi in v5
and is now called gmsl-cameras.dtsi to expand support for the secondary GMSL
channel.

Integration of the new "maxim,gpio-poc" property required for Eagle/Condor is
fully reviewed and can be eventually fast-tracked.

The series is based on:
https://patchwork.linuxtv.org/project/linux-media/list/?series=5847
and has been tested on Eagle V3H board, while only compile tested for Condor.

Thanks
   j

Jacopo Mondi (5):
  dt-bindings: media: max9286: Re-indent example
  dt-bindings: media: max9286: Define 'maxim,gpio-poc'
  media: i2c: max9286: Use "maxim,gpio-poc" property
  media: i2c: rdacm20: Re-program chip address earlier
  arm64: dts: renesas: condor: Enable MAX9286

Kieran Bingham (3):
  arm64: dts: renesas: eagle: Enable MAX9286
  arm64: dts: renesas: Add GMSL cameras .dtsi
  DNI: arm64: dts: renesas: eagle: Include eagle-gmsl

 .../bindings/media/i2c/maxim,max9286.yaml     | 275 +++++++++------
 arch/arm64/boot/dts/renesas/gmsl-cameras.dtsi | 332 ++++++++++++++++++
 .../arm64/boot/dts/renesas/r8a77970-eagle.dts | 112 ++++++
 .../boot/dts/renesas/r8a77980-condor.dts      | 193 ++++++++++
 drivers/media/i2c/max9286.c                   | 125 +++++--
 drivers/media/i2c/rdacm20.c                   |  10 +-
 6 files changed, 906 insertions(+), 141 deletions(-)
 create mode 100644 arch/arm64/boot/dts/renesas/gmsl-cameras.dtsi

--
2.32.0


             reply	other threads:[~2021-07-22  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22  9:12 Jacopo Mondi [this message]
2021-07-22  9:12 ` [PATCH v6 1/8] dt-bindings: media: max9286: Re-indent example Jacopo Mondi
2021-07-22  9:12 ` [PATCH v6 2/8] dt-bindings: media: max9286: Define 'maxim,gpio-poc' Jacopo Mondi
2021-07-22  9:12 ` [PATCH v6 3/8] media: i2c: max9286: Use "maxim,gpio-poc" property Jacopo Mondi
2021-07-22  9:12 ` [PATCH v6 4/8] media: i2c: rdacm20: Re-program chip address earlier Jacopo Mondi
2021-07-22  9:12 ` [PATCH v6 5/8] arm64: dts: renesas: condor: Enable MAX9286 Jacopo Mondi
2021-07-22  9:12 ` [PATCH v6 6/8] arm64: dts: renesas: eagle: " Jacopo Mondi
2021-07-22  9:12 ` [PATCH v6 7/8] arm64: dts: renesas: Add GMSL cameras .dtsi Jacopo Mondi
2021-07-22  9:12 ` [PATCH v6 8/8] DNI: arm64: dts: renesas: eagle: Include eagle-gmsl 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=20210722091239.26451-1-jacopo+renesas@jmondi.org \
    --to=jacopo+renesas@jmondi.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=kieran.bingham@ideasonboard.com \
    --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=magnus.damm@gmail.com \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=robh+dt@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 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).