All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jon-hunter@ti.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Russell King <linux@arm.linux.org.uk>,
	Grant Likely <grant.likely@secretlab.ca>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	device-tree <devicetree-discuss@lists.ozlabs.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	Paul Walmsley <paul@pwsan.com>,
	Pratik Patel <pratikp@codeaurora.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Ming Lei <ming.lei@canonical.com>,
	Mark Rutland <Mark.Rutland@arm.com>
Subject: Re: [RFC 2/5] ARM: dts: Add Cross Trigger Interface binding
Date: Thu, 13 Dec 2012 13:21:30 -0600	[thread overview]
Message-ID: <50CA2ABA.1050600@ti.com> (raw)
In-Reply-To: <20121213174139.GA12946@mudshark.cambridge.arm.com>


On 12/13/2012 11:41 AM, Will Deacon wrote:
> On Wed, Dec 12, 2012 at 09:43:05PM +0000, Jon Hunter wrote:
>> Adds a device-tree binding for the ARM Cross Trigger Interface (CTI).
>> The ARM Cross Trigger Interface provides a way to route events between
>> processor modules. For example, on OMAP4430 we use the CTI module to
>> route PMU events to the GIC interrupt module.
>>
>> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
>> ---
>>  Documentation/devicetree/bindings/arm/cti.txt |   32 +++++++++++++++++++++++++
>>  1 file changed, 32 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/arm/cti.txt
>>
>> diff --git a/Documentation/devicetree/bindings/arm/cti.txt b/Documentation/devicetree/bindings/arm/cti.txt
>> new file mode 100644
>> index 0000000..4a0e2d3
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/cti.txt
>> @@ -0,0 +1,32 @@
>> +* ARM Cross Trigger Interface (CTI)
>> +
>> +The ARM Cross Trigger Interface provides a way to route events between
>> +processor modules. For example, debug events from one processor can be
>> +broadcasted to other processors. The events that can be routed between
>> +processors are specific to the device.
>> +
>> +Required properties:
>> +
>> +- compatible:			Should be "arm,primecell".
>> +- interrupts:			Interrupt associated with CTI module.
>> +- reg:				Contains timer register address range (base
>> +				address and length).
>> +- arm,cti-name:			A unique name for the CTI module, that will be
>> +				used when requesting the CTI module instance.
>> +
>> +
>> +Optional properties:
>> +
>> +- arm-primecell-periphid:	Primecell peripheral ID associated with CTI
>> +				module.
> 
> For multi-cluster systems, I wouldn't be surprised to see multiple CTI
> instances, each with different CPU affinities. Can we include an affinity
> property following Mark's proposed binding?
> 
>   http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137290.html

Yes I can take a look. Would something like that be applicable to pmu as
well or is that unlikely to have different affinities? I am just
wondering if there is something that we should implement in general for
the various primecell components.

Cheers
Jon

WARNING: multiple messages have this Message-ID (diff)
From: jon-hunter@ti.com (Jon Hunter)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 2/5] ARM: dts: Add Cross Trigger Interface binding
Date: Thu, 13 Dec 2012 13:21:30 -0600	[thread overview]
Message-ID: <50CA2ABA.1050600@ti.com> (raw)
In-Reply-To: <20121213174139.GA12946@mudshark.cambridge.arm.com>


On 12/13/2012 11:41 AM, Will Deacon wrote:
> On Wed, Dec 12, 2012 at 09:43:05PM +0000, Jon Hunter wrote:
>> Adds a device-tree binding for the ARM Cross Trigger Interface (CTI).
>> The ARM Cross Trigger Interface provides a way to route events between
>> processor modules. For example, on OMAP4430 we use the CTI module to
>> route PMU events to the GIC interrupt module.
>>
>> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
>> ---
>>  Documentation/devicetree/bindings/arm/cti.txt |   32 +++++++++++++++++++++++++
>>  1 file changed, 32 insertions(+)
>>  create mode 100644 Documentation/devicetree/bindings/arm/cti.txt
>>
>> diff --git a/Documentation/devicetree/bindings/arm/cti.txt b/Documentation/devicetree/bindings/arm/cti.txt
>> new file mode 100644
>> index 0000000..4a0e2d3
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/cti.txt
>> @@ -0,0 +1,32 @@
>> +* ARM Cross Trigger Interface (CTI)
>> +
>> +The ARM Cross Trigger Interface provides a way to route events between
>> +processor modules. For example, debug events from one processor can be
>> +broadcasted to other processors. The events that can be routed between
>> +processors are specific to the device.
>> +
>> +Required properties:
>> +
>> +- compatible:			Should be "arm,primecell".
>> +- interrupts:			Interrupt associated with CTI module.
>> +- reg:				Contains timer register address range (base
>> +				address and length).
>> +- arm,cti-name:			A unique name for the CTI module, that will be
>> +				used when requesting the CTI module instance.
>> +
>> +
>> +Optional properties:
>> +
>> +- arm-primecell-periphid:	Primecell peripheral ID associated with CTI
>> +				module.
> 
> For multi-cluster systems, I wouldn't be surprised to see multiple CTI
> instances, each with different CPU affinities. Can we include an affinity
> property following Mark's proposed binding?
> 
>   http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137290.html

