From: Rob Herring <robh@kernel.org>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: devicetree@vger.kernel.org, narmstrong@baylibre.com,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
jbrunet@baylibre.com
Subject: Re: [PATCH v2 1/4] dt-bindings: clock: meson8b: export the VPU clock
Date: Sun, 31 Mar 2019 01:41:45 -0500 [thread overview]
Message-ID: <5ca0612a.1c69fb81.9bbef.7249@mx.google.com> (raw)
In-Reply-To: <20190324151104.18397-2-martin.blumenstingl@googlemail.com>
On Sun, 24 Mar 2019 16:11:01 +0100, Martin Blumenstingl wrote:
> The VPU clock is an input the the "VPU" (Video Processing Unit), which is
> one of the components of the display controller.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> include/dt-bindings/clock/meson8b-clkc.h | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-03-31 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 15:11 [PATCH v2 0/4] clk: meson8b: add the VPU clock tree Martin Blumenstingl
2019-03-24 15:11 ` [PATCH v2 1/4] dt-bindings: clock: meson8b: export the VPU clock Martin Blumenstingl
2019-03-31 6:41 ` Rob Herring [this message]
2019-03-24 15:11 ` [PATCH v2 2/4] clk: meson: meson8b: use a separate clock table for Meson8m2 Martin Blumenstingl
2019-03-24 15:11 ` [PATCH v2 3/4] clk: meson: meson8b: add support for the GP_PLL clock on Meson8m2 Martin Blumenstingl
2019-03-24 15:11 ` [PATCH v2 4/4] clk: meson: meson8b: add the VPU clock trees Martin Blumenstingl
2019-03-25 9:54 ` [PATCH v2 0/4] clk: meson8b: add the VPU clock tree Jerome Brunet
2019-04-01 8:40 ` Neil Armstrong
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=5ca0612a.1c69fb81.9bbef.7249@mx.google.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.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).