All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Tomi Valkeinen" <tomi.valkeinen@ti.com>,
	"Rob Herring" <robh@kernel.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	devicetree <devicetree@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: omap3-gta04: Fix graph_port warning
Date: Wed, 9 Jan 2019 09:01:19 -0800	[thread overview]
Message-ID: <20190109170119.GR5544@atomide.com> (raw)
In-Reply-To: <4F877B6F-2AED-4891-9676-5AB69B01C1AD@goldelico.com>

* H. Nikolaus Schaller <hns@goldelico.com> [190109 16:47]:
> Ho Tony, Tomi,
> 
> > Am 08.01.2019 um 16:56 schrieb Tony Lindgren <tony@atomide.com>:
> > 
> > * Tomi Valkeinen <tomi.valkeinen@ti.com> [190108 07:57]:
> >> On 07/01/19 21:34, H. Nikolaus Schaller wrote:
> >> 
> >>>>> If there's only one port, then it is redundant and you should drop reg
> >>>>> instead.
> >>> 
> >>> If I remember correctly it was required by older omapdrm code (which
> >>> did scan for a reg property) but that may have changed. Therefore I've
> >>> added Tomi to this discussion.
> >> 
> >> I don't think so. The code looks for 'reg', but if it's not there, then
> >> it's considered 0.
> > 
> > FYI, the binding doc for the graph bindings is at
> > Documentation/devicetree/bindings/graph.txt if there is
> > any questions on how things should work.
> 
> I interpret it that "port@number" is only needed if there are
> multiple ports and there should not be any "@" or "reg" for the
> single port case. Although it seems not to be explicitly
> forbidden.
> 
> The &dss port doesn't have it either.
> 
> So let's remove the reg = <0>;
> 
> It also seems that
> 
> 	#address-cells = <1>;
> 	#size-cells = <0>;
> 
> is not required in this case and can also be removed.
> 
> I've tested and it works with v5.0-rc1.
> 
> There is an edited patch [1] but IMHO you as the original
> author should post it.

Looks good to me. But since you already modified it, all
you need to do is add your Signed-off-by after mine and
mail it out :) That is if you want to keep me as the
original author I guess for the description.

Otherwise we have to go through one more round of emails
where I post it you ack it and so on as I can't test it.

Regards,

Tony

> [1]: http://git.goldelico.com/?p=letux-kernel.git;a=commit;h=e46369390f62ce7176e91dfa443185e4b097ef4b

  reply	other threads:[~2019-01-09 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 16:05 [PATCH] ARM: dts: omap3-gta04: Fix graph_port warning Tony Lindgren
2019-01-07 16:21 ` 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 [this message]
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=20190109170119.GR5544@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 \
    --cc=robh@kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /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.