All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	SH-Linux <linux-sh@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [RFC/PATCH 1/7] drm/rcar-du: Add OF support
Date: Thu, 23 Jan 2014 11:31:27 +0000	[thread overview]
Message-ID: <3739709.HlpN7KneJZ@avalon> (raw)
In-Reply-To: <CANqRtoQQ45w1EroyfbWSFtWQVdg-YyPVPWpGTvFmCXqoDZhpQA@mail.gmail.com>

Hi Magnus,

On Thursday 23 January 2014 18:52:29 Magnus Damm wrote:
> On Wed, Jan 22, 2014 at 12:32 AM, Laurent Pinchart wrote:
> > Add DT bindings for the R-Car DU with support for core resources
> > (memory, IRQ and clocks). Output configuration must still be passed
> > through platform data using OF_DEV_AUXDATA.
> > 
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> > 
> >  .../devicetree/bindings/video/renesas,du.txt       |  49 +++++++
> >  drivers/gpu/drm/rcar-du/rcar_du_drv.c              | 161 +++++++++-------
> > 2 files changed, 138 insertions(+), 72 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/video/renesas,du.txt
> 
> Hi Laurent,
> 
> Thanks for your patches. I have some minor comments related to r8a7790
> vs r8a7791, please see below.
> 
> > diff --git a/Documentation/devicetree/bindings/video/renesas,du.txt
> > b/Documentation/devicetree/bindings/video/renesas,du.txt new file mode
> > 100644
> > index 0000000..6bd947c
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/video/renesas,du.txt
> > @@ -0,0 +1,49 @@
> > +* Renesas R-Car Display Unit (DU)
> > +
> > +Required Properties:
> > +
> > +  - compatible: must be one of the following.
> > +    - "renesas,du-r8a7779" for R8A7779 (R-Car H1) compatible DU
> > +    - "renesas,du-r8a7790" for R8A7790 (R-Car H2) compatible DU
> > +    - "renesas,du-r8a7790" for R8A7791 (R-Car M2) compatible DU
> 
> I suppose the last line above should be "renesas,du-r8a7791", right?
> 
> > +  - reg: A list of base address and length of each memory resource, one
> > for
> > +    each entry in the reg-names property.
> > +  - reg-names: Name of the memory resources. The DU requires one memory
> > +    resource for the DU core (named "du") and one memory resource for
> > each
> > +    LVDS encoder (named "lvds.x" with "x" being the LVDS controller
> > numerical
> > +    index).
> > +
> > +  - interrupt-parent: phandle of the parent interrupt controller.
> > +  - interrupts: Interrupt specifiers for the DU interrupts.
> > +
> > +  - clocks: A list of phandles + clock-specifier pairs, one for each
> > entry in
> > +    the clock-names property.
> > +  - clock-names: Name of the clocks. This property is model-dependent.
> > +    - R8A7779 uses a single functional clock. The clock doesn't need to
> > be
> > +      named.
> > +    - R8A7790 and R8A7790 use one functional clock per channel and one
> > clock
> > +      per LVDS encoder. The functional clocks must be named "du.x" with
> > "x"
> > +      being the channel numerical index. The LVDS clocks must be named
> > +      "lvds.x" with "x" being the LVDS encoder numerical index.
> 
> "R8A7790 and R8A7791"...?

I'll fix both in the next version.

-- 
Regards,

Laurent Pinchart


WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	SH-Linux <linux-sh@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [RFC/PATCH 1/7] drm/rcar-du: Add OF support
Date: Thu, 23 Jan 2014 12:31:27 +0100	[thread overview]
Message-ID: <3739709.HlpN7KneJZ@avalon> (raw)
In-Reply-To: <CANqRtoQQ45w1EroyfbWSFtWQVdg-YyPVPWpGTvFmCXqoDZhpQA@mail.gmail.com>

Hi Magnus,

