public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Geetha sowjanya" <gakula@marvell.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: perf: marvell: Add CN20K DDR PMU binding
Date: Mon, 13 Apr 2026 17:12:06 +0000	[thread overview]
Message-ID: <20260413171206.F380AC2BCAF@smtp.kernel.org> (raw)
In-Reply-To: <20260413165621.10921-2-gakula@marvell.com>

Sashiko AI review found 2 potential issue(s):
- [Low] DT binding example unit address and generic node name mismatch.
- [Low] Unnecessary duplication of binding files instead of updating the existing schema.
--

commit e2d439a05897c67e7bc90170f7cf6e218505769a
Author: Geetha sowjanya <gakula@marvell.com>

dt-bindings: perf: marvell: Add CN20K DDR PMU binding

This commit adds a new device tree binding for the DDR Performance Monitoring
Unit found in Marvell CN20K SoCs. The hardware provides counters to monitor
DDR traffic and is accessed via a dedicated MMIO region.

> diff --git a/Documentation/devicetree/bindings/perf/marvell,cn20k-ddr-pmu.yaml b/Documentation/devicetree/bindings/perf/marvell,cn20k-ddr-pmu.yaml
> new file mode 100644
> index 0000000000000..cc6aa760de49e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/perf/marvell,cn20k-ddr-pmu.yaml

The commit message notes that the CN20K DDR PMU is functionally equivalent
to the CN10K DDR PMU. Does it make sense to consolidate this by adding the new
compatible string to the existing marvell-cn10k-ddr.yaml schema instead of
introducing a new duplicate file?

Splitting schemas is typically recommended only when conditionals become
too unwieldy.

[ ... ]

> +examples:
> +  - |
> +    bus {
> +        #address-cells = <2>;
> +        #size-cells = <2>;
> +
> +        ddr-pmu@c200000000 {
> +            compatible = "marvell,cn20k-ddr-pmu";
> +            reg = <0xc200 0x00000000 0x0 0x100000>;
> +        };
> +    };

Is there a unit address mismatch here? The 64-bit base address formed by the
reg property is 0xc20000000000, but the node name uses @c200000000, missing two
trailing zeros. This can trigger a unit_address_vs_reg regression during
dt_binding_check.

Also, does this example need to use a generic class-based node name like pmu
instead of ddr-pmu to match devicetree recommendations?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260413165621.10921-1-gakula@marvell.com?part=1

  reply	other threads:[~2026-04-13 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 16:56 [PATCH v5 0/2] perf: marvell: Add CN20K DDR PMU support Geetha sowjanya
2026-04-13 16:56 ` [PATCH v5 1/2] dt-bindings: perf: marvell: Add CN20K DDR PMU binding Geetha sowjanya
2026-04-13 17:12   ` sashiko-bot [this message]
2026-04-14  6:37     ` Krzysztof Kozlowski
2026-04-13 16:56 ` [PATCH v5 2/2] perf: marvell: Add CN20K DDR PMU support Geetha sowjanya
2026-04-13 17:50   ` sashiko-bot

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=20260413171206.F380AC2BCAF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=gakula@marvell.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko@lists.linux.dev \
    /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