[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200713182834.GA494208@bogus>
Date: Mon, 13 Jul 2020 12:28:34 -0600
From: Rob Herring <robh@...nel.org>
To: Suman Anna <s-anna@...com>
Cc: Bjorn Andersson <bjorn.andersson@...aro.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Lokesh Vutla <lokeshvutla@...com>,
Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>,
linux-remoteproc@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/6] dt-bindings: remoteproc: Add common TI SCI rproc
bindings
On Fri, Jun 12, 2020 at 05:49:11PM -0500, Suman Anna wrote:
> Add a bindings document that lists the common TI SCI properties
> used by the K3 R5F and DSP remoteproc devices.
>
> Signed-off-by: Suman Anna <s-anna@...com>
> ---
> v3: New Patch refactoring out the common ti-sci-proc properties
>
> .../bindings/remoteproc/ti,k3-sci-proc.yaml | 51 +++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-sci-proc.yaml
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/ti,k3-sci-proc.yaml b/Documentation/devicetree/bindings/remoteproc/ti,k3-sci-proc.yaml
> new file mode 100644
> index 000000000000..883b6e9b5282
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/remoteproc/ti,k3-sci-proc.yaml
> @@ -0,0 +1,51 @@
> +# SPDX-License-Identifier: (GPL-2.0-only or BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/remoteproc/ti,k3-sci-proc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Common TI K3 remote processor device bindings
> +
> +maintainers:
> + - Suman Anna <s-anna@...com>
> +
> +description: |
> + The TI K3 family of SoCs usually have one or more remote processor sub-systems
> + like the dual-core R5F sub-system or a C66x or C71x DSP processor subsystem.
> + The device management of these remote processors is managed by a dedicated
> + System Processor, and the communication with that processor is managed through
> + the TI-SCI protocol.
> +
> + Each remote processor device node should define a common set of properties
> + that allows the System Processor firmware to perform the device management
> + such as powering the IPs, asserting/deasserting the resets for each of these
> + processors.
> +
> +properties:
> + ti,sci:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + Should be a phandle to the TI-SCI System Controller node
> +
> + ti,sci-dev-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: |
> + Should contain the TI-SCI device id corresponding to the remote processor
> + core. Please refer to the corresponding System Controller documentation
> + for valid values.
> +
> + ti,sci-proc-ids:
> + description: Should contain a single tuple of <proc_id host_id>.
> + allOf:
You can drop allOf now.
> + - $ref: /schemas/types.yaml#/definitions/uint32-array
> + - maxItems: 1
> + items:
You don't need 'maxItems' or 1st 'items' here.
> + items:
> + - description: TI-SCI processor id for the remote processor device
> + - description: TI-SCI host id to which processor control
> + ownership should be transferred to
> +
> +required:
> + - ti,sci
> + - ti,sci-dev-id
> + - ti,sci-proc-ids
> --
> 2.26.0
>
Powered by blists - more mailing lists