All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ian Rogers" <irogers@google.com>
Cc: linux-perf-users@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v17 1/3] dt-bindings: perf: Add Broadcom Raspberry Pi AXI PMU definition
Date: Wed, 04 Nov 2026 03:09:01 +0000	[thread overview]
Message-ID: <sashiko-outbox-196587@kernel.org> (raw)
In-Reply-To: <20261104030300.1140180-2-irogers@google.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: perf: invalid plain scalar colon in brcm,bcm2835-axiperf.yaml
--

commit 585240cf0e14c8ec2eefa09a1ecc59a1d82cc72f
Author: Ian Rogers <irogers@google.com>

dt-bindings: perf: Add Broadcom Raspberry Pi AXI PMU definition

This commit adds the Device Tree binding schema for the Broadcom Raspberry Pi
AXI PMU block on BCM2835, BCM2711, and BCM2712 SoCs.

> diff --git a/Documentation/devicetree/bindings/perf/brcm,bcm2835-axiperf.yaml b/Documentation/devicetree/bindings/perf/brcm,bcm2835-axiperf.yaml
> new file mode 100644
> index 0000000000000..2f1f4f286ab57
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/perf/brcm,bcm2835-axiperf.yaml
> @@ -0,0 +1,44 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/perf/brcm,bcm2835-axiperf.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom BCM2835/2711/2712 AXI Performance Monitor
> +
> +maintainers:
> +  - Ian Rogers <irogers@google.com>
> +
> +description:
> +  The Broadcom BCM2835 series (including BCM2711 and BCM2712) features hardware
> +  performance monitors on the AXI bus for evaluating memory bandwidth and
> +  system traffic. Two monitor register blocks are present: the primary monitor
> +  evaluates the System fabric, while the secondary monitor evaluates the
> +  VideoCore VPU fabric. This block is distinct from the BCM5301X AXI Trace
> +  Module.

[Severity: Low]
In Documentation/devicetree/bindings/perf/brcm,bcm2835-axiperf.yaml, the
top-level description property is written as an unquoted multi-line plain
scalar and contains a colon followed by a space in "present: the primary
monitor".

In YAML 1.2, a colon followed by whitespace inside a plain scalar is parsed
as a mapping value indicator, which causes make dt_binding_check and yamllint
to fail with a syntax error ("mapping values are not allowed here").

Should description use a block scalar indicator (such as description: |) or
avoid the colon followed by a space?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261104030300.1140180-1-irogers@google.com?part=1

  reply	other threads:[~2026-11-04  3:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  3:02 [PATCH v17 0/3] perf: Add Raspberry Pi AXI PMU driver Ian Rogers
2026-11-04  3:02 ` [PATCH v17 1/3] dt-bindings: perf: Add Broadcom Raspberry Pi AXI PMU definition Ian Rogers
2026-11-04  3:09   ` sashiko-bot [this message]
2026-11-04 15:07   ` Rob Herring (Arm)
2026-11-04  3:02 ` [PATCH v17 2/3] perf: Add Raspberry Pi BCM2835 AXI PMU driver Ian Rogers
2026-11-04  3:31   ` sashiko-bot
2026-11-04  3:03 ` [PATCH v17 3/3] perf: Add Raspberry Pi 5 (BCM2712) AXI PMU support Ian Rogers
2026-11-04  3:08   ` 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=sashiko-outbox-196587@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=irogers@google.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.