From: Rob Herring <robh@kernel.org>
To: "JiaLong.Yang" <jialong.yang@shingroup.cn>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
shenghui.qu@shingroup.cn, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: perf: Support uncore NI-700 PMU
Date: Wed, 6 Mar 2024 15:46:13 -0600 [thread overview]
Message-ID: <20240306214613.GA716904-robh@kernel.org> (raw)
In-Reply-To: <7f2576291e51043b33296a2cd9e21263d16ca077.1709694173.git.jialong.yang@shingroup.cn>
On Wed, Mar 06, 2024 at 02:16:02PM +0800, JiaLong.Yang wrote:
> Add file corresponding to hx_arm_ni.c introducing ARM NI-700 PMU
> driver for HX.
>
> Signed-off-by: JiaLong.Yang <jialong.yang@shingroup.cn>
> ---
> v1 --> v2:
> 1. Submit dt-bindings file Seperately.
> 2. Do some check:
> ~ #: make dt_binding_check DT_SCHEMA_FILES=perf
> LINT Documentation/devicetree/bindings
> CHKDT Documentation/devicetree/bindings/processed-schema.json
> SCHEMA Documentation/devicetree/bindings/processed-schema.json
> DTEX Documentation/devicetree/bindings/perf/hx,c2000-arm-ni.example.dts
> DTC_CHK Documentation/devicetree/bindings/perf/hx,c2000-arm-ni.example.dtb
>
> v2 --> v3:
> 1. Change vendor from hx to hexin.
> 2. Submit driver and dt-bindings files together.
> 3. Delete pccs-id property. Use alias-id to do this.
> 4. There are at least one interrupt line for the hardware and driver
> for handling counter overflow.
> 5. Use 4 spaces for example indentation in yaml file.
>
> .../bindings/perf/hexin,c2000-arm-ni.yaml | 51 +++++++++++++++++++
> MAINTAINERS | 6 +++
> 2 files changed, 57 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/perf/hexin,c2000-arm-ni.yaml
>
> diff --git a/Documentation/devicetree/bindings/perf/hexin,c2000-arm-ni.yaml b/Documentation/devicetree/bindings/perf/hexin,c2000-arm-ni.yaml
> new file mode 100644
> index 000000000000..b2641ee84d60
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/perf/hexin,c2000-arm-ni.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/hexin,c2000-arm-ni.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: HX-C2000 NI (Network-on-chip Interconnect) Performance Monitors
> +
> +maintainers:
> + - Jialong Yang <jialong.yang@shingroup.cn>
> +
> +properties:
> + compatible:
> + enum:
> + - hexin,c2000-arm-ni
As this seems to be Arm IP, I'd expect arm,ni-700-pmu or something.
Are there Hexin modifications to it?
> +
> + reg:
> + items:
> + - description: Physical address of the base (PERIPHBASE) and
> + size of the whole NI configuration address space.
Just 'maxItems: 1' if there is only 1 entry.
> +
> + interrupts:
> + minItems: 1
> + items:
> + - description: Overflow interrupt for clock domain 0
> + - description: Overflow interrupt for clock domain 1
> + - description: Overflow interrupt for clock domain 2
> + - description: Generally, one interrupt line for one PMU. But this also
> + support one interrupt line for a NI if merged.
I don't understand this last entry.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + aliases {
> + ni-pmu0 = &nipmu0;
Drop. Please don't make up your own alias names.
> + };
> +
> + nipmu0: pmu@23ff0000 {
> + compatible = "hexin,c2000-arm-ni";
> + reg = <0x2b420000 0x10000>;
> + interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4f298c4187fb..4b664cec98a7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -18890,6 +18890,12 @@ L: linux-riscv@lists.infradead.org
> S: Maintained
> F: arch/riscv/boot/dts/thead/
>
> +HX ARM-NI-700 PMU DRIVERS
> +M: Jialong Yang <jialong.yang@shingroup.cn>
> +S: Supported
> +F: Documentation/devicetree/bindings/perf/hexin,c2000-arm-ni.yaml
> +F: drivers/perf/hx_arm_ni.c
> +
> RNBD BLOCK DRIVERS
> M: Md. Haris Iqbal <haris.iqbal@ionos.com>
> M: Jack Wang <jinpu.wang@ionos.com>
> --
> 2.25.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-06 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1709694173.git.jialong.yang@shingroup.cn>
[not found] ` <f674ec19ce824dfc13258396931256c3d33cd207.1709694173.git.jialong.yang@shingroup.cn>
2024-03-06 6:16 ` [PATCH v3 1/2] dt-bindings: perf: Support uncore NI-700 PMU JiaLong.Yang
2024-03-06 21:46 ` Rob Herring [this message]
2024-03-07 6:33 ` Yang Jialong 杨佳龙
2024-03-06 6:16 ` [PATCH v3 2/2] perf/hx_arm_ni: " JiaLong.Yang
2024-03-21 9:28 ` Yang Jialong 杨佳龙
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=20240306214613.GA716904-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jialong.yang@shingroup.cn \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shenghui.qu@shingroup.cn \
--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).