From: Rob Herring <robh@kernel.org>
To: Taniya Das <tdas@codeaurora.org>
Cc: "Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette " <mturquette@baylibre.com>,
"David Brown" <david.brown@linaro.org>,
"Rajendra Nayak" <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org,
"Taniya Das" <tdas@codeaurora.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: clock: Add YAML schemas for the QCOM RPMHCC clock bindings
Date: Tue, 5 Nov 2019 15:55:47 -0600 [thread overview]
Message-ID: <20191105215547.GA402@bogus> (raw)
In-Reply-To: <1572371299-16774-2-git-send-email-tdas@codeaurora.org>
On Tue, 29 Oct 2019 23:18:17 +0530, Taniya Das wrote:
> The RPMHCC clock provider have a bunch of generic properties that
> are needed in a device tree. Add a YAML schemas for those.
>
> Signed-off-by: Taniya Das <tdas@codeaurora.org>
> ---
> .../devicetree/bindings/clock/qcom,rpmh-clk.txt | 27 ------------
> .../devicetree/bindings/clock/qcom,rpmhcc.yaml | 48 ++++++++++++++++++++++
> 2 files changed, 48 insertions(+), 27 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/qcom,rpmh-clk.txt
> create mode 100644 Documentation/devicetree/bindings/clock/qcom,rpmhcc.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-11-05 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 17:48 [PATCH v2 0/3] Add support for RPMHCC for SC7180 Taniya Das
2019-10-29 17:48 ` [PATCH v2 1/3] dt-bindings: clock: Add YAML schemas for the QCOM RPMHCC clock bindings Taniya Das
2019-11-05 21:55 ` Rob Herring [this message]
2019-11-07 21:23 ` Stephen Boyd
2019-10-29 17:48 ` [PATCH v2 2/3] dt-bindings: clock: Introduce RPMHCC bindings for SC7180 Taniya Das
2019-11-05 22:36 ` Stephen Boyd
2019-11-07 21:24 ` Stephen Boyd
2019-11-08 3:30 ` Taniya Das
2019-10-29 17:48 ` [PATCH v2 3/3] clk: qcom: clk-rpmh: Add support for RPMHCC " Taniya Das
2019-11-07 21:13 ` Stephen Boyd
2019-11-07 21:19 ` Stephen Boyd
2019-11-07 21:24 ` 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=20191105215547.GA402@bogus \
--to=robh@kernel.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=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tdas@codeaurora.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).