mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: hangsuan.wang@altera.com,
	linux-kernel <linux-kernel@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Thierry Reding <treding@nvidia.com>, Lee Jones <lee@kernel.org>,
	Romain Gantois <romain.gantois@bootlin.com>,
	Andrea della Porta <andrea.porta@suse.com>,
	Andrei Simion <andrei.simion@microchip.com>,
	Dinh Nguyen <dinguyen@kernel.org>,
	Mahesh Rao <mahesh.rao@altera.com>
Cc: Marek <marex@denx.de>, Simon <simon.k.r.goldschmidt@gmail.com>,
	linux-drivers-review@altera.com,
	Muhammad Amirul Asyraf Mohamad Jamian
	<muhammad.amirul.asyraf.mohamad.jamian@altera.com>,
	Khairul Anuar Romli <khairul.anuar.romli@altera.com>
Subject: Re: [PATCH 2/4] dt-bindings: firmware: stratix10-svc: add fcs-config property
Date: Sat, 13 Dec 2025 04:21:21 +0100	[thread overview]
Message-ID: <3cfea9e6-0cc6-406f-9a4c-3564ef1e3569@kernel.org> (raw)
In-Reply-To: <c5b2e76a7dd04d2143580c4574def095d3f0550c.1765534135.git.hang.suan.wang@altera.com>

On 12/12/2025 12:35, hangsuan.wang@altera.com wrote:
> From: "Wang, Hang Suan" <hangsuan.wang@altera.com>
> 
> Altera SoC FPGA Crypto Service (fcs) provide hardware crypto features
> through mailbox. Fcs property has to be added to compliance with device
> tree schema fcs bindings and driver.

Last sentence is completely redundant. If you add new devices for some
"compliance" you do it wrong. We don't build hardware for "dt compliance"...

> 
> Signed-off-by: Wang, Hang Suan <hangsuan.wang@altera.com>
> ---
> ---
>  .../devicetree/bindings/firmware/intel,stratix10-svc.yaml     | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/firmware/intel,stratix10-svc.yaml b/Documentation/devicetree/bindings/firmware/intel,stratix10-svc.yaml
> index b42cfa78b28b..c105f8dc4b7d 100644
> --- a/Documentation/devicetree/bindings/firmware/intel,stratix10-svc.yaml
> +++ b/Documentation/devicetree/bindings/firmware/intel,stratix10-svc.yaml
> @@ -62,6 +62,10 @@ properties:
>      $ref: /schemas/fpga/intel,stratix10-soc-fpga-mgr.yaml
>      description: Optional child node for fpga manager to perform fabric configuration.
>  
> +  fcs-config:
> +    $ref: /schemas/misc/intel,agilex5-soc-fcs-config.yaml
> +    description: Optional child node for fcs Fpga Crypto Service (fcs) to perform SoC Crypto Engine.

You need to wrap according to Linux coding style. Anyway, above schema
is NAKed so is this child.

> +
>  required:
>    - compatible
>    - method


Best regards,
Krzysztof

  reply	other threads:[~2025-12-13  3:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 11:35 [PATCH 0/4] Add Device Tree binding and nodes for Agilex5/Agilex SOC FCS configuration hangsuan.wang
2025-12-12 11:35 ` [PATCH 1/4] dt-bindings: misc: agilex5-soc-fcs-config: Add binding hangsuan.wang
2025-12-13  3:20   ` Krzysztof Kozlowski
2025-12-12 11:35 ` [PATCH 2/4] dt-bindings: firmware: stratix10-svc: add fcs-config property hangsuan.wang
2025-12-13  3:21   ` Krzysztof Kozlowski [this message]
2025-12-12 11:35 ` [PATCH 3/4] arm64: dts: socfpga: agilex5: add fcs node hangsuan.wang
2025-12-12 11:35 ` [PATCH 4/4] arm64: dts: socfpga: agilex: " hangsuan.wang
2025-12-12 16:45 ` [PATCH 0/4] Add Device Tree binding and nodes for Agilex5/Agilex SOC FCS configuration Wang, Hang Suan
2025-12-13  3:22   ` Krzysztof Kozlowski
2025-12-13  3:24 ` Krzysztof Kozlowski
2025-12-14 14:25 ` Lee Jones

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=3cfea9e6-0cc6-406f-9a4c-3564ef1e3569@kernel.org \
    --to=krzk@kernel.org \
    --cc=andrea.porta@suse.com \
    --cc=andrei.simion@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=hangsuan.wang@altera.com \
    --cc=khairul.anuar.romli@altera.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-drivers-review@altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mahesh.rao@altera.com \
    --cc=marex@denx.de \
    --cc=muhammad.amirul.asyraf.mohamad.jamian@altera.com \
    --cc=robh@kernel.org \
    --cc=romain.gantois@bootlin.com \
    --cc=simon.k.r.goldschmidt@gmail.com \
    --cc=treding@nvidia.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®