mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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>,
	Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
	 Tengfei Fan <tengfei.fan@oss.qualcomm.com>,
	Bartosz Golaszewski <brgl@kernel.org>,
	 David Wronek <davidwronek@gmail.com>,
	Luca Weiss <luca.weiss@fairphone.com>,
	 Neil Armstrong <neil.armstrong@linaro.org>,
	Melody Olvera <quic_molvera@quicinc.com>,
	 Alexander Koskovich <akoskovich@pm.me>,
	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>,
	 Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
Subject: Re: [PATCH v3 01/12] dt-bindings: crypto: qcom,ice: Allow power-domain and iface clk
Date: Wed, 18 Mar 2026 08:22:04 +0100	[thread overview]
Message-ID: <20260318-aboriginal-peach-bird-cacb8c@quoll> (raw)
In-Reply-To: <do62iaopjcahvn576gfcdbyo4yxudf4uit2sbifvjw3pwrlb7j@higm25fdesk3>

On Tue, Mar 17, 2026 at 05:12:36PM +0200, Dmitry Baryshkov wrote:
> On Tue, Mar 17, 2026 at 02:50:40PM +0530, Harshal Dev wrote:
> > Update the inline-crypto engine DT binding in a backward compatible manner
> > to allow specifying up to two clocks along with their names and associated
> > power-domain.
> 
> This should come after the "why" part.
> 
> > 
> > When the 'clk_ignore_unused' flag is not passed on the kernel command line
> > occasional unclocked ICE hardware register access are observed when the
> > kernel disables the unused 'iface' clock before ICE can probe. 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 could happen.
> 
> You can simply say that ICE requires these clocks and these power
> domains to function. Accessing the hardware can fail if they are
> disabled by the kernel for whater reasons.

Yeah, mentioning clk_ignore_unused/pd is redundant here.

> 
> > 
> > To avoid these scenarios, the 'iface' clock and the associated power-domain
> > should be specified in the ICE device tree node and enabled by ICE.

And this repeats the first paragraph.

> > 
> > 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 876bf90ed96e..99c541e7fa8c 100644
> > --- a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> > +++ b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> > @@ -30,6 +30,16 @@ properties:
> >      maxItems: 1
> >  
> >    clocks:
> > +    minItems: 1
> > +    maxItems: 2
> > +
> > +  clock-names:
> > +    minItems: 1
> > +    items:
> > +      - const: core
> > +      - const: iface
> > +
> > +  power-domains:
> >      maxItems: 1

I do not see how you implemented my feedback, at all. Nothing from it.

I even provided you final clarifications. What is the point of asking me
for the third time, again, what should you do, if you just ignore it?

1. What the DTS is doing here?
2. How did you address "with explanation why this is a fix thus why this
should go to current cycle." - where is this part?
3. Where is Eliza and Milos?

I was repeating the last 2 points multiple times already.

Best regards,
Krzysztof


  parent reply	other threads:[~2026-03-18  7:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17  9:20 [PATCH v3 00/12] Add explicit clock vote and enable power-domain for QCOM-ICE Harshal Dev
2026-03-17  9:20 ` [PATCH v3 01/12] dt-bindings: crypto: qcom,ice: Allow power-domain and iface clk Harshal Dev
2026-03-17 15:12   ` Dmitry Baryshkov
2026-03-18  7:21     ` Harshal Dev
2026-03-18  7:22     ` Krzysztof Kozlowski [this message]
2026-03-18 10:30       ` Harshal Dev
2026-03-18 11:33         ` Krzysztof Kozlowski
2026-03-17  9:20 ` [PATCH v3 02/12] dt-bindings: crypto: qcom,ice: Require " Harshal Dev
2026-03-17 15:13   ` Dmitry Baryshkov
2026-03-18  7:27     ` Krzysztof Kozlowski
2026-03-18 10:32       ` Harshal Dev
2026-03-18  7:23   ` Krzysztof Kozlowski
2026-03-18 10:33     ` Harshal Dev
2026-03-17  9:20 ` [PATCH v3 03/12] arm64: dts: qcom: kaanapali: Add power-domain and iface clk for ice node Harshal Dev
2026-03-17  9:20 ` [PATCH v3 04/12] arm64: dts: qcom: lemans: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 05/12] arm64: dts: qcom: monaco: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 06/12] arm64: dts: qcom: sc7180: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 07/12] arm64: dts: qcom: kodiak: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 08/12] arm64: dts: qcom: sm8450: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 09/12] arm64: dts: qcom: sm8550: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 10/12] arm64: dts: qcom: sm8650: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 11/12] arm64: dts: qcom: sm8750: " Harshal Dev
2026-03-17  9:20 ` [PATCH v3 12/12] soc: qcom: ice: Allow explicit votes on 'iface' clock for ICE Harshal Dev
2026-03-18  7:33   ` Krzysztof Kozlowski
2026-03-18 10:39     ` 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=20260318-aboriginal-peach-bird-cacb8c@quoll \
    --to=krzk@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=akoskovich@pm.me \
    --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=kuldeep.singh@oss.qualcomm.com \
    --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=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

all inboxes | Powered by JetHome®