From: Rob Herring <robh@kernel.org>
To: mgross@linux.intel.com
Cc: markgross@kernel.org, arnd@arndb.de, bp@suse.de,
damien.lemoal@wdc.com, dragan.cvetic@xilinx.com,
gregkh@linuxfoundation.org, corbet@lwn.net,
leonard.crestez@nxp.com, palmerdabbelt@google.com,
paul.walmsley@sifive.com, peng.fan@nxp.com, shawnguo@kernel.org,
jassisinghbrar@gmail.com, linux-kernel@vger.kernel.org,
Paul Murphy <paul.j.murphy@intel.com>,
devicetree@vger.kernel.org,
Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Subject: Re: [PATCH v2 06/34] dt-bindings: Add bindings for Keem Bay VPU IPC driver
Date: Mon, 11 Jan 2021 13:24:10 -0600 [thread overview]
Message-ID: <20210111192410.GA2906041@robh.at.kernel.org> (raw)
In-Reply-To: <20210108212600.36850-7-mgross@linux.intel.com>
On Fri, Jan 08, 2021 at 01:25:32PM -0800, mgross@linux.intel.com wrote:
> From: Paul Murphy <paul.j.murphy@intel.com>
>
> Add DT bindings documentation for the Keem Bay VPU IPC driver.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: devicetree@vger.kernel.org
> Reviewed-by: Mark Gross <mgross@linux.intel.com>
> Signed-off-by: Paul Murphy <paul.j.murphy@intel.com>
> Co-developed-by: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
> Signed-off-by: Daniele Alessandrelli <daniele.alessandrelli@intel.com>
Needs your Sob.
> ---
> .../soc/intel/intel,keembay-vpu-ipc.yaml | 153 ++++++++++++++++++
This doesn't fit somewhere else?
> 1 file changed, 153 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/soc/intel/intel,keembay-vpu-ipc.yaml
>
> diff --git a/Documentation/devicetree/bindings/soc/intel/intel,keembay-vpu-ipc.yaml b/Documentation/devicetree/bindings/soc/intel/intel,keembay-vpu-ipc.yaml
> new file mode 100644
> index 000000000000..cd1c4abe8bc9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/intel/intel,keembay-vpu-ipc.yaml
> @@ -0,0 +1,153 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright (c) Intel Corporation. All rights reserved.
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/soc/intel/intel,keembay-vpu-ipc.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Intel Keem Bay VPU IPC
> +
> +maintainers:
> + - Paul Murphy <paul.j.murphy@intel.com>
> +
> +description:
> + The VPU IPC driver facilitates loading of firmware, control, and communication
> + with the VPU over the IPC FIFO in the Intel Keem Bay SoC.
VPU is never defined.
Bindings are for h/w blocks, not drivers.
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - const: intel,keembay-vpu-ipc
> +
> + reg:
> + items:
> + - description: NCE WDT registers
> + - description: NCE TIM_GEN_CONFIG registers
> + - description: MSS WDT registers
> + - description: MSS TIM_GEN_CONFIG registers
> +
> + reg-names:
> + items:
> + - const: nce_wdt
> + - const: nce_tim_cfg
> + - const: mss_wdt
> + - const: mss_tim_cfg
> +
> + memory-region:
> + items:
> + - description: reference to the VPU reserved memory region
> + - description: reference to the X509 reserved memory region
> + - description: reference to the MSS IPC area
> +
> + clocks:
> + items:
> + - description: cpu clock
> + - description: pll 0 out 0 rate
> + - description: pll 0 out 1 rate
> + - description: pll 0 out 2 rate
> + - description: pll 0 out 3 rate
> + - description: pll 1 out 0 rate
> + - description: pll 1 out 1 rate
> + - description: pll 1 out 2 rate
> + - description: pll 1 out 3 rate
> + - description: pll 2 out 0 rate
> + - description: pll 2 out 1 rate
> + - description: pll 2 out 2 rate
> + - description: pll 2 out 3 rate
> +
> + clock-names:
> + items:
> + - const: cpu_clock
> + - const: pll_0_out_0
> + - const: pll_0_out_1
> + - const: pll_0_out_2
> + - const: pll_0_out_3
> + - const: pll_1_out_0
> + - const: pll_1_out_1
> + - const: pll_1_out_2
> + - const: pll_1_out_3
> + - const: pll_2_out_0
> + - const: pll_2_out_1
> + - const: pll_2_out_2
> + - const: pll_2_out_3
> +
> + interrupts:
> + items:
> + - description: number of NCE sub-system WDT timeout IRQ
> + - description: number of MSS sub-system WDT timeout IRQ
> +
> + interrupt-names:
> + items:
> + - const: nce_wdt
> + - const: mss_wdt
> +
> + intel,keembay-vpu-ipc-nce-wdt-redirect:
> + $ref: "/schemas/types.yaml#/definitions/uint32"
> + description:
> + Number to which we will request that the NCE sub-system
> + re-directs it's WDT timeout IRQ
> +
> + intel,keembay-vpu-ipc-mss-wdt-redirect:
> + $ref: "/schemas/types.yaml#/definitions/uint32"
> + description:
> + Number to which we will request that the MSS sub-system
> + re-directs it's WDT timeout IRQ
These look like the same value as the interrupt numbers?
> +
> + intel,keembay-vpu-ipc-imr:
> + $ref: "/schemas/types.yaml#/definitions/uint32"
> + description:
> + IMR (isolated memory region) number which we will request
> + the runtime service uses to protect the VPU memory region
> + before authentication
> +
> + intel,keembay-vpu-ipc-id:
> + $ref: "/schemas/types.yaml#/definitions/uint32"
> + description: The VPU ID to be passed to the VPU firmware.
> +
> +additionalProperties: False
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + vpu-ipc@3f00209c {
> + compatible = "intel,keembay-vpu-ipc";
> + reg = <0x3f00209c 0x10>,
> + <0x3f003008 0x4>,
> + <0x2082009c 0x10>,
> + <0x20821008 0x4>;
> + reg-names = "nce_wdt",
> + "nce_tim_cfg",
> + "mss_wdt",
> + "mss_tim_cfg";
> + memory-region = <&vpu_reserved>,
> + <&vpu_x509_reserved>,
> + <&mss_ipc_reserved>;
> + clocks = <&scmi_clk 0>,
> + <&scmi_clk 0>,
> + <&scmi_clk 1>,
> + <&scmi_clk 2>,
> + <&scmi_clk 3>,
> + <&scmi_clk 4>,
> + <&scmi_clk 5>,
> + <&scmi_clk 6>,
> + <&scmi_clk 7>,
> + <&scmi_clk 8>,
> + <&scmi_clk 9>,
> + <&scmi_clk 10>,
> + <&scmi_clk 11>;
> + clock-names = "cpu_clock",
> + "pll_0_out_0", "pll_0_out_1",
> + "pll_0_out_2", "pll_0_out_3",
> + "pll_1_out_0", "pll_1_out_1",
> + "pll_1_out_2", "pll_1_out_3",
> + "pll_2_out_0", "pll_2_out_1",
> + "pll_2_out_2", "pll_2_out_3";
> + interrupts = <GIC_SPI 63 IRQ_TYPE_LEVEL_HIGH>,
> + <GIC_SPI 47 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-names = "nce_wdt", "mss_wdt";
> + intel,keembay-vpu-ipc-nce-wdt-redirect = <63>;
> + intel,keembay-vpu-ipc-mss-wdt-redirect = <47>;
> + intel,keembay-vpu-ipc-imr = <9>;
> + intel,keembay-vpu-ipc-id = <0>;
> + };
> --
> 2.17.1
>
next prev parent reply other threads:[~2021-01-11 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210108212600.36850-1-mgross@linux.intel.com>
2021-01-08 21:25 ` [PATCH v2 04/34] dt-bindings: Add bindings for Keem Bay IPC driver mgross
2021-01-08 21:25 ` [PATCH v2 06/34] dt-bindings: Add bindings for Keem Bay VPU " mgross
2021-01-10 17:18 ` Rob Herring
2021-01-11 19:24 ` Rob Herring [this message]
2021-01-19 14:32 ` Alessandrelli, Daniele
2021-01-08 21:25 ` [PATCH v2 17/34] xlink-ipc: Add xlink ipc device tree bindings mgross
2021-01-10 17:18 ` Rob Herring
2021-01-08 21:25 ` [PATCH v2 19/34] xlink-core: Add xlink core " mgross
2021-01-10 17:18 ` Rob Herring
2021-01-11 19:27 ` Rob Herring
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=20210111192410.GA2906041@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=damien.lemoal@wdc.com \
--cc=daniele.alessandrelli@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=gregkh@linuxfoundation.org \
--cc=jassisinghbrar@gmail.com \
--cc=leonard.crestez@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=mgross@linux.intel.com \
--cc=palmerdabbelt@google.com \
--cc=paul.j.murphy@intel.com \
--cc=paul.walmsley@sifive.com \
--cc=peng.fan@nxp.com \
--cc=shawnguo@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).