From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH/RFC 1/2] media: dt-bindings: adv748x: Fix decimal unit addresses
Date: Thu, 16 Aug 2018 09:40:50 +0100 [thread overview]
Message-ID: <ec3c39d5-17a6-50f2-b54d-d30c89aadf1f@ideasonboard.com> (raw)
In-Reply-To: <1528984088-24801-2-git-send-email-geert+renesas@glider.be>
Hi Geert,
On 14/06/18 14:48, Geert Uytterhoeven wrote:
> With recent dtc and W=1:
>
> Warning (graph_port): video-receiver@70/port@10: graph node unit address error, expected "a"
> Warning (graph_port): video-receiver@70/port@11: graph node unit address error, expected "b"
>
> Unit addresses are always hexadecimal (without prefix), while the bases
> of reg property values depend on their prefixes.
>
> Fixes: e69595170b1cad85 ("media: adv748x: Add adv7481, adv7482 bindings")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> Documentation/devicetree/bindings/media/i2c/adv748x.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/adv748x.txt b/Documentation/devicetree/bindings/media/i2c/adv748x.txt
> index 21ffb5ed818302ff..54d1d3bc186949fa 100644
> --- a/Documentation/devicetree/bindings/media/i2c/adv748x.txt
> +++ b/Documentation/devicetree/bindings/media/i2c/adv748x.txt
> @@ -73,7 +73,7 @@ Example:
> };
> };
>
> - port@10 {
> + port@a {
> reg = <10>;
>
> adv7482_txa: endpoint {
> @@ -83,7 +83,7 @@ Example:
> };
> };
>
> - port@11 {
> + port@b {
> reg = <11>;
>
> adv7482_txb: endpoint {
>
Just looking back through these patches, to make sure they get integrated.
Having read yours and Robs responses, I do agree that this is a correct fix.
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
next prev parent reply other threads:[~2018-08-16 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 13:48 [PATCH/RFC 0/2] media: adv748x: Fix decimal unit addresses Geert Uytterhoeven
2018-06-14 13:48 ` [PATCH/RFC 1/2] media: dt-bindings: " Geert Uytterhoeven
2018-06-26 19:56 ` Rob Herring
2018-08-16 8:40 ` Kieran Bingham [this message]
2018-06-14 13:48 ` [PATCH/RFC 2/2] arm64: dts: renesas: salvator-common: Fix adv7482 " Geert Uytterhoeven
2018-06-14 15:53 ` Kieran Bingham
2018-06-26 19:57 ` Rob Herring
2018-06-27 15:10 ` Simon Horman
2018-06-27 16:40 ` Geert Uytterhoeven
2018-06-27 16:45 ` Kieran Bingham
2018-06-28 8:47 ` Simon Horman
2018-06-28 8:52 ` Geert Uytterhoeven
2018-06-28 12:25 ` Simon Horman
2018-06-14 15:50 ` [PATCH/RFC 0/2] media: adv748x: Fix " Kieran Bingham
2018-06-26 20:13 ` Rob Herring
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=ec3c39d5-17a6-50f2-b54d-d30c89aadf1f@ideasonboard.com \
--to=kieran.bingham+renesas@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).