From: Stephen Boyd <sboyd@kernel.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>, Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/4] dt-bindings: clock: Document the parent clocks
Date: Mon, 09 Sep 2019 04:41:54 -0700 [thread overview]
Message-ID: <20190909114155.32E40218AF@mail.kernel.org> (raw)
In-Reply-To: <20190826173120.2971-2-vkoul@kernel.org>
Quoting Vinod Koul (2019-08-26 10:31:17)
> With clock parent data scheme we must specify the parent clocks for the
> rpmhcc nodes. So describe the parent clock for rpmhcc in the bindings.
>
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> ---
Applied to clk-next
next prev parent reply other threads:[~2019-09-09 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 17:31 [PATCH v5 0/4] clk: qcom: Add support for SM8150 rpmh Vinod Koul
2019-08-26 17:31 ` [PATCH v5 1/4] dt-bindings: clock: Document the parent clocks Vinod Koul
2019-08-27 18:50 ` Rob Herring
2019-09-09 11:41 ` Stephen Boyd [this message]
2019-08-26 17:31 ` [PATCH v5 2/4] clk: qcom: clk-rpmh: Convert to parent data scheme Vinod Koul
2019-08-27 4:31 ` Bjorn Andersson
2019-09-09 11:42 ` Stephen Boyd
2019-08-26 17:31 ` [PATCH v5 3/4] dt-bindings: clock: Document SM8150 rpmh-clock compatible Vinod Koul
2019-08-27 18:51 ` Rob Herring
2019-09-09 11:42 ` Stephen Boyd
2019-08-26 17:31 ` [PATCH v5 4/4] clk: qcom: clk-rpmh: Add support for SM8150 Vinod Koul
2019-09-09 11:42 ` 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=20190909114155.32E40218AF@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@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 \
--cc=vkoul@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).