All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
	devicetree@vger.kernel.org,
	"H . Nikolaus Schaller" <hns@goldelico.com>
Subject: [PATCH] ARM: dts: omap3-gta04: Fix graph_port warning
Date: Mon,  7 Jan 2019 08:05:12 -0800	[thread overview]
Message-ID: <20190107160512.9480-1-tony@atomide.com> (raw)

We're currently getting a warning with make dtbs:

arch/arm/boot/dts/omap3-gta04.dtsi:720.7-727.4: Warning (graph_port):
/ocp@68000000/dss@48050000/encoder@48050c0 0/port: graph node unit
address error, expected "0"

Cc: H. Nikolaus Schaller <hns@goldelico.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
 arch/arm/boot/dts/omap3-gta04.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm/boot/dts/omap3-gta04.dtsi b/arch/arm/boot/dts/omap3-gta04.dtsi
--- a/arch/arm/boot/dts/omap3-gta04.dtsi
+++ b/arch/arm/boot/dts/omap3-gta04.dtsi
@@ -717,7 +717,7 @@
 	#address-cells = <1>;
 	#size-cells = <0>;
 
-	port {
+	port@0 {
 		reg = <0>;
 		venc_out: endpoint {
 			remote-endpoint = <&opa_in>;
-- 
2.20.1

             reply	other threads:[~2019-01-07 16:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 16:05 Tony Lindgren [this message]
2019-01-07 16:21 ` [PATCH] ARM: dts: omap3-gta04: Fix graph_port warning H. Nikolaus Schaller
2019-01-07 18:31   ` Rob Herring
2019-01-07 18:34     ` Tony Lindgren
2019-01-07 19:34       ` H. Nikolaus Schaller
2019-01-08  7:57         ` Tomi Valkeinen
2019-01-08 15:56           ` Tony Lindgren
2019-01-09 16:46             ` H. Nikolaus Schaller
2019-01-09 17:01               ` Tony Lindgren
2019-01-09 17:42                 ` H. Nikolaus Schaller

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=20190107160512.9480-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hns@goldelico.com \
    --cc=linux-omap@vger.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 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.