All of lore.kernel.org
 help / color / mirror / Atom feed
From: punit.agrawal@arm.com (Punit Agrawal)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drivers: CCI: add ARM CCI PMU support
Date: Thu, 15 Aug 2013 11:09:04 +0100	[thread overview]
Message-ID: <520CA8C0.4080008@arm.com> (raw)
In-Reply-To: <ABE5FFA6-8709-4E8F-A726-27C1154157F0@codeaurora.org>

On 14/08/13 22:16, Kumar Gala wrote:
>
> On Aug 14, 2013, at 4:13 PM, Stephen Warren wrote:
>
>> On 08/14/2013 03:09 PM, Kumar Gala wrote:
>>>
>>> On Aug 14, 2013, at 4:06 PM, Stephen Warren wrote:
>>>
>>>> On 07/23/2013 03:19 AM, Punit Agrawal wrote:
>>>>> The CCI PMU can profile bus transactions at the master and slave
>>>>> interfaces of the CCI. The PMU can be used to observe an aggregated view
>>>>> of the bus traffic between the various components connected to the CCI.
>>>>>
>>>>> Extend the existing CCI driver to support the PMU by registering a perf
>>>>> backend for it.
>>>>>
>>>>> Document the device tree binding to describe the CCI PMU.
>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/arm/cci.txt b/Documentation/devicetree/bindings/arm/cci.txt
>>>>
>>>>> +	- CCI PMU node
>>>>> +
>>>>> +		Node name must be "pmu".
>>>>
>>>> I don't think the binding should require the node to have a particular
>>>> name; node names shouldn't be interpret/used/relied-upon by drivers.
>>>
>>> While I agree with that, we should be aiming for some convention and consistency with node names.
>>
>> Sure. Should there be a Documentation/devictree/bindings/node-names that
>> lists common node names for people to use? Either way though, I still
>> think this is an aspect of authoring the *.dts file, not an aspect of
>> the DT binding? After all, what if there were more than one CCI so they
>> needed to be named pmu at 0, pmu at 1, etc.?
>
> Agreed, I was thinking a bindings/node-names would be a good idea.
>
> I'm guessing 99% of people copy either from the example in the binding of an existing .dts file.  So while I agree the binding shouldn't require a node name be a specific thing as part of the spec, we as reviewers should try to ensure consistency in examples or .dts files.
>

Based on the comments so far, I will change the bindings documentation 
submitted with this patch to remove the requirement for a particular 
node name for CCI PMU.

As it is, this is not required by the driver but was only done for 
consistency.

Cheers,
Punit

> - k
>

  reply	other threads:[~2013-08-15 10:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11  3:00 [PATCH] drivers: CCI: add ARM CCI PMU support Punit Agrawal
2013-08-05 11:37 ` Punit Agrawal
2013-08-07  1:45   ` Will Deacon
2013-08-12 13:59     ` Will Deacon
2013-08-12 16:08       ` Will Deacon
2013-08-12 16:58         ` Punit Agrawal
2013-08-14 21:03 ` Kumar Gala
2013-08-14 22:38   ` Rob Herring
2013-08-15 10:01     ` Punit Agrawal
2013-08-15  9:10   ` Punit Agrawal
2013-08-15 16:25     ` Kumar Gala
2013-08-16 10:31       ` Punit Agrawal
2013-08-16 10:53         ` Kumar Gala
2013-08-15 19:00     ` Kumar Gala
2013-08-16 10:56       ` Punit Agrawal
2013-08-16 11:31         ` Kumar Gala
2013-08-16 12:41           ` Punit Agrawal
2013-08-14 21:06 ` Stephen Warren
2013-08-14 21:09   ` Kumar Gala
2013-08-14 21:13     ` Stephen Warren
2013-08-14 21:16       ` Kumar Gala
2013-08-15 10:09         ` Punit Agrawal [this message]
2013-08-16 17:19 ` [PATCH v2] " Punit Agrawal
2013-08-16 18:31   ` Stephen Warren
2013-08-19 11:14     ` Punit Agrawal
2013-08-19 16:15       ` Stephen Warren
2013-08-16 18:47   ` Kumar Gala
2013-08-19 11:21     ` Punit Agrawal
2013-08-20 15:07   ` Will Deacon

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=520CA8C0.4080008@arm.com \
    --to=punit.agrawal@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.