From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Abel Vesa <abel.vesa@linaro.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v8 3/4] clk: qcom: rpmh: Add support for SM8550 rpmh clocks
Date: Wed, 4 Jan 2023 12:46:55 +0200 [thread overview]
Message-ID: <07a849a9-03dc-f3af-1d3f-2369cb71451e@linaro.org> (raw)
In-Reply-To: <20230104093450.3150578-4-abel.vesa@linaro.org>
On 04/01/2023 11:34, Abel Vesa wrote:
> Adds the RPMH clocks present in SM8550 SoC.
>
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
> ---
> drivers/clk/qcom/clk-rpmh.c | 36 ++++++++++++++++++++++++++++++++++++
> 1 file changed, 36 insertions(+)
I think the plan was to have the _PAD clock as a child node of the
rpmcc. Is it still the planned implementation?
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-01-04 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 9:34 [PATCH v8 0/4] clk: qcom: Add support for SM8550 Abel Vesa
2023-01-04 9:34 ` [PATCH v8 1/4] dt-bindings: clock: Add SM8550 TCSR CC clocks Abel Vesa
2023-01-04 9:34 ` [PATCH v8 2/4] dt-bindings: clock: Add RPMHCC for SM8550 Abel Vesa
2023-01-04 9:34 ` [PATCH v8 3/4] clk: qcom: rpmh: Add support for SM8550 rpmh clocks Abel Vesa
2023-01-04 10:46 ` Dmitry Baryshkov [this message]
2023-01-04 12:45 ` Abel Vesa
2023-01-04 14:40 ` Dmitry Baryshkov
2023-01-06 16:56 ` Bjorn Andersson
2023-01-04 9:34 ` [PATCH v8 4/4] clk: qcom: Add TCSR clock driver for SM8550 Abel Vesa
2023-01-06 17:12 ` [PATCH v8 0/4] clk: qcom: Add support " Bjorn Andersson
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=07a849a9-03dc-f3af-1d3f-2369cb71451e@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).