From: Jacopo Mondi <jacopo+renesas@jmondi.org>
To: kieran.bingham+renesas@ideasonboard.com,
laurent.pinchart@ideasonboard.com, niklas.soderlund@ragnatech.se
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
linux-renesas-soc@vger.kernel.org
Subject: [RFC 00/11] GMSL: Initial RDACM21 support
Date: Mon, 16 Dec 2019 18:16:09 +0100 [thread overview]
Message-ID: <20191216171620.372683-1-jacopo+renesas@jmondi.org> (raw)
Hello Renesas multimedia,
this series provides an initial support for RDACM21 camera modules,
which like the RDACM20 includes a MAX9271 serializer together with an OV490 ISP
chip and an OV10640 imager.
The series is based on the latest development from Kieran (gmsl/dev tag on
Kieran's kernel.org remote).
The series includes
- 4 fixes to be applied on top of Kieran's branch. Almost all of them have been
reported by the dt schema validator.
- 05/11 which converts the proposed RDACM20 bindings to yaml
- 06/11 which breaks out MAX9271 handling from RDACM20 driver
- 07->09 which modified the max9286 driver to support remote communications
with RDACM21 as well as RDACM20
- 10/11 which is an initial attempt to verify communication with RDACM21 by
reading the ISP chip ID.
At this stage, I augmented the RDACM20 driver to support both RDACM20 and 21.
This defeats the purpose of 06/11 but I'm not sure which direction is better
here, hence the RFC and the request for feedback.
One driver per camera module, or a single driver with multiple compatibles?
Please note that, as per RDACM20, the initial support for video capture
operations will be limited to 1 resolution and one format, as the ISP+imager
are configured by reading an on-chip EEPROM.
- Finally, enable RDACM21 in the Eagle DTS to test the example.
I'm very much interested in feedbacks on how to advance development for the
RDACM21 module.
Thanks
j
Jacopo Mondi (11):
fixup! DNI: Debug
fixup! arm64: dts: renesas: salvator-x: Add MAX9286 expansion board
fixup! arm64: dts: renesas: eagle: Provide Eagle FAKRA dynamic overlay
fixup! arm64: dts: renesas: eagle: Provide MAX9286 GMSL deserialiser
fixup! dt-bindings: media: i2c: Add bindings for IMI RDACM20
media: i2c: Break out max9271 from rdacm20 driver
media: i2c: max9286: Move notifiers operations
media: i2c: max9286: Move link setup to completion
media: i2c: max9286: Expand reverse chanenl amplitude
WIP: media: i2c: rdacm20: Add RDACM21 support
arm64: boot: dts: Eagle: Enable RDACM21
.../bindings/media/i2c/imi,rdacm20.txt | 66 ---
.../bindings/media/i2c/imi,rdacm20.yaml | 116 +++++
arch/arm64/boot/dts/renesas/eagle-fakra.dtsi | 12 +-
.../arm64/boot/dts/renesas/r8a77970-eagle.dts | 3 -
.../boot/dts/renesas/salvator-x-max9286.dtsi | 16 +-
drivers/media/i2c/Makefile | 3 +-
drivers/media/i2c/max9271.c | 212 +++++++++
drivers/media/i2c/max9271.h | 84 ++++
drivers/media/i2c/max9286.c | 168 ++++---
drivers/media/i2c/rdacm20.c | 433 +++++++-----------
10 files changed, 693 insertions(+), 420 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/media/i2c/imi,rdacm20.txt
create mode 100644 Documentation/devicetree/bindings/media/i2c/imi,rdacm20.yaml
create mode 100644 drivers/media/i2c/max9271.c
create mode 100644 drivers/media/i2c/max9271.h
--
2.24.0
next reply other threads:[~2019-12-16 17:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 17:16 Jacopo Mondi [this message]
2019-12-16 17:16 ` [RFC 01/11] fixup! DNI: Debug Jacopo Mondi
2019-12-16 22:34 ` Kieran Bingham
2019-12-16 17:16 ` [RFC 02/11] fixup! arm64: dts: renesas: salvator-x: Add MAX9286 expansion board Jacopo Mondi
2019-12-16 22:37 ` Kieran Bingham
2019-12-16 17:16 ` [RFC 03/11] fixup! arm64: dts: renesas: eagle: Provide Eagle FAKRA dynamic overlay Jacopo Mondi
2019-12-16 22:40 ` Kieran Bingham
2019-12-16 17:16 ` [RFC 04/11] fixup! arm64: dts: renesas: eagle: Provide MAX9286 GMSL deserialiser Jacopo Mondi
2019-12-16 22:41 ` Kieran Bingham
2019-12-16 17:16 ` [RFC 05/11] fixup! dt-bindings: media: i2c: Add bindings for IMI RDACM20 Jacopo Mondi
2019-12-16 22:42 ` Laurent Pinchart
2020-02-14 9:07 ` Kieran Bingham
2019-12-16 17:16 ` [RFC 06/11] media: i2c: Break out max9271 from rdacm20 driver Jacopo Mondi
2019-12-16 17:16 ` [RFC 07/11] media: i2c: max9286: Move notifiers operations Jacopo Mondi
2019-12-16 17:16 ` [RFC 08/11] media: i2c: max9286: Move link setup to completion Jacopo Mondi
2019-12-16 17:16 ` [RFC 09/11] media: i2c: max9286: Expand reverse chanenl amplitude Jacopo Mondi
2019-12-16 17:16 ` [RFC 10/11] WIP: media: i2c: rdacm20: Add RDACM21 support Jacopo Mondi
2019-12-16 17:16 ` [RFC 11/11] arm64: boot: dts: Eagle: Enable RDACM21 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=20191216171620.372683-1-jacopo+renesas@jmondi.org \
--to=jacopo+renesas@jmondi.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@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.