From: Jiucheng Xu <jiucheng.xu@amlogic.com>
To: Robin Murphy <robin.murphy@arm.com>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>, <devicetree@vger.kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH 4/4] dt-binding:perf: Add Amlogic DDR PMU
Date: Thu, 14 Jul 2022 17:13:06 +0800 [thread overview]
Message-ID: <79ff63fc-dbd7-bc31-ebe7-7d15d121add1@amlogic.com> (raw)
In-Reply-To: <94ab770b-8a8a-4299-a54e-2ff77afb9e04@arm.com>
On 7/12/2022 8:54 PM, Robin Murphy wrote:
> [ EXTERNAL EMAIL ]
>
> On 2022-07-12 07:36, Jiucheng Xu wrote:
>> Add binding documentation for the Amlogic G12 series DDR
>> performance monitor unit.
>>
>> Signed-off-by: Jiucheng Xu <jiucheng.xu@amlogic.com>
>> ---
>> .../devicetree/bindings/perf/aml-ddr-pmu.yaml | 51 +++++++++++++++++++
>> MAINTAINERS | 1 +
>> 2 files changed, 52 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml
>> b/Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml
>> new file mode 100644
>> index 000000000000..c586b4ab4009
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml
>> @@ -0,0 +1,51 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/perf/aml-ddr-pmu.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Amlogic G12 DDR performance monitor
>> +
>> +maintainers:
>> + - Jiucheng Xu <jiucheng.xu@amlogic.com>
>> +
>> +properties:
>> + compatible:
>> + oneOf:
>> + - enum:
>> + - aml,g12-ddr-pmu
>> + - items:
>> + - enum:
>> + - aml,g12-ddr-pmu
>> + - const: aml,g12-ddr-pmu
>
> Judging by what the driver actually implements, this should probably be:
>
> compatible:
> items:
> - enum:
> - amlogic,g12a-ddr-pmu
> - amlogic,g12b-ddr-pmu
> - amlogic,sm1-ddr-pmu
> - const: amlogic,g12-ddr-pmu
>
> There doesn't seem much point in allowing only the common compatible
> without a SoC-specific identifier. Note also that "aml," is not the
> documented vendor prefix.
Okay, I finally know what you mean.
>
>> +
>> + reg:
>> + maxItems: 2
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> +required:
>> + - compatible
>> + - model
>
> Remove this, and use the compatible strings properly as above.
Okay. I will make the change.
>
>> + - dmc_nr
>> + - chann_nr
>
> I suspect those could probably be inferred from the correct compatible
> string, but if not (i.e. within one SoC you have multiple PMUs
> supporting the same events but with different numbers of usable
> channels), then document what exactly they mean.
>
Yes, as you mentioned, these could be inferred from the compatible
string. I will make the change.
>> + - reg
>> + - interrupts
>> + - interrupt-names
>
> As mentioned in the driver review, if you really want to use a named
> interrupt (which should usually be unnecessary when there's only one),
> it has to be a defined name. DT is not a mechanism for overriding what
> Linux shows in /proc/interrupts.
>
> Thanks,
> Robin.
>
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + ddr_pmu: ddr_pmu {
>> + compatible = "amlogic,g12-ddr-pmu";
>> + model = "g12a";
>> + dmc_nr = <1>;
>> + chann_nr = <4>;
>> + reg = <0x0 0xff638000 0x0 0x100
>> + 0x0 0xff638c00 0x0 0x100>;
>> + interrupts = <GIC_SPI 52 IRQ_TYPE_EDGE_RISING>;
>> + interrupt-names = "ddr_pmu";
>> + };
>> + };
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index fd2a56a339b4..ac0a1df4622d 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1055,6 +1055,7 @@ M: Jiucheng Xu <jiucheng.xu@amlogic.com>
>> S: Supported
>> W: http://www.amlogic.com
>> F: Documentation/admin-guide/perf/aml-ddr-pmu.rst
>> +F: Documentation/devicetree/bindings/perf/aml-ddr-pmu.yaml
>> F: drivers/perf/amlogic/
>> F: include/soc/amlogic/
>
next prev parent reply other threads:[~2022-07-14 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 6:36 [PATCH 1/4] perf/amlogic: Add support for Amlogic meson G12 SoC DDR PMU driver Jiucheng Xu
2022-07-12 6:36 ` [PATCH 2/4] docs/perf: Add documentation for the Amlogic G12 DDR PMU Jiucheng Xu
2022-07-12 6:36 ` [PATCH 3/4] arm64:dts:meson: Add DDR PMU node Jiucheng Xu
2022-07-12 6:36 ` [PATCH 4/4] dt-binding:perf: Add Amlogic DDR PMU Jiucheng Xu
2022-07-12 7:15 ` Krzysztof Kozlowski
2022-07-14 3:22 ` Jiucheng Xu
2022-07-12 12:54 ` Robin Murphy
2022-07-14 9:13 ` Jiucheng Xu [this message]
2022-07-12 14:26 ` Rob Herring
2022-07-12 12:36 ` [PATCH 1/4] perf/amlogic: Add support for Amlogic meson G12 SoC DDR PMU driver Robin Murphy
2022-07-14 8:17 ` Jiucheng Xu
2022-07-15 16:38 ` Robin Murphy
2022-07-17 20:58 ` Chris Healy
2022-07-18 8:06 ` Neil Armstrong
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=79ff63fc-dbd7-bc31-ebe7-7d15d121add1@amlogic.com \
--to=jiucheng.xu@amlogic.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--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).