linux-kernel - Re: [PATCH v6 1/5] dt-bindings: remoteproc: Add PRU consumer bindings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78805233-0802-7a7e-f1b1-84c566084833@linaro.org>
Date:   Wed, 12 Oct 2022 11:24:59 -0400
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     MD Danish Anwar <danishanwar@...com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Mathieu Poirier <mathieu.poirier@...aro.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc:     Suman Anna <s-anna@...com>, Roger Quadros <rogerq@...nel.org>,
        nm@...com, vigneshr@...com, srk@...com,
        linux-remoteproc@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Tero Kristo <t-kristo@...com>,
        Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>,
        Puranjay Mohan <p-mohan@...com>
Subject: Re: [PATCH v6 1/5] dt-bindings: remoteproc: Add PRU consumer bindings

On 12/10/2022 07:44, MD Danish Anwar wrote:
> From: Suman Anna <s-anna@...com>
> 
> Add a YAML binding document for PRU consumers. The binding includes

Add a DT schema binding for ...

Second thing: where is a user of this common binding? How do you apply
this schema to anything?

> all the common properties that can be used by different PRU consumer
> or application nodes and supported by the PRU remoteproc driver.
> These are used to configure the PRU hardware for specific user
> applications.
> 
> The application nodes themselves should define their own bindings.
> 
> Co-developed-by: Tero Kristo <t-kristo@...com>
> Signed-off-by: Tero Kristo <t-kristo@...com>
> Signed-off-by: Suman Anna <s-anna@...com>
> Co-developed-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>
> Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>
> Signed-off-by: Puranjay Mohan <p-mohan@...com>
> Signed-off-by: MD Danish Anwar <danishanwar@...com>
> ---
>  .../bindings/remoteproc/ti,pru-consumer.yaml  | 132 ++++++++++++++++++
>  1 file changed, 132 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml
> 
> diff --git a/Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml b/Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml
> new file mode 100644
> index 000000000000..16be98b7d600
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml
> @@ -0,0 +1,132 @@
> +# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/remoteproc/ti,pru-consumer.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Common TI PRU Consumer Binding
> +
> +maintainers:
> +  - Suman Anna <s-anna@...com>
> +
> +description: |
> +  A PRU application/consumer/user node typically uses one or more PRU device
> +  nodes to implement a PRU application/functionality. Each application/client
> +  node would need a reference to at least a PRU node, and optionally define
> +  some properties needed for hardware/firmware configuration. The below
> +  properties are a list of common properties supported by the PRU remoteproc
> +  infrastructure.
> +
> +  The application nodes shall define their own bindings like regular platform
> +  devices, so below are in addition to each node's bindings.
> +
> +properties:
> +  ti,prus:
> +    $ref: /schemas/types.yaml#/definitions/phandle-array
> +    description: phandles to the PRU, RTU or Tx_PRU nodes used
> +    minItems: 1
> +    maxItems: 6
> +    items:
> +      maxItems: 1
> +
> +  firmware-name:
> +    $ref: /schemas/types.yaml#/definitions/string-array
> +    minItems: 1
> +    maxItems: 6
> +    description: |
> +      firmwares for the PRU cores, the default firmware for the core from
> +      the PRU node will be used if not provided. The firmware names should
> +      correspond to the PRU cores listed in the 'ti,prus' property
> +
> +  ti,pruss-gp-mux-sel:
> +    $ref: /schemas/types.yaml#/definitions/uint32-array
> +    minItems: 1
> +    maxItems: 6
> +    items:
> +      enum: [0, 1, 2, 3, 4]
> +    description: |
> +      array of values for the GP_MUX_SEL under PRUSS_GPCFG register for a PRU.
> +      This selects the internal muxing scheme for the PRU instance. Values
> +      should correspond to the PRU cores listed in the 'ti,prus' property. The
> +      GP_MUX_SEL setting is a per-slice setting (one setting for PRU0, RTU0,
> +      and Tx_PRU0 on K3 SoCs). Use the same value for all cores within the
> +      same slice in the associative array. If the array size is smaller than
> +      the size of 'ti,prus' property, the default out-of-reset value (0) for the
> +      PRU core is used.
> +
> +required:
> +  - ti,prus
> +
> +additionalProperties: true
> +
> +examples:
> +  - |
> +    /* PRU application node full example */
> +    icssg2_eth: icssg2-eth {
> +      compatible = "ti,am654-icssg-prueth";
> +      pinctrl-names = "default";
> +      pinctrl-0 = <&icssg2_rgmii_pins_default>;
> +      sram = <&msmc_ram>;
> +      ti,prus = <&pru2_0>, <&rtu2_0>, <&tx_pru2_0>,
> +        <&pru2_1>, <&rtu2_1>, <&tx_pru2_1>;

Fix alignment. In other places as well.


> +      firmware-name = "ti-pruss/am65x-sr2-pru0-prueth-fw.elf",
> +          "ti-pruss/am65x-sr2-rtu0-prueth-fw.elf",
> +          "ti-pruss/am65x-sr2-txpru0-prueth-fw.elf",
> +          "ti-pruss/am65x-sr2-pru1-prueth-fw.elf",
> +          "ti-pruss/am65x-sr2-rtu1-prueth-fw.elf",
> +          "ti-pruss/am65x-sr2-txpru1-prueth-fw.elf";
> +

Best regards,
Krzysztof