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: Fri, 16 Aug 2013 11:56:22 +0100	[thread overview]
Message-ID: <520E0556.5080702@arm.com> (raw)
In-Reply-To: <9E753731-852D-4F04-931B-112B589D9FFB@codeaurora.org>

Hi Kumar,

On 15/08/13 20:00, Kumar Gala wrote:
>
> On Aug 15, 2013, at 4:10 AM, Punit Agrawal wrote:
>
>>> What is the list of interrupts related to, should there be an associated interrupts-names
>>>
>>
>> For the CCI PMU, each interrupt signal corresponds to the overflow of a performance counter.
>>
>> Here again, I was trying to be robust in the face of differing hardware configurations - specially the scenario where multiple interrupt lines from the CCI PMU are tied together to generate a single interrupt to the CPU.
>
> Even in the case of multiple interrupt lines tied together, why wouldn't you still specify each interrupt specifier and they all just be the same and thus the interrupt appears to be shared ?
>

I am not quite sure what you are asking here. Are you suggesting that 
even if the interrupts are muxed, they should be specified multiple times?

Below is an update I've added to the documentation to better describe 
the interrupts. Does this help?

@@ -104,8 +103,19 @@ specific to ARM.
                 - interrupts:
                         Usage: required
                         Value type: <prop-encoded-array>
-                   Definition: comma-separated list of unique PMU
-                               interrupts
+                 Definition: comma-separated list of counter overflow
+                             interrupts.
+
+                             The CCI PMU has an interrupt signal for each
+                             counters. Typically, the number of
+                             interrupts will be equal to the number of
+                             counters.
+
+                             On some platforms, the individual interrupt
+                             signals may be combined in some fashion
+                             before being routed to the interrupt
+                             controller resulting in less number of
+                             interrupts than counters.

  * CCI interconnect bus masters


> - k
>

  reply	other threads:[~2013-08-16 10:56 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 [this message]
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
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=520E0556.5080702@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.