From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: drm: rcar-du: Document optional reset properties
Date: Mon, 06 Mar 2017 18:39:33 +0200 [thread overview]
Message-ID: <15041321.g73uU3sC2l@avalon> (raw)
In-Reply-To: <CAMuHMdVw7nR1EG_+3Vjm6HdUKtq+jvbO6AbQk5WT2dEs7JDqmg@mail.gmail.com>
Hi Geert,
On Monday 06 Mar 2017 17:36:41 Geert Uytterhoeven wrote:
> On Mon, Mar 6, 2017 at 5:32 PM, Laurent Pinchart wrote:
> > On Monday 06 Mar 2017 17:25:56 Geert Uytterhoeven wrote:
> >> Document the optional properties for describing module resets, to
> >> support resetting display channels and LVDS encoders on R-Car Gen2 and
> >> Gen3.
> >>
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > This looks good to me.
> >
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> Thanks!
>
> > I think we should try implementing support for reset in the DU driver
> > before merging this though, it always helps to test the proposed DT
> > bindings.
>
> Do you want me to drop the DU parts from my big patches to add all resets
> to the .dtsis I was going to send?
>
> DU is the special one, as it doesn't have a one-to-one mapping of resets
> to modules.
If it's not too urgent, I'd appreciate if we could test it first, yes.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
DRI Development <dri-devel@lists.freedesktop.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: drm: rcar-du: Document optional reset properties
Date: Mon, 06 Mar 2017 18:39:33 +0200 [thread overview]
Message-ID: <15041321.g73uU3sC2l@avalon> (raw)
In-Reply-To: <CAMuHMdVw7nR1EG_+3Vjm6HdUKtq+jvbO6AbQk5WT2dEs7JDqmg@mail.gmail.com>
Hi Geert,
On Monday 06 Mar 2017 17:36:41 Geert Uytterhoeven wrote:
> On Mon, Mar 6, 2017 at 5:32 PM, Laurent Pinchart wrote:
> > On Monday 06 Mar 2017 17:25:56 Geert Uytterhoeven wrote:
> >> Document the optional properties for describing module resets, to
> >> support resetting display channels and LVDS encoders on R-Car Gen2 and
> >> Gen3.
> >>
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > This looks good to me.
> >
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> Thanks!
>
> > I think we should try implementing support for reset in the DU driver
> > before merging this though, it always helps to test the proposed DT
> > bindings.
>
> Do you want me to drop the DU parts from my big patches to add all resets
> to the .dtsis I was going to send?
>
> DU is the special one, as it doesn't have a one-to-one mapping of resets
> to modules.
If it's not too urgent, I'd appreciate if we could test it first, yes.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-06 16:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 16:25 [PATCH v2] dt-bindings: drm: rcar-du: Document optional reset properties Geert Uytterhoeven
2017-03-06 16:32 ` Laurent Pinchart
2017-03-06 16:32 ` Laurent Pinchart
2017-03-06 16:36 ` Geert Uytterhoeven
2017-03-06 16:36 ` Geert Uytterhoeven
2017-03-06 16:39 ` Laurent Pinchart [this message]
2017-03-06 16:39 ` Laurent Pinchart
2017-03-15 17:01 ` Rob Herring
2017-03-15 17:01 ` Rob Herring
2017-03-16 8:13 ` Geert Uytterhoeven
2017-03-16 20:56 ` Rob Herring
2017-03-16 20:56 ` Rob Herring
2017-03-16 20:59 ` Geert Uytterhoeven
2017-03-16 20:59 ` Geert Uytterhoeven
2017-03-20 15:04 ` Rob Herring
2017-03-20 15:04 ` Rob Herring
2017-04-07 12:55 ` 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=15041321.g73uU3sC2l@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@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.