From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>,
laurent.pinchart@ideasonboard.com, niklas.soderlund@ragnatech.se
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [RFC 03/11] fixup! arm64: dts: renesas: eagle: Provide Eagle FAKRA dynamic overlay
Date: Mon, 16 Dec 2019 22:40:33 +0000 [thread overview]
Message-ID: <c8123fa1-b918-caad-4917-c6d694b49d8d@ideasonboard.com> (raw)
In-Reply-To: <20191216171620.372683-4-jacopo+renesas@jmondi.org>
Hi Jacopo,
On 16/12/2019 17:16, Jacopo Mondi wrote:
> Fixes DTC warning
> r8a77970-eagle.dt.yaml: camera@51: reg: [[81, 97]] is too short
Also agreed,
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Thanks - I'll squash this onto my gmsl/platform branch.
> ---
> arch/arm64/boot/dts/renesas/eagle-fakra.dtsi | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/renesas/eagle-fakra.dtsi b/arch/arm64/boot/dts/renesas/eagle-fakra.dtsi
> index 1f3aeb49e4d9..d30d0f25e60f 100644
> --- a/arch/arm64/boot/dts/renesas/eagle-fakra.dtsi
> +++ b/arch/arm64/boot/dts/renesas/eagle-fakra.dtsi
> @@ -63,7 +63,7 @@ i2c@0 {
>
> camera@51 {
> compatible = EAGLE_CAMERA0;
> - reg = <0x51 0x61>;
> + reg = <0x51>, <0x61>;
>
> port {
> fakra_con0: endpoint {
> @@ -80,7 +80,7 @@ i2c@1 {
>
> camera@52 {
> compatible = EAGLE_CAMERA1;
> - reg = <0x52 0x62>;
> + reg = <0x52>, <0x62>;
>
> port {
> fakra_con1: endpoint {
> @@ -97,7 +97,7 @@ i2c@2 {
>
> camera@53 {
> compatible = EAGLE_CAMERA2;
> - reg = <0x53 0x63>;
> + reg = <0x53>, <0x63>;
>
> port {
> fakra_con2: endpoint {
> @@ -114,7 +114,7 @@ i2c@3 {
>
> camera@54 {
> compatible = EAGLE_CAMERA3;
> - reg = <0x54 0x64>;
> + reg = <0x54>, <0x64>;
>
> port {
> fakra_con3: endpoint {
>
next prev parent reply other threads:[~2019-12-16 22:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 17:16 [RFC 00/11] GMSL: Initial RDACM21 support Jacopo Mondi
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 [this message]
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=c8123fa1-b918-caad-4917-c6d694b49d8d@ideasonboard.com \
--to=kieran.bingham+renesas@ideasonboard.com \
--cc=jacopo+renesas@jmondi.org \
--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 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).