From: Krzysztof Kozlowski <krzk@kernel.org>
To: Herman van Hazendonk <github.com@herrie.org>,
Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: clock: qcom,gcc-msm8660: add CE2_P_CLK, PLL4_VOTE + per-clock annotations
Date: Sun, 31 May 2026 09:57:05 +0200 [thread overview]
Message-ID: <53f65444-0560-4e4b-8929-ebc01009294b@kernel.org> (raw)
In-Reply-To: <c36dcf40802d89a4b43255394386fff974a6301c.1780197117.git.github.com@herrie.org>
On 31/05/2026 06:08, Herman van Hazendonk wrote:
> Annotate each clock with provenance and consumer information cross-
> referenced against the GCC driver, the downstream HTC/Samsung/Palm
> sources and the legacy TouchPad / Pre3 vendor trees, so reviewers
> adding new MSM8x60 board DTs can tell at a glance whether a given
> clock is wired up in the GCC driver, in the device tree, or both.
I don't understand what problem you are solving. ABI is fixed, you
cannot change it. This document does not describe usage, but ABI with
clock IDs.
I suggest to start commit msg with clear description of existing problem.
>
> Add two clocks that the in-tree driver and downstream consumers
> already use but which were missing from the header:
>
> - CE2_P_CLK (Crypto Engine 2 APB) - needed by drivers/crypto/qce
> for the MSM8x60 CE2 path that the qcom,msm8660-qce binding adds.
> - PLL4_VOTE - software-vote handle for the LPASS PLL4 used by both
> lcc-msm8660 and the modem subsystem.
Don't mix up completely independent work.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-05-31 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 13:57 [PATCH] dt-bindings: clock: qcom,gcc-msm8660: collision fixes + per-clock annotations Herman van Hazendonk
2026-05-30 14:14 ` sashiko-bot
[not found] ` <c36dcf40802d89a4b43255394386fff974a6301c.1780197117.git.github.com@herrie.org>
2026-05-31 4:32 ` [PATCH v2] dt-bindings: clock: qcom,gcc-msm8660: add CE2_P_CLK, PLL4_VOTE " sashiko-bot
2026-05-31 7:57 ` Krzysztof Kozlowski [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=53f65444-0560-4e4b-8929-ebc01009294b@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=github.com@herrie.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=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