devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	etnaviv@lists.freedesktop.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	patchwork-lst@pengutronix.de,
	Sascha Hauer <kernel@pengutronix.de>,
	Russell King <linux+etnaviv@armlinux.org.uk>
Subject: Re: [PATCH v2 1/2] dt-bindings: etnaviv: add slave interface clock
Date: Wed, 24 Jan 2018 14:50:16 -0600	[thread overview]
Message-ID: <CAL_JsqKWeOwHvgZ55AnZ=b6W7LZhCTgq0NYCwDztJDFZOYEm8A@mail.gmail.com> (raw)
In-Reply-To: <20180124153711.22049-1-l.stach@pengutronix.de>

On Wed, Jan 24, 2018 at 9:37 AM, Lucas Stach <l.stach@pengutronix.de> wrote:
> Newer GPU cores added a new clock input, which allows to gate the slave (AHB)
> interface independently from other parts of the GPU. Add it to the supported
> clocks.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> v2: State when this clock is required.
> ---
>  Documentation/devicetree/bindings/display/etnaviv/etnaviv-drm.txt | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)

Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      parent reply	other threads:[~2018-01-24 20:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-24 15:37 [PATCH v2 1/2] dt-bindings: etnaviv: add slave interface clock Lucas Stach
     [not found] ` <20180124153711.22049-1-l.stach-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2018-01-24 15:37   ` [PATCH v2 2/2] drm/etnaviv: remove the need for a gpu-subsystem DT node Lucas Stach
2018-01-24 20:49     ` Rob Herring
     [not found]       ` <CAL_JsqJYfX3ngPns4TcTbaCWQwwZQHq=VtvZ3KTpBNyVVMH-mQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-25  9:43         ` Lucas Stach
2018-01-24 20:50 ` Rob Herring [this message]

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='CAL_JsqKWeOwHvgZ55AnZ=b6W7LZhCTgq0NYCwDztJDFZOYEm8A@mail.gmail.com' \
    --to=robh+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=etnaviv@lists.freedesktop.org \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux+etnaviv@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=patchwork-lst@pengutronix.de \
    /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).