From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
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,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH/RFC 0/2] media: adv748x: Fix decimal unit addresses
Date: Thu, 14 Jun 2018 15:48:06 +0200 [thread overview]
Message-ID: <1528984088-24801-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Rob et al.
Recent dtc assumes unit addresses are always hexadecimal (without
prefix), while the bases of reg property values depend on their
prefixes, and thus can be either decimal or hexadecimal.
This leads to (with 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"
In this particular case, the unit addresses are (assumed hexadecimal) 10
resp. 11, while the reg properties are decimal 10 resp. 11, and thus
don't match.
This RFC patch series corrects the unit addresses to match the reg
address values for the DT bindings for adi,adv748x and its users.
There's at least one other violator (port@10 in
arch/arm/boot/dts/vf610-zii-dev-rev-c.dts), which I didn't fix.
However, ePAPR v1.1 states:
The unit-address component of the name is specific to the bus type
on which the node sits. It consists of one or more ASCII characters
from the set of characters in Table 2-1. The unit-address must match
the first address specified in the reg property of the node. If the
node has no reg property, the @ and unit-address must be omitted and
the node-name alone differentiates the node from other nodes at the
same level in the tree. The binding for a particular bus may specify
additional, more specific requirements for the format of reg and the
unit-address.
i.e. nothing about an hexadecimal address requirement?
Should this series be applied, or should the warnings be ignored, until
dtc is fixed?
Thanks for your comments!
Geert Uytterhoeven (2):
media: dt-bindings: adv748x: Fix decimal unit addresses
arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit
addresses
Documentation/devicetree/bindings/media/i2c/adv748x.txt | 4 ++--
arch/arm64/boot/dts/renesas/salvator-common.dtsi | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.7.4
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2018-06-14 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 13:48 Geert Uytterhoeven [this message]
2018-06-14 13:48 ` [PATCH/RFC 1/2] media: dt-bindings: adv748x: Fix decimal unit addresses Geert Uytterhoeven
2018-06-26 19:56 ` Rob Herring
2018-08-16 8:40 ` Kieran Bingham
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=1528984088-24801-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=kieran.bingham+renesas@ideasonboard.com \
--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).