From: Rob Herring <robh+dt@kernel.org>
To: Eric Anholt <eric@anholt.net>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] drm/vc4: Turn the V3D clock on at runtime.
Date: Mon, 1 May 2017 17:59:59 -0500 [thread overview]
Message-ID: <CAL_JsqL6yxK19EowvEJgZ1_h9UAu=b26RnMmMg7HEed-exV9pw@mail.gmail.com> (raw)
In-Reply-To: <20170428224223.21904-1-eric@anholt.net>
On Fri, Apr 28, 2017 at 5:42 PM, Eric Anholt <eric@anholt.net> wrote:
> For the Raspberry Pi's bindings, the power domain also implicitly
> turns on the clock and deasserts reset, but for the new Cygnus port we
> start representing the clock in the devicetree.
>
> v2: Document the clock-names property, check for -ENOENT for no clock
> in DT.
> v3: Drop NULL checks around clk calls which embed NULL checks.
> v4: Drop clk-names (feedback by Rob Herring)
>
> Signed-off-by: Eric Anholt <eric@anholt.net>
> ---
> .../devicetree/bindings/display/brcm,bcm-vc4.txt | 3 +++
> drivers/gpu/drm/vc4/vc4_drv.h | 1 +
> drivers/gpu/drm/vc4/vc4_v3d.c | 31 +++++++++++++++++++++-
> 3 files changed, 34 insertions(+), 1 deletion(-)
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2017-05-01 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 22:42 [PATCH v4 1/3] drm/vc4: Turn the V3D clock on at runtime Eric Anholt
2017-04-28 22:42 ` [PATCH v4 2/3] drm/vc4: Don't try to initialize FBDEV if we're only bound to V3D Eric Anholt
2017-05-02 9:24 ` Daniel Vetter
2017-05-03 19:06 ` Eric Anholt
2017-04-28 22:42 ` [PATCH v4 3/3] drm/vc4: Add specific compatible strings for Cygnus Eric Anholt
2017-05-01 22:59 ` 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_JsqL6yxK19EowvEJgZ1_h9UAu=b26RnMmMg7HEed-exV9pw@mail.gmail.com' \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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 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).