Linux Perf Users
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: will@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org, linux-perf-users@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: perf: Add Arm Bus Monitor Unit
Date: Mon, 13 Jul 2026 13:59:22 +0100	[thread overview]
Message-ID: <3f3e6dec-9e37-4731-8de1-bd9f3cee9b80@arm.com> (raw)
In-Reply-To: <20260713-noble-jade-wapiti-20ba9d@quoll>

On 13/07/2026 8:26 am, Krzysztof Kozlowski wrote:
> On Thu, Jul 09, 2026 at 08:22:07PM +0100, Robin Murphy wrote:
>> +required:
>> +  - compatible
>> +  - reg
>> +  - label
>> +
>> +additionalProperties: false
> 
> You need an example DTS, unless this is a subdevice and part of other device as
> subschema.

I still fundamentally disagree with the necessity of "validating" my 
ability to understand my own trivial 3-property binding that I wrote, 
but whatever... v2 can have this which I've made up out of thin air 
since I have no real-world reference to hand:

examples:
   - |
     pmu@12340000 {
         compatible = "arm,bus-monitor-unit";
         reg = <0x12340000 0x40000>;
         label = "ddr_ch_1_2";
     };

Thanks,
Robin.

  reply	other threads:[~2026-07-13 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 19:22 [PATCH 0/2] perf: Support Arm Bus Monitor Unit Robin Murphy
2026-07-09 19:22 ` [PATCH 1/2] dt-bindings: perf: Add " Robin Murphy
2026-07-09 19:26   ` sashiko-bot
2026-07-13  7:26   ` Krzysztof Kozlowski
2026-07-13 12:59     ` Robin Murphy [this message]
2026-07-09 19:22 ` [PATCH 2/2] perf: Add Arm Bus Monitor Unit driver Robin Murphy
2026-07-09 19:36   ` 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=3f3e6dec-9e37-4731-8de1-bd9f3cee9b80@arm.com \
    --to=robin.murphy@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@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