devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: devicetree-discuss@lists.ozlabs.org
Cc: Mark Salter <msalter@redhat.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/24] C6X: devicetree
Date: Tue, 13 Sep 2011 08:43:56 +0200	[thread overview]
Message-ID: <6360771.ouEC5EKNMR@wuerfel> (raw)
In-Reply-To: <1315869636.11280.26.camel@deneb.redhat.com>

On Monday 12 September 2011 19:20:35 Mark Salter wrote:
> On Mon, 2011-09-12 at 14:11 -0600, Grant Likely wrote:
> > On Wed, Aug 31, 2011 at 05:26:41PM -0400, Mark Salter wrote:
> > > +           interrupt-controller;
> > > +           #interrupt-cells = <1>;
> > > +           compatible = "ti,c64x+core-pic";
> > 
> > The interrupt controller isn't addressable?  Is it integrated into
> > the CPU?
> 
> Yes, that core controller is controlled through registers accessed
> with special-purpose instructions, not MMIO. Other controllers, like
> megamodule and some as-yet unimplemented use MMIO.

Are these instructions specific to the interrupt controller or
do they access a register space that can contain arbitrary
devices?

If there is a separate address space for special devices, it might
be good to describe that in the device tree, like we do for PCI
I/O space.

	Arnd

  reply	other threads:[~2011-09-13  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1314826019-22330-1-git-send-email-msalter@redhat.com>
     [not found] ` <1314826019-22330-1-git-send-email-msalter-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-08-31 21:26   ` [PATCH 06/24] C6X: devicetree Mark Salter
2011-09-12 20:11     ` Grant Likely
     [not found]       ` <20110912201102.GF23345-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-09-12 23:20         ` Mark Salter
2011-09-13  6:43           ` Arnd Bergmann [this message]
2011-09-13 12:39             ` Mark Salter
     [not found]               ` <1315917546.11280.38.camel-PDpCo7skNiwAicBL8TP8PQ@public.gmane.org>
2011-09-13 15:33                 ` Arnd Bergmann
2011-09-13 17:54                   ` Grant Likely
     [not found]                     ` <CACxGe6tVafwVN6vdU7sCxL5JM7+as0bp_AaHaGAyE9+eTgR5Tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-09-13 20:11                       ` Arnd Bergmann
2011-09-13 22:26                       ` Mark Salter
     [not found] <1314043785-2880-1-git-send-email-msalter@redhat.com>
2011-08-22 20:09 ` Mark Salter

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=6360771.ouEC5EKNMR@wuerfel \
    --to=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msalter@redhat.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 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).