All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Wenjia Zhang" <wenjia.zhang@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: crypto: qcom,inline-crypto-engine: Add x1e80100 support
Date: Tue, 21 Jul 2026 09:32:51 +0000	[thread overview]
Message-ID: <20260721093251.AB4CC1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260721-devtool-v1-1-ade633accb41@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `qcom,x1e80100-inline-crypto-engine` compatible string was omitted from the `allOf` conditional block that enforces required properties (`power-domains` and `clock-names`).
--

--- Patch [1]: [PATCH 1/2] dt-bindings: crypto: qcom,inline-crypto-engine: Add x1e80100 support ---
commit cfe29b614f97bbb01610fe15e88b3fd50c7177bb
Author: Wenjia Zhang <wenjia.zhang@oss.qualcomm.com>

dt-bindings: crypto: qcom,inline-crypto-engine: Add x1e80100 support
    
Add the compatible string for the Qualcomm X1E80100 SoC,
which is used on the Hamoa IoT EVK board.

> diff --git a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> index db895c50e2d25..29c9a1ff638c5 100644
> --- a/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> +++ b/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml
> @@ -25,6 +25,7 @@ properties:
>            - qcom,sm8550-inline-crypto-engine
>            - qcom,sm8650-inline-crypto-engine
>            - qcom,sm8750-inline-crypto-engine
> +          - qcom,x1e80100-inline-crypto-engine

[Severity: Medium]
Does this cause a regression in schema validation by omitting the new
compatible string from the conditional block?

Looking further down in qcom,inline-crypto-engine.yaml, there is an allOf
block that enforces power-domains and clock-names:

Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml:allOf:
  - if:
      properties:
        compatible:
          contains:
            enum:
              - qcom,eliza-inline-crypto-engine
              - qcom,milos-inline-crypto-engine

    then:
      required:
        - power-domains
        - clock-names

Omitting the new qcom,x1e80100-inline-crypto-engine compatible string from
this block allows incomplete device tree nodes missing power domains or
interface clocks to pass schema validation.

Could we add the new compatible string to this enum if it shares the same
hardware constraints?

>        - const: qcom,inline-crypto-engine
>  
>    reg:

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-devtool-v1-0-ade633accb41@oss.qualcomm.com?part=1

  reply	other threads:[~2026-07-21  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  9:22 [PATCH 0/2] Enable ICE for UFS on Hamoa IoT EVK Wenjia Zhang
2026-07-21  9:22 ` [PATCH 1/2] dt-bindings: crypto: qcom,inline-crypto-engine: Add x1e80100 support Wenjia Zhang
2026-07-21  9:32   ` sashiko-bot [this message]
2026-07-21  9:22 ` [PATCH 2/2] arm64: dts: qcom: hamoa: Add ICE node for UFS inline encryption Wenjia Zhang
2026-07-21  9:53   ` 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=20260721093251.AB4CC1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wenjia.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.