From: Bjorn Andersson <andersson@kernel.org>
To: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
Cc: quic_srichara@quicinc.com, quic_varada@quicinc.com
Subject: Re: [PATCH v2 0/2] Remove apss_dbg clock from IPQ5424 gcc driver
Date: Tue, 7 Jan 2025 10:38:49 -0600 [thread overview]
Message-ID: <173626793403.69400.201506218508426724.b4-ty@kernel.org> (raw)
In-Reply-To: <20241217113909.3522305-1-quic_mmanikan@quicinc.com>
On Tue, 17 Dec 2024 17:09:07 +0530, Manikanta Mylavarapu wrote:
> The gcc_apss_dbg clk is access protected by trust zone, and accessing
> it results in a kernel crash. Therefore remove the gcc_apss_dbg_clk
> from gcc driver and dt-bindings.
>
> Changes in V2:
> - Fixed all review comments from Krzysztof Kozlowski.
> - Patches were re-ordered to ensure each patch is bisectable.
> - Detailed change logs are added to the respective patches.
>
> [...]
Applied, thanks!
[1/2] clk: qcom: ipq5424: remove apss_dbg clock
commit: 5051b61d769ecc02b218499c35bee4cc1c38b7dc
[2/2] dt-bindings: clock: qcom: gcc-ipq5424: remove apss_dbg clock macro
commit: 46e6075287e68e1d3d0ea8ecda610064636e0854
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-01-07 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 11:39 [PATCH v2 0/2] Remove apss_dbg clock from IPQ5424 gcc driver Manikanta Mylavarapu
2024-12-17 11:39 ` [PATCH v2 1/2] clk: qcom: ipq5424: remove apss_dbg clock Manikanta Mylavarapu
2024-12-17 11:39 ` [PATCH v2 2/2] dt-bindings: clock: qcom: gcc-ipq5424: remove apss_dbg clock macro Manikanta Mylavarapu
2025-01-07 16:38 ` 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=173626793403.69400.201506218508426724.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.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_mmanikan@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--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