public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nipun Gupta <nipun.gupta@amd.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org, krzk+dt@kernel.org,
	gregkh@linuxfoundation.org, robh@kernel.org,
	 conor+dt@kernel.org, ogabbay@kernel.org,
	maarten.lankhorst@linux.intel.com,  mripard@kernel.org,
	tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
	 derek.kiernan@amd.com, dragan.cvetic@amd.com, arnd@arndb.de,
	praveen.jain@amd.com,  harpreet.anand@amd.com,
	nikhil.agarwal@amd.com, srivatsa@csail.mit.edu, code@tyhicks.com,
	 ptsm@linux.microsoft.com
Subject: Re: [PATCH v2 1/3] dt-bindings: accel: add device tree for AMD PKI accelerator
Date: Thu, 10 Apr 2025 09:29:28 +0200	[thread overview]
Message-ID: <20250410-flat-violet-bull-a2a0b7@shite> (raw)
In-Reply-To: <20250409173033.2261755-1-nipun.gupta@amd.com>

On Wed, Apr 09, 2025 at 11:00:31PM GMT, Nipun Gupta wrote:
> Add binding documentation for AMD PKI accelerator supported for AMD
> versal-net SoC.
>

A nit, subject: drop second/last, redundant "device tree for". The
"dt-bindings" prefix is already stating that these are bindings.
See also:
https://elixir.bootlin.com/linux/v6.7-rc8/source/Documentation/devicetree/bindings/submitting-patches.rst#L18

You already got this comment...

> AMD PKI accelerator is a device on AMD versa-net SoC to execute public key
> asymmetric crypto operations like ECDSA, ECDH, RSA etc. with high performance.
> The driver provides accel interface to applications for configuring the device
> and performing the required operations. AMD PKI device comprises of multiple
> Barco Silex ba414 PKI engines bundled together, and providing a queue based
> interface to interact with the device.

...

> 
>  .../bindings/accel/amd,versal-net-pki.yaml    | 58 +++++++++++++++++++
>  MAINTAINERS                                   |  8 +++
>  2 files changed, 66 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/accel/amd,versal-net-pki.yaml

That's a crypto device, so goes to 'crypto' directory.

> 
> diff --git a/Documentation/devicetree/bindings/accel/amd,versal-net-pki.yaml b/Documentation/devicetree/bindings/accel/amd,versal-net-pki.yaml
> new file mode 100644
> index 000000000000..2dca7458f845
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/accel/amd,versal-net-pki.yaml
> @@ -0,0 +1,58 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/accel/amd,versal-net-pki.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: AMD PKI accelerator device
> +
> +maintainers:
> +  - Nipun Gupta <nipun.gupta@amd.com>
> +  - Praveen Jain <praveen.jain@amd.com>
> +
> +description: |
> +  AMD PKI accelerator handles the public key asymmetric crypto operations.
> +  The driver provides accel interface to the application for configuring the
> +  device and performing the required operations. AMD PKI device comprises of
> +  multiple Barco Silex ba414 PKI engines bundled together, and providing a
> +  queue based interface to interact with these devices on AMD versal-net SoC.
> +
> +  Link to ba414 datasheet:
> +  https://datasheet.datasheetarchive.com/originals/crawler/barco-silex.com/34b540b9dc5db40c5bc01999401cf1e4.pdf
> +
> +properties:
> +  compatible:
> +    const: amd,versal-net-pki
> +
> +  reg:
> +    description: AMD PKI register space

Drop description, obvious.

> +    maxItems: 1
> +
> +  interrupts:
> +    maxItems: 1
> +

And the resets? I understand from previous email that there is a reset controller.

> +  iommus: true
> +
> +required:
> +  - compatible
> +  - reg
> +  - interrupts
> +  - iommus
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> +    bus {
> +        #address-cells = <2>;
> +        #size-cells = <2>;
> +
> +        amdpk@20400000000 {

crypto@

> +            compatible = "amd,versal-net-pki";
> +            interrupts = <GIC_SPI 155 IRQ_TYPE_LEVEL_HIGH>;
> +            reg = <0x204 0x00000000 0x0 0x10000>;
> +            iommus = <&smmu 0x25b>;
> +        };
> +    };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 96b827049501..11f8815daa77 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1154,6 +1154,14 @@ F:	Documentation/networking/device_drivers/ethernet/amd/pds_core.rst
>  F:	drivers/net/ethernet/amd/pds_core/
>  F:	include/linux/pds/
> 
> +AMD PKI DRIVER
> +M:	Nipun Gupta <nipun.gupta@amd.com>
> +M:	Praveen Jain <praveen.jain@amd.com>
> +L:	dri-devel@lists.freedesktop.org
> +S:	Maintained
> +T:	git https://gitlab.freedesktop.org/drm/misc/kernel.git

Are you going to apply patches to this tree?

Best regards,
Krzysztof


  parent reply	other threads:[~2025-04-10  7:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 17:30 [PATCH v2 1/3] dt-bindings: accel: add device tree for AMD PKI accelerator Nipun Gupta
2025-04-09 17:30 ` [PATCH v2 2/3] accel/amdpk: add driver " Nipun Gupta
2025-04-10  7:36   ` Krzysztof Kozlowski
2025-04-11  4:51     ` Gupta, Nipun
2025-04-11  5:17       ` Herbert Xu
2025-04-11 18:20         ` Gupta, Nipun
2025-04-12  1:23           ` Herbert Xu
2025-04-17 15:32             ` Gupta, Nipun
2025-04-20  6:39               ` Herbert Xu
2025-04-13 18:52       ` Lukas Wunner
2025-04-16 15:11         ` Gupta, Nipun
2025-04-11 16:34   ` Jeff Hugo
2025-04-16 10:41   ` kernel test robot
2025-04-09 17:30 ` [PATCH v2 3/3] accel/amdpk: add debugfs support Nipun Gupta
2025-04-10  7:29 ` Krzysztof Kozlowski [this message]
2025-04-11 18:18   ` [PATCH v2 1/3] dt-bindings: accel: add device tree for AMD PKI accelerator Gupta, Nipun
2025-04-11 16:16 ` Jeff Hugo

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=20250410-flat-violet-bull-a2a0b7@shite \
    --to=krzk@kernel.org \
    --cc=airlied@gmail.com \
    --cc=arnd@arndb.de \
    --cc=code@tyhicks.com \
    --cc=conor+dt@kernel.org \
    --cc=derek.kiernan@amd.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dragan.cvetic@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=harpreet.anand@amd.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nikhil.agarwal@amd.com \
    --cc=nipun.gupta@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=praveen.jain@amd.com \
    --cc=ptsm@linux.microsoft.com \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=srivatsa@csail.mit.edu \
    --cc=tzimmermann@suse.de \
    /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