From: Rob Herring <robh@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: clock: Introduce Qualcomm Turing Clock controller
Date: Wed, 27 Mar 2019 18:34:55 -0500 [thread overview]
Message-ID: <20190327233455.GA8216@bogus> (raw)
In-Reply-To: <20190306174758.22462-2-bjorn.andersson@linaro.org>
On Wed, 6 Mar 2019 09:47:56 -0800, Bjorn Andersson wrote:
> Add devicetree binding for the turing clock controller found in QCS404.
>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
> .../bindings/clock/qcom,turingcc.txt | 19 +++++++++++++++++++
> .../dt-bindings/clock/qcom,turingcc-qcs404.h | 15 +++++++++++++++
> 2 files changed, 34 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/qcom,turingcc.txt
> create mode 100644 include/dt-bindings/clock/qcom,turingcc-qcs404.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-03-27 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 17:47 [PATCH 0/3] Qualcomm QCS404 Turing Clock Controller Bjorn Andersson
2019-03-06 17:47 ` [PATCH 1/3] dt-bindings: clock: Introduce Qualcomm Turing Clock controller Bjorn Andersson
2019-03-27 23:34 ` Rob Herring [this message]
2019-04-11 20:35 ` Stephen Boyd
2019-03-06 17:47 ` [PATCH 2/3] clk: qcom: branch: Add AON clock ops Bjorn Andersson
2019-04-11 20:36 ` Stephen Boyd
2019-03-06 17:47 ` [PATCH 3/3] clk: qcom: Add QCS404 TuringCC Bjorn Andersson
2019-04-11 20:36 ` Stephen Boyd
2019-04-11 20:36 ` Stephen Boyd
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=20190327233455.GA8216@bogus \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@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).