From: Rob Herring <robh@kernel.org>
To: Sumit Gupta <sumitg@nvidia.com>
Cc: rjw@rjwysocki.net, viresh.kumar@linaro.org,
catalin.marinas@arm.com, will@kernel.org,
thierry.reding@gmail.com, mirq-linux@rere.qmqm.pl,
devicetree@vger.kernel.org, jonathanh@nvidia.com,
talho@nvidia.com, linux-pm@vger.kernel.org,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bbasu@nvidia.com,
mperttunen@nvidia.com
Subject: Re: [TEGRA194_CPUFREQ PATCH v6 1/4] dt-bindings: arm: Add NVIDIA Tegra194 CPU Complex binding
Date: Tue, 14 Jul 2020 14:47:42 -0600 [thread overview]
Message-ID: <20200714204742.GA2875540@bogus> (raw)
In-Reply-To: <1594742870-19957-1-git-send-email-sumitg@nvidia.com>
On Tue, Jul 14, 2020 at 09:37:50PM +0530, Sumit Gupta wrote:
> Add device-tree binding documentation to represent Tegra194
> CPU Complex with compatible string under 'cpus' node. This
> can be used by drivers like cpufreq which don't have their
> node or CPU Complex node to bind to. Also, documenting
> 'nvidia,bpmp' property which points to BPMP device.
>
> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
> ---
> .../bindings/arm/nvidia,tegra194-ccplex.yaml | 106 +++++++++++++++++++++
> 1 file changed, 106 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/nvidia,tegra194-ccplex.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/nvidia,tegra194-ccplex.yaml b/Documentation/devicetree/bindings/arm/nvidia,tegra194-ccplex.yaml
> new file mode 100644
> index 0000000..06dbdaa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/nvidia,tegra194-ccplex.yaml
> @@ -0,0 +1,106 @@
> +# SPDX-License-Identifier: GPL-2.0
Dual license please.
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/arm/nvidia,tegra194-ccplex.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: NVIDIA Tegra194 CPU Complex device tree bindings
> +
> +maintainers:
> + - Thierry Reding <thierry.reding@gmail.com>
> + - Jonathan Hunter <jonathanh@nvidia.com>
> + - Sumit Gupta <sumitg@nvidia.com>
> +
> +description: |+
> + Tegra194 SOC has homogeneous architecture where each cluster has two
> + symmetric cores. Compatible string in "cpus" node represents the CPU
> + Complex having all clusters.
> +
> +properties:
$nodename:
const: cpus
> + compatible:
> + enum:
> + - nvidia,tegra194-ccplex
> +
> + nvidia,bpmp:
> + $ref: '/schemas/types.yaml#/definitions/phandle'
> + description: |
> + Specifies the bpmp node that needs to be queried to get
> + operating point data for all CPUs.
> +
> + Optional for systems that have a "compatible"
> + property value of "nvidia,tegra194-ccplex".
The schema says this already.
> +
> + "#address-cells":
> + const: 1
This is wrong. The binding says it's 2 cells on aarch64 cpus though we
don't enforce that.
> +
> + "#size-cells":
> + const: 0
> +
> +dependencies:
> + nvidia,bpmp: [compatible]
This is kind of redundant as 'compatible' is required in order to apply
the schema.
> +
> +examples:
> + - |
> + cpus {
> + compatible = "nvidia,tegra194-ccplex";
> + nvidia,bpmp = <&bpmp>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + cpu0_0: cpu@0 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x0>;
> + enable-method = "psci";
> + };
> +
> + cpu0_1: cpu@1 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x001>;
> + enable-method = "psci";
> + };
> +
> + cpu1_0: cpu@100 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x100>;
> + enable-method = "psci";
> + };
> +
> + cpu1_1: cpu@101 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x101>;
> + enable-method = "psci";
> + };
> +
> + cpu2_0: cpu@200 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x200>;
> + enable-method = "psci";
> + };
> +
> + cpu2_1: cpu@201 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x201>;
> + enable-method = "psci";
> + };
> +
> + cpu3_0: cpu@300 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x300>;
> + enable-method = "psci";
> + };
> +
> + cpu3_1: cpu@301 {
> + compatible = "nvidia,tegra194-carmel";
> + device_type = "cpu";
> + reg = <0x301>;
> + enable-method = "psci";
> + };
Not really that useful describing all these cpus.
> + };
> +...
> --
> 2.7.4
>
next prev parent reply other threads:[~2020-07-14 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 14:06 [TEGRA194_CPUFREQ PATCH v5 0/4] Add cpufreq driver for Tegra194 Sumit Gupta
2020-07-13 14:06 ` [TEGRA194_CPUFREQ PATCH v5 1/4] dt-bindings: arm: Add t194 ccplex compatible and bpmp property Sumit Gupta
2020-07-13 16:42 ` Rob Herring
2020-07-14 11:43 ` Sumit Gupta
2020-07-14 13:46 ` Rob Herring
2020-07-14 16:07 ` [TEGRA194_CPUFREQ PATCH v6 1/4] dt-bindings: arm: Add NVIDIA Tegra194 CPU Complex binding Sumit Gupta
2020-07-14 20:47 ` Rob Herring [this message]
2020-07-15 10:22 ` Sumit Gupta
2020-07-14 16:14 ` [TEGRA194_CPUFREQ PATCH v5 1/4] dt-bindings: arm: Add t194 ccplex compatible and bpmp property Sumit Gupta
2020-07-13 14:06 ` [TEGRA194_CPUFREQ PATCH v5 2/4] arm64: tegra: " Sumit Gupta
2020-07-13 14:06 ` [TEGRA194_CPUFREQ PATCH v5 3/4] cpufreq: Add Tegra194 cpufreq driver Sumit Gupta
2020-07-15 11:16 ` Viresh Kumar
2020-07-15 12:31 ` Sumit Gupta
2020-07-13 14:06 ` [TEGRA194_CPUFREQ PATCH v5 4/4] soc/tegra: cpufreq: select cpufreq for Tegra194 Sumit Gupta
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=20200714204742.GA2875540@bogus \
--to=robh@kernel.org \
--cc=bbasu@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=mperttunen@nvidia.com \
--cc=rjw@rjwysocki.net \
--cc=sumitg@nvidia.com \
--cc=talho@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=viresh.kumar@linaro.org \
--cc=will@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).