From: Bjorn Andersson <andersson@kernel.org>
To: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Kathiravan T <quic_kathirav@quicinc.com>
Cc: quic_srichara@quicinc.com, quic_sjaganat@quicinc.com,
quic_anusha@quicinc.com, quic_saahtoma@quicinc.com
Subject: Re: [PATCH 0/2] Drop the mem noc clocks from the IPQ5332 GCC driver
Date: Sun, 13 Aug 2023 20:27:42 -0700 [thread overview]
Message-ID: <169198364306.2443702.8402512633493071282.b4-ty@kernel.org> (raw)
In-Reply-To: <20230710102807.1189942-1-quic_kathirav@quicinc.com>
On Mon, 10 Jul 2023 15:58:05 +0530, Kathiravan T wrote:
> Due to the recent design changes, all the mem noc clocks will be
> configured by the bootloaders and it will be access protected by the TZ
> firmware. Also there are no comsumers for these clocks in the kernel. So
> drop these clocks from the GCC driver.
>
> With these clocks removal, remove the gcc_apss_axi_clk_src clock as well
> since no clocks uses this as a parent.
>
> [...]
Applied, thanks!
[1/2] clk: qcom: ipq5332: drop the mem noc clocks
commit: 1784d031ef1f329bd362343a8fe1c083116160af
[2/2] clk: qcom: ipq5332: drop the gcc_apss_axi_clk_src clock
commit: 90d5c043dda7901065e9da4b23967903640fd2ea
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-08-14 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 10:28 Kathiravan T
2023-07-10 10:28 ` [PATCH 1/2] clk: qcom: ipq5332: drop the mem noc clocks Kathiravan T
2023-07-15 14:10 ` Konrad Dybcio
2023-07-15 15:17 ` Kathiravan T
2023-07-10 10:28 ` [PATCH 2/2] clk: qcom: ipq5332: drop the gcc_apss_axi_clk_src clock Kathiravan T
2023-07-31 5:25 ` [PATCH 0/2] Drop the mem noc clocks from the IPQ5332 GCC driver Kathiravan T
2023-08-14 3:27 ` Bjorn Andersson [this message]
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=169198364306.2443702.8402512633493071282.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=konrad.dybcio@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=quic_anusha@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_saahtoma@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@quicinc.com \
--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
all inboxes | Powered by JetHome®