linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>
Cc: Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] clk: qcom: Add QCS404 TuringCC
Date: Thu, 11 Apr 2019 13:36:48 -0700	[thread overview]
Message-ID: <155501500860.20095.12195621768250948176@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190306174758.22462-4-bjorn.andersson@linaro.org>

Quoting Bjorn Andersson (2019-03-06 09:47:58)
> The Turing Clock Controller provides resources related to running the
> Turing subsystem.
> 
> PM runtime is used to ensure that the associated AHB clock is ticking
> while the clock framework is accessing the registers in the Turing clock
> controller.
> 
> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---

Applied to clk-next


      parent reply	other threads:[~2019-04-11 20:36 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
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 [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=155501500860.20095.12195621768250948176@swboyd.mtv.corp.google.com \
    --to=sboyd@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=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).