Re: [PATCH v2 1/6] dt-bindings: crypto: qcom,inline-crypto-engine: Fix legacy/new SoC strictness split
From: Krzysztof Kozlowski
Date: Fri Jul 03 2026 - 02:52:47 EST
On Thu, Jul 02, 2026 at 01:47:11AM +0530, Kuldeep Singh wrote:
> Couple of already merged SoCs describe ICE as single clock historically
> which are recently updated with mandatory 2 clocks.
>
> Keep only the known legacy compatibles flexible, and make strict
> validation default(of power-domains and 2 clocks) for all other Soc
> compatibles.
>
> This ensures old DTs are valid while ensuring any new SoC (not in the
> legacy allowlist) must follow latest requirements by default.
>
> Fixes: e27264daac7d ("dt-bindings: crypto: qcom,ice: Fix missing power-domain and iface clk")
Please drop, original codeo was correct, no bug to fix.
> Signed-off-by: Kuldeep Singh <kuldeep.singh@xxxxxxxxxxxxxxxx>
> ---
> .../bindings/crypto/qcom,inline-crypto-engine.yaml | 23 ++++++++++++++++------
> 1 file changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> index db895c50e2d2..4f3689a24410 100644
> --- a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> +++ b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> @@ -55,14 +55,25 @@ required:
>
> additionalProperties: false
>
> +# Do not extend the list.
> +# Legacy SoCs are allowed for single clock.
> +# New SoCs must provide both clocks and power domains.
> allOf:
> - if:
> - properties:
> - compatible:
> - contains:
> - enum:
> - - qcom,eliza-inline-crypto-engine
> - - qcom,milos-inline-crypto-engine
> + not:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,kaanapali-inline-crypto-engine
Your change is not equivalent in relation to hawi. Please make it
explicit in commit msg - all devices which are fixed by this.
> + - qcom,qcs8300-inline-crypto-engine
> + - qcom,sa8775p-inline-crypto-engine
> + - qcom,sc7180-inline-crypto-engine
> + - qcom,sc7280-inline-crypto-engine
> + - qcom,sm8450-inline-crypto-engine
> + - qcom,sm8550-inline-crypto-engine
> + - qcom,sm8650-inline-crypto-engine
> + - qcom,sm8750-inline-crypto-engine
Best regards,
Krzysztof