Yes I can take a look. Would something like that be applicable to pmu as
well or is that unlikely to have different affinities? I am just
wondering if there is something that we should implement in general for
the various primecell components.

Cheers
Jon

  reply	other threads:[~2012-12-13 19:21 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 21:43 [RFC 0/5] ARM: Add Cross Trigger Interface driver Jon Hunter
2012-12-12 21:43 ` Jon Hunter
     [not found] ` <1355348588-22318-1-git-send-email-jon-hunter-l0cyMroinI0@public.gmane.org>
2012-12-12 21:43   ` [RFC 1/5] ARM: CORESIGHT: Add generic lock/unlock helpers Jon Hunter
2012-12-12 21:43     ` Jon Hunter
     [not found]     ` <1355348588-22318-2-git-send-email-jon-hunter-l0cyMroinI0@public.gmane.org>
2012-12-13 14:58       ` Will Deacon
2012-12-13 14:58         ` Will Deacon
     [not found]         ` <20121213145803.GL26540-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2012-12-13 19:18           ` Jon Hunter
2012-12-13 19:18             ` Jon Hunter
2012-12-13 19:36             ` Jean Pihet
2012-12-13 19:36               ` Jean Pihet
2012-12-12 21:43   ` [RFC 4/5] ARM: dts: OMAP4: Add CTI nodes Jon Hunter
2012-12-12 21:43     ` Jon Hunter
2012-12-12 21:43 ` [RFC 2/5] ARM: dts: Add Cross Trigger Interface binding Jon Hunter
2012-12-12 21:43   ` Jon Hunter
2012-12-12 22:12   ` Rob Herring
2012-12-12 22:12     ` Rob Herring
2012-12-12 23:23     ` Jon Hunter
2012-12-12 23:23       ` Jon Hunter
2012-12-14 19:53       ` Rob Herring
2012-12-14 19:53         ` Rob Herring
2012-12-13 17:41   ` Will Deacon
2012-12-13 17:41     ` Will Deacon
2012-12-13 19:21     ` Jon Hunter [this message]
2012-12-13 19:21       ` Jon Hunter
2012-12-17 16:20       ` Mark Rutland
2012-12-17 16:20         ` Mark Rutland
2012-12-17 16:30         ` Jon Hunter
2012-12-17 16:30           ` Jon Hunter
2012-12-12 21:43 ` [RFC 3/5] ARM: CTI: Convert CTI helpers to AMBA bus driver Jon Hunter
2012-12-12 21:43   ` Jon Hunter
2012-12-13 15:08   ` Will Deacon
2012-12-13 15:08     ` Will Deacon
     [not found]     ` <20121213150826.GM26540-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2012-12-13 19:35       ` Jon Hunter
2012-12-13 19:35         ` Jon Hunter
2012-12-21 22:27   ` Pratik Patel
2012-12-21 22:27     ` Pratik Patel
2012-12-21 22:35     ` Pratik Patel
2012-12-21 22:35       ` Pratik Patel
2013-01-02 19:13       ` Jon Hunter
2013-01-02 19:13         ` Jon Hunter
2013-01-02 19:23     ` Jon Hunter
2013-01-02 19:23       ` Jon Hunter
2013-01-03 18:47       ` Pratik Patel
2013-01-03 18:47         ` Pratik Patel
2012-12-12 21:43 ` [RFC 5/5] ARM: OMAP4: Add AMBA APB Clock Jon Hunter
2012-12-12 21:43   ` Jon Hunter

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=50CA2ABA.1050600@ti.com \
    --to=jon-hunter@ti.com \
    --cc=Mark.Rutland@arm.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ming.lei@canonical.com \
    --cc=paul@pwsan.com \
    --cc=pratikp@codeaurora.org \
    --cc=rob.herring@calxeda.com \
    --cc=will.deacon@arm.com \
    /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.