From: Rob Herring <robh@kernel.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Baoyou Xie <xie.baoyou@zte.com.cn>,
dri-devel@lists.freedesktop.org, Jun Nie <jun.nie@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: add bindings doc for ZTE VOU display controller
Date: Mon, 10 Oct 2016 16:48:21 -0500 [thread overview]
Message-ID: <20161010214821.GA17551@rob-hp-laptop> (raw)
In-Reply-To: <20161009074910.GA15400@tiger>
On Sun, Oct 09, 2016 at 03:49:10PM +0800, Shawn Guo wrote:
> On Mon, Oct 03, 2016 at 12:44:29PM -0500, Rob Herring wrote:
> > > +Example:
> > > +
> > > +vou: vou@1440000 {
> > > + compatible = "zte,zx296718-vou";
> > > + #address-cells = <1>;
> > > + #size-cells = <1>;
> > > + reg = <0x1440000 0x10000>;
> > > + ranges;
> >
> > You still have overlapping addresses. Explicitly list the sub ranges in
> > reg here used by the VOU driver if the driver usage doesn't overlap. If
> > there is overlap (2 drivers accessing the same range), then you need
> > some APIs between the components (or possibly regmap).
>
> The driver matching "zte,zx296718-vou" doesn't map or access the any
> 'reg' address. The 'reg' property here is more like a hint telling
> that the VOU block covers the address space of all child devices.
>
> I will simply drop the 'reg' property here.
>
> > Also, don't do an empty ranges here. Fill it in so the child nodes are
> > just offsets of 0x1440000
>
> Okay. I thought that empty 'ranges' is fine as long as parent and child
> address spaces are identical (1:1 mapping).
It is fine, but it's just better policy to limit the scope of things.
> So with your suggestion, I made the changes below. Let me know if this
> is still not what you are asking for.
Looks fine. With that,
Acked-by: Rob Herring <robh@kernel.org>
>
> Shawn
>
> -----8<-----------------
>
> diff --git a/Documentation/devicetree/bindings/display/zte,vou.txt b/Documentation/devicetree/bindings/display/zte,vou.txt
> index d03ba4c4810c..6bb4ab2517ef 100644
> --- a/Documentation/devicetree/bindings/display/zte,vou.txt
> +++ b/Documentation/devicetree/bindings/display/zte,vou.txt
> @@ -56,14 +56,13 @@ vou: vou@1440000 {
> compatible = "zte,zx296718-vou";
> #address-cells = <1>;
> #size-cells = <1>;
> - reg = <0x1440000 0x10000>;
> - ranges;
> + ranges = <0 0x1440000 0x10000>;
>
> - dpc: dpc@1440000 {
> + dpc: dpc@0 {
> compatible = "zte,zx296718-dpc";
> - reg = <0x1440000 0x1000>, <0x1441000 0x1000>,
> - <0x1445000 0x1000>, <0x1446000 0x1000>,
> - <0x144a000 0x1000>;
> + reg = <0x0000 0x1000>, <0x1000 0x1000>,
> + <0x5000 0x1000>, <0x6000 0x1000>,
> + <0xa000 0x1000>;
> reg-names = "osd", "timing_ctrl",
> "dtrc", "vou_ctrl",
> "otfppu";
> @@ -74,9 +73,9 @@ vou: vou@1440000 {
> "main_wclk", "aux_wclk";
> };
>
> - hdmi: hdmi@144c000 {
> + hdmi: hdmi@c000 {
> compatible = "zte,zx296718-hdmi";
> - reg = <0x144c000 0x4000>;
> + reg = <0xc000 0x4000>;
> interrupts = <GIC_SPI 82 IRQ_TYPE_EDGE_RISING>;
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-10 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 14:26 [PATCH v2 0/2] Add initial ZTE VOU DRM/KMS driver Shawn Guo
2016-09-24 14:26 ` [PATCH v2 1/2] dt-bindings: add bindings doc for ZTE VOU display controller Shawn Guo
[not found] ` <1474727185-24180-2-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-10-03 17:44 ` Rob Herring
2016-10-09 7:49 ` Shawn Guo
2016-10-10 21:48 ` Rob Herring [this message]
2016-09-24 14:26 ` [PATCH v2 2/2] drm: zte: add initial vou drm driver Shawn Guo
2016-09-25 20:58 ` Daniel Vetter
[not found] ` <20160925205809.GR20761-dv86pmgwkMBes7Z6vYuT8azUEOm+Xw19@public.gmane.org>
2016-09-29 23:42 ` Shawn Guo
2016-09-27 15:48 ` Sean Paul
2016-09-30 1:43 ` Shawn Guo
[not found] ` <1474727185-24180-3-git-send-email-shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-09-30 12:34 ` Emil Velikov
[not found] ` <CACvgo51feNJYrHaKT+M06Z7kOUqzYo1Uv_TAHdLhNXPtRUwsvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-01 0:22 ` Shawn Guo
2016-10-03 10:36 ` Emil Velikov
[not found] ` <CACvgo53A7BpVWHgkFrZsjWnw_uW6xDmKRsrxF=46HOEWQ43BxA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-03 13:49 ` Daniel Vetter
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=20161010214821.GA17551@rob-hp-laptop \
--to=robh@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=shawnguo@kernel.org \
--cc=xie.baoyou@zte.com.cn \
/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