devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
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, 6 Mar 2017 17:36:41 +0100	[thread overview]
Message-ID: <CAMuHMdVw7nR1EG_+3Vjm6HdUKtq+jvbO6AbQk5WT2dEs7JDqmg@mail.gmail.com> (raw)
In-Reply-To: <1503576.T3vfvR3RGC@avalon>

Hi Laurent,

On Mon, Mar 6, 2017 at 5:32 PM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> 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.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-03-06 16:36 UTC|newest]

Thread overview: 10+ 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:36   ` Geert Uytterhoeven [this message]
2017-03-06 16:39     ` Laurent Pinchart
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:59       ` Geert Uytterhoeven
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=CAMuHMdVw7nR1EG_+3Vjm6HdUKtq+jvbO6AbQk5WT2dEs7JDqmg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).