From: Rob Herring <robh@kernel.org>
To: Jeffrey Hugo <jhugo@codeaurora.org>
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, agross@kernel.org,
bjorn.andersson@linaro.org, marc.w.gonzalez@free.fr,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Jeffrey Hugo <jhugo@codeaurora.org>
Subject: Re: [PATCH v10 2/4] dt-bindings: clock: Convert qcom,mmcc to DT schema
Date: Thu, 21 Nov 2019 14:20:01 -0600 [thread overview]
Message-ID: <20191121202001.GA19935@bogus> (raw)
In-Reply-To: <0101016e7b4311fe-8edd7849-df65-47dd-98fa-1e2063c83178-000000@us-west-2.amazonses.com>
On Sun, 17 Nov 2019 21:27:03 +0000, Jeffrey Hugo wrote:
> Convert the qcom,mmcc-X clock controller binding to DT schema. Add the
> protected-clocks property to the schema to show that is it explicitly
> allowed, instead of relying on the generic, pre-schema binding.
>
> Signed-off-by: Jeffrey Hugo <jhugo@codeaurora.org>
> ---
> .../devicetree/bindings/clock/qcom,mmcc.txt | 28 ----------
> .../devicetree/bindings/clock/qcom,mmcc.yaml | 60 ++++++++++++++++++++++
> 2 files changed, 60 insertions(+), 28 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/qcom,mmcc.txt
> create mode 100644 Documentation/devicetree/bindings/clock/qcom,mmcc.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-11-21 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1574025887-32667-1-git-send-email-jhugo@codeaurora.org>
2019-11-17 21:26 ` [PATCH v10 1/4] dt-bindings: clock: Document external clocks for MSM8998 gcc Jeffrey Hugo
2019-11-17 21:27 ` [PATCH v10 2/4] dt-bindings: clock: Convert qcom,mmcc to DT schema Jeffrey Hugo
2019-11-21 20:20 ` Rob Herring [this message]
2019-11-17 21:27 ` [PATCH v10 3/4] dt-bindings: clock: Add support for the MSM8998 mmcc Jeffrey Hugo
2019-11-17 21:27 ` [PATCH v10 4/4] clk: qcom: Add MSM8998 Multimedia Clock Controller (MMCC) driver Jeffrey Hugo
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=20191121202001.GA19935@bogus \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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).