From: Taniya Das <tdas@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: 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,
Andy Gross <agross@kernel.org>,
devicetree@vger.kernel.org, robh@kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: clock: Add YAML schemas for LPASS clocks on SC7180
Date: Wed, 10 Jun 2020 22:37:56 +0530 [thread overview]
Message-ID: <b12652b6-3c82-c5fd-42cc-89bba4a15a01@codeaurora.org> (raw)
In-Reply-To: <159054910485.88029.14861222587907627358@swboyd.mtv.corp.google.com>
Thanks for the review.
On 5/27/2020 8:41 AM, Stephen Boyd wrote:
>> + clocks:
>> + items:
>> + - description: gcc_lpass_sway clock from GCC
>> +
>> + clock-names:
>> + items:
>> + - const: gcc_lpass_sway
>
> As said on patch #4, maybe "iface" instead?
>
Will take care in the next patch.
>> +
>> + power-domains:
>> + items:
>> + - description: LPASS CORE HM GSDCR
>> +
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.
--
next prev parent reply other threads:[~2020-06-10 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 9:22 [PATCH v2 0/4] clk: qcom: Support for Low Power Audio Clocks on SC7180 Taniya Das
2020-05-17 9:22 ` [PATCH v2 1/4] clk: qcom: gdsc: Add support to enable retention of GSDCR Taniya Das
2020-05-17 9:22 ` [PATCH v2 2/4] dt-bindings: clock: Add YAML schemas for LPASS clocks on SC7180 Taniya Das
2020-05-27 3:11 ` Stephen Boyd
2020-06-10 17:07 ` Taniya Das [this message]
2020-05-28 20:25 ` Rob Herring
2020-06-10 17:09 ` Taniya Das
2020-05-17 9:22 ` [PATCH v2 3/4] clk: qcom: gcc: Add support for GCC LPASS clock for SC7180 Taniya Das
2020-05-17 9:22 ` [PATCH v2 4/4] clk: qcom: lpass: Add support for LPASS clock controller " Taniya Das
2020-05-27 3:10 ` Stephen Boyd
2020-06-10 17:11 ` Taniya Das
2020-06-11 1:06 ` 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=b12652b6-3c82-c5fd-42cc-89bba4a15a01@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=agross@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=robh@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).