From: Krzysztof Kozlowski <krzk@kernel.org>
To: Harshal Dev <harshal.dev@oss.qualcomm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abel.vesa@oss.qualcomm.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
cros-qcom-dts-watchers@chromium.org,
Eric Biggers <ebiggers@google.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
Tengfei Fan <tengfei.fan@oss.qualcomm.com>,
Bartosz Golaszewski <brgl@kernel.org>,
Yuvaraj Ranganathan <quic_yrangana@quicinc.com>,
David Wronek <davidwronek@gmail.com>,
Luca Weiss <luca.weiss@fairphone.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Melody Olvera <quic_molvera@quicinc.com>
Cc: Brian Masney <bmasney@redhat.com>,
Neeraj Soni <neeraj.soni@oss.qualcomm.com>,
Gaurav Kashyap <gaurav.kashyap@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2 01/11] dt-bindings: crypto: qcom,ice: Allow power-domain and iface clk
Date: Wed, 11 Mar 2026 19:25:36 +0100 [thread overview]
Message-ID: <b2d852c4-9f52-4ad4-a916-ced19c599938@kernel.org> (raw)
In-Reply-To: <a2d6c630-e4df-4cdf-8b10-64d87d24bf8f@oss.qualcomm.com>
On 11/03/2026 10:37, Harshal Dev wrote:
>
>
> On 3/11/2026 1:55 AM, Krzysztof Kozlowski wrote:
>> On 10/03/2026 09:06, Harshal Dev wrote:
>>> Update the inline-crypto engine DT binding to allow specifying up to two
>>> clocks along with their names and associated power-domain. When the
>>> 'clk_ignore_unused' flag is not passed on the kernel command line
>>> occasional unclocked ICE hardware register access are observed during ICE
>>> driver probe based on the relative timing between the probe and the kernel
>>> disabling the unused clocks. On the other hand, when the 'pd_ignore_unused'
>>> flag is not passed on the command line, clock 'stuck' issues are
>>> observed if the power-domain required by ICE hardware is unused and thus
>>> disabled before ICE probe. To avoid these scenarios, the 'iface' clock and
>>> the associated power-domain should be specified in the ICE device tree node
>>> and the 'iface' clock should be voted on by the ICE driver during probe.
>>>
>>> Fixes: f6ff91a47ac57 ("dt-bindings: crypto: Add Qualcomm Inline Crypto Engine")
>>> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
>>> ---
>>> .../bindings/crypto/qcom,inline-crypto-engine.yaml | 16 +++++++++++++++-
>>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
>>> index c3408dcf5d20..d9a0a8adf645 100644
>>> --- a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
>>> +++ b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
>>> @@ -28,6 +28,16 @@ properties:
>>> maxItems: 1
>>>
>>> clocks:
>>> + minItems: 1
>>> + maxItems: 2
>>> +
>>> + clock-names:
>>> + minItems: 1
>>> + items:
>>> + - const: ice_core_clk
>>
>> core
>
> Ack. I'll introduce a check for this specific name here as well:
> https://elixir.bootlin.com/linux/v7.0-rc3/source/drivers/soc/qcom/ice.c#L582
>
>>
>>> + - const: iface_clk
>>
>> iface or bus
>
> Ack, will call it 'iface'.
>
>>
>> I don't understand why this is flexible and commit msg does not explain
>> that. Devices do not have one and two clocks at the same time. You miss
>> proper constraints.
>>
>
> I agree, it might confuse someone reading the commit message the first time.
> I'll re-write the commit message to make it explicit that even though these
> two properties are 'required', for the time being we are introducing 'iface'
> clk and 'power-domain' as an optional property to maintain bisectability,
> and that the properties would be made 'required' in a subsequent commit once
> the DTS changes which are part of this patch series have reached the top tree.
>
> Let me know if any concerns with this kind of commit message.
So you are adding it for backwards compatibility? It's fine then,
although I had impression you are fixing something which is not working
correctly. New devices will need to constrain this.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-11 18:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 8:06 [PATCH v2 00/11] Add explicit clock vote and enable power-domain for QCOM-ICE Harshal Dev
2026-03-10 8:06 ` [PATCH v2 01/11] dt-bindings: crypto: qcom,ice: Allow power-domain and iface clk Harshal Dev
2026-03-10 14:13 ` Konrad Dybcio
2026-03-11 8:56 ` Harshal Dev
2026-03-10 20:25 ` Krzysztof Kozlowski
2026-03-11 9:37 ` Harshal Dev
2026-03-11 18:25 ` Krzysztof Kozlowski [this message]
2026-03-11 18:28 ` Krzysztof Kozlowski
2026-03-13 11:45 ` Harshal Dev
2026-03-13 15:58 ` Krzysztof Kozlowski
2026-03-16 10:56 ` Harshal Dev
2026-03-16 11:09 ` Krzysztof Kozlowski
2026-03-16 12:38 ` Harshal Dev
2026-03-10 8:06 ` [PATCH v2 02/11] arm64: dts: qcom: kaanapali: Add power-domain and iface clk for ice node Harshal Dev
2026-03-10 14:12 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 03/11] arm64: dts: qcom: lemans: " Harshal Dev
2026-03-10 14:12 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 04/11] arm64: dts: qcom: monaco: " Harshal Dev
2026-03-10 14:12 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 05/11] arm64: dts: qcom: sc7180: " Harshal Dev
2026-03-10 14:12 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 06/11] arm64: dts: qcom: kodiak: " Harshal Dev
2026-03-10 14:12 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 07/11] arm64: dts: qcom: sm8450: " Harshal Dev
2026-03-10 14:12 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 08/11] arm64: dts: qcom: sm8550: " Harshal Dev
2026-03-10 14:13 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 09/11] arm64: dts: qcom: sm8650: " Harshal Dev
2026-03-10 14:13 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 10/11] arm64: dts: qcom: sm8750: " Harshal Dev
2026-03-10 14:13 ` Konrad Dybcio
2026-03-10 8:06 ` [PATCH v2 11/11] soc: qcom: ice: Allow explicit votes on 'iface' clock for ICE Harshal Dev
2026-03-13 11:51 ` Konrad Dybcio
2026-03-16 10:58 ` Harshal Dev
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=b2d852c4-9f52-4ad4-a916-ced19c599938@kernel.org \
--to=krzk@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=davem@davemloft.net \
--cc=davidwronek@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=ebiggers@google.com \
--cc=gaurav.kashyap@oss.qualcomm.com \
--cc=harshal.dev@oss.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=neeraj.soni@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_molvera@quicinc.com \
--cc=quic_yrangana@quicinc.com \
--cc=robh@kernel.org \
--cc=tengfei.fan@oss.qualcomm.com \
/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