devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	"rvaswani-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
	<rvaswani-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"davidb-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org"
	<davidb-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Subject: Re: [DT] API to determine if interrupt is PPI or SPI ?
Date: Fri, 27 Jul 2012 14:09:47 +0100	[thread overview]
Message-ID: <20120727130947.GN559@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <50128AA0.8040409-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Fri, Jul 27, 2012 at 01:33:36PM +0100, Rob Herring wrote:
> On 07/26/2012 02:18 PM, rvaswani-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org wrote:
> > Hello,
> > 
> > We can specify the interrupt information in the device tree using the arm
> > gic convention.
> > Is there an API to read directly the 1st cell and determine if an
> > interrupt is a PPI or a SPI ? This information is directly relevant to the
> > driver because it needs to call request_irq or request_percpu_irq based on
> > this data.
> > 
> > How should this be done ideally ?
> 
> Seems a bit strange to me that you would have a h/w block that can be
> connected either way...

The CPU PMU can be wired as either SPI or PPI. The latter makes more sense to
me but usually (although not exclusively) it's wired using the former.

Will

  parent reply	other threads:[~2012-07-27 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 19:18 [DT] API to determine if interrupt is PPI or SPI ? rvaswani
     [not found] ` <53a41d02c4c4c24bdab47667183891bf.squirrel-mMfbam+mt9083fI46fginR2eb7JE58TQ@public.gmane.org>
2012-07-27 12:33   ` Rob Herring
     [not found]     ` <50128AA0.8040409-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-07-27 13:09       ` Will Deacon [this message]
2012-07-27 20:00         ` rvaswani

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=20120727130947.GN559@mudshark.cambridge.arm.com \
    --to=will.deacon-5wv7dgnigg8@public.gmane.org \
    --cc=davidb-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=rvaswani-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).