[RFC,v6,00/13] GMSL Renesas Platform Support
mbox series

Message ID 20191216102930.5867-1-kieran.bingham+renesas@ideasonboard.com
Headers show
  • GMSL Renesas Platform Support
Related show


Kieran Bingham Dec. 16, 2019, 10:29 a.m. UTC
Here is the current state of my GMSL v6 platform support which applies on top
of the recently posted MAX9286 driver.

These patches are marked RFC as they are not yet intended for integration, but
are posted to allow review and to build upon them with work that is currently
in progress by Jacopo.

This includes the RDACM20 driver which we still would like to refactor further
before posting to mainline (and we probably need max9286 to land or settle for
that too)

Included in this series are a few debug patches and workarounds.

I would specifically like to know if there is value in integrating:
  "[10/13] media: i2c: max9286: Introduce a debugfs layer"

directly into the max9286 driver, as I think there will be benefits to
developers to be able to expose state and statistics from this device.

The patch:
 "[01/13] media: i2c: max9286: Add GPIO chip controller"

Is currently blocked while we decide whether we should create this as an MFD
device - but expresses a means to expose the GPIO lines from the MAX9286 as a
GPIO controller directly.

These patches (and a few more specific debug patches, and configuration of 'my'
specific camera layout) are also available at:

 Branch: gmsl/dev



Jacopo Mondi (1):
  dt-bindings: media: i2c: Add bindings for IMI RDACM20

Kieran Bingham (10):
  media: i2c: max9286: Add GPIO chip controller
  media: i2c: Add RDACM20 driver
  arm64: dts: renesas: eagle: Provide MAX9286 GMSL deserialiser
  arm64: dts: renesas: eagle: Provide Eagle FAKRA dynamic overlay
  arm64: dts: renesas: eagle: Include Eagle FAKRA overlay
  arm64: dts: renesas: r8a7795-es1-salvator-x: Include MAX9286 8 Camera
    expansion board
  media: i2c: max9286: Introduce a debugfs layer
  [DNI:DEBUG] media: i2c: max9286: Add max9286_check_config_link()
  media: i2c: max9286: [Workaround] Hard delay while waiting to enable
    the V3M cameras
  media: i2c: max9286: [Workaround] 'device is bound'

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

Niklas Söderlund (1):
  arm64: dts: renesas: eagle: enable VIN

 .../bindings/media/i2c/imi,rdacm20.txt        |  66 ++
 .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
 MAINTAINERS                                   |  10 +
 arch/arm64/boot/dts/renesas/eagle-fakra.dtsi  | 128 +++
 .../dts/renesas/r8a7795-es1-salvator-x.dts    |   3 +
 .../arm64/boot/dts/renesas/r8a77970-eagle.dts | 154 +++
 .../boot/dts/renesas/salvator-x-max9286.dtsi  | 394 ++++++++
 drivers/media/i2c/Kconfig                     |  11 +
 drivers/media/i2c/Makefile                    |   1 +
 drivers/media/i2c/max9286.c                   | 291 +++++-
 drivers/media/i2c/rdacm20-ov10635.h           | 953 ++++++++++++++++++
 drivers/media/i2c/rdacm20.c                   | 613 +++++++++++
 12 files changed, 2624 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/media/i2c/imi,rdacm20.txt
 create mode 100644 arch/arm64/boot/dts/renesas/eagle-fakra.dtsi
 create mode 100644 arch/arm64/boot/dts/renesas/salvator-x-max9286.dtsi
 create mode 100644 drivers/media/i2c/rdacm20-ov10635.h
 create mode 100644 drivers/media/i2c/rdacm20.c