On Thursday 23 January 2014 18:52:29 Magnus Damm wrote:
> On Wed, Jan 22, 2014 at 12:32 AM, Laurent Pinchart wrote:
> > Add DT bindings for the R-Car DU with support for core resources
> > (memory, IRQ and clocks). Output configuration must still be passed
> > through platform data using OF_DEV_AUXDATA.
> > 
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> > 
> >  .../devicetree/bindings/video/renesas,du.txt       |  49 +++++++
> >  drivers/gpu/drm/rcar-du/rcar_du_drv.c              | 161 +++++++++-------
> > 2 files changed, 138 insertions(+), 72 deletions(-)
> >  create mode 100644 Documentation/devicetree/bindings/video/renesas,du.txt
> 
> Hi Laurent,
> 
> Thanks for your patches. I have some minor comments related to r8a7790
> vs r8a7791, please see below.
> 
> > diff --git a/Documentation/devicetree/bindings/video/renesas,du.txt
> > b/Documentation/devicetree/bindings/video/renesas,du.txt new file mode
> > 100644
> > index 0000000..6bd947c
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/video/renesas,du.txt
> > @@ -0,0 +1,49 @@
> > +* Renesas R-Car Display Unit (DU)
> > +
> > +Required Properties:
> > +
> > +  - compatible: must be one of the following.
> > +    - "renesas,du-r8a7779" for R8A7779 (R-Car H1) compatible DU
> > +    - "renesas,du-r8a7790" for R8A7790 (R-Car H2) compatible DU
> > +    - "renesas,du-r8a7790" for R8A7791 (R-Car M2) compatible DU
> 
> I suppose the last line above should be "renesas,du-r8a7791", right?
> 
> > +  - reg: A list of base address and length of each memory resource, one
> > for
> > +    each entry in the reg-names property.
> > +  - reg-names: Name of the memory resources. The DU requires one memory
> > +    resource for the DU core (named "du") and one memory resource for
> > each
> > +    LVDS encoder (named "lvds.x" with "x" being the LVDS controller
> > numerical
> > +    index).
> > +
> > +  - interrupt-parent: phandle of the parent interrupt controller.
> > +  - interrupts: Interrupt specifiers for the DU interrupts.
> > +
> > +  - clocks: A list of phandles + clock-specifier pairs, one for each
> > entry in
> > +    the clock-names property.
> > +  - clock-names: Name of the clocks. This property is model-dependent.
> > +    - R8A7779 uses a single functional clock. The clock doesn't need to
> > be
> > +      named.
> > +    - R8A7790 and R8A7790 use one functional clock per channel and one
> > clock
> > +      per LVDS encoder. The functional clocks must be named "du.x" with
> > "x"
> > +      being the channel numerical index. The LVDS clocks must be named
> > +      "lvds.x" with "x" being the LVDS encoder numerical index.
> 
> "R8A7790 and R8A7791"...?

I'll fix both in the next version.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-01-23 11:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 15:32 [RFC/PATCH 0/7] Renesas R-Car DU OF support Laurent Pinchart
2014-01-21 15:32 ` Laurent Pinchart
2014-01-21 15:32 ` [RFC/PATCH 1/7] drm/rcar-du: Add " Laurent Pinchart
2014-01-21 15:32   ` Laurent Pinchart
2014-01-21 15:35   ` [RFC/PATCH 1/7 RESEND] " Laurent Pinchart
2014-01-21 15:35     ` Laurent Pinchart
2014-01-23  9:52   ` [RFC/PATCH 1/7] " Magnus Damm
2014-01-23  9:52     ` Magnus Damm
2014-01-23 11:31     ` Laurent Pinchart [this message]
2014-01-23 11:31       ` Laurent Pinchart
2014-01-21 15:32 ` [RFC/PATCH 2/7] ARM: shmobile: r8a7790: Add DU node to device tree Laurent Pinchart
2014-01-21 15:32   ` Laurent Pinchart
2014-01-21 15:32 ` [RFC/PATCH 3/7] ARM: shmobile: lager-reference: Add DU platform data Laurent Pinchart
2014-01-21 15:32   ` Laurent Pinchart
2014-01-21 15:32 ` [RFC/PATCH 4/7] ARM: shmobile: lager: Enable DU device in DT Laurent Pinchart
2014-01-21 15:32   ` Laurent Pinchart
2014-01-21 15:32 ` [RFC/PATCH 5/7] ARM: shmobile: r8a7791: Add DU node to device tree Laurent Pinchart
2014-01-21 15:32   ` Laurent Pinchart
2014-01-21 15:32 ` [RFC/PATCH 6/7] ARM: shmobile: koelsch-reference: Add DU platform data Laurent Pinchart
2014-01-21 15:32   ` Laurent Pinchart
2014-01-21 15:32 ` [RFC/PATCH 7/7] ARM: shmobile: koelsch: Enable DU device in DT Laurent Pinchart
2014-01-21 15:32   ` Laurent Pinchart

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=3739709.HlpN7KneJZ@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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.