From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] picoxcell: support for Picochip picoxcell devices
Date: Sat, 20 Aug 2011 07:52:51 +0100 [thread overview]
Message-ID: <20110820065251.GB18892@gallagher> (raw)
In-Reply-To: <4E4F54CC.8000506@secretlab.ca>
Hi Grant,
On Fri, Aug 19, 2011 at 11:31:40PM -0700, Grant Likely wrote:
> On 11-08-09 03:10 AM, Jamie Iles wrote:
[...]
> >+VIC required properties:
> >+ - compatible = "arm,pl192-vic-pair".
> >+ - interrupt-controller.
> >+ - reg : The register bank for the devices. Picoxcell has two VIC's and the
> >+ IRQ outputs are wire-OR'd together so we effectively have a combined
> >+ controller that handles 64 IRQ's. The first reg tuple is the register
> >+ bank of the VIC that generates IRQ's 0->31 and the second tuple handles
> >+ IRQ's 32->63.
>
> If they are two separate devices, then it probably should still be
> represented as two separate device tree nodes. Linux can take care
> of assigning a range of linux irq numbers to each VIC.
The reason I did this is because of the entry macro get_irqnr_and_base
macro decoding. If I used irq_domain_generate_simple() rather than
irq_domain_add_simple() then I guess the ordering of the VIC's in the DT
wont matter. I'll give this a test when I have access to hardware again
and respin.
Many thanks for the review!
Jamie
WARNING: multiple messages have this Message-ID (diff)
From: Jamie Iles <jamie@jamieiles.com>
To: Grant Likely <glikely@secretlab.ca>
Cc: Jamie Iles <jamie@jamieiles.com>,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] picoxcell: support for Picochip picoxcell devices
Date: Sat, 20 Aug 2011 07:52:51 +0100 [thread overview]
Message-ID: <20110820065251.GB18892@gallagher> (raw)
In-Reply-To: <4E4F54CC.8000506@secretlab.ca>
Hi Grant,
On Fri, Aug 19, 2011 at 11:31:40PM -0700, Grant Likely wrote:
> On 11-08-09 03:10 AM, Jamie Iles wrote:
[...]
> >+VIC required properties:
> >+ - compatible = "arm,pl192-vic-pair".
> >+ - interrupt-controller.
> >+ - reg : The register bank for the devices. Picoxcell has two VIC's and the
> >+ IRQ outputs are wire-OR'd together so we effectively have a combined
> >+ controller that handles 64 IRQ's. The first reg tuple is the register
> >+ bank of the VIC that generates IRQ's 0->31 and the second tuple handles
> >+ IRQ's 32->63.
>
> If they are two separate devices, then it probably should still be
> represented as two separate device tree nodes. Linux can take care
> of assigning a range of linux irq numbers to each VIC.
The reason I did this is because of the entry macro get_irqnr_and_base
macro decoding. If I used irq_domain_generate_simple() rather than
irq_domain_add_simple() then I guess the ordering of the VIC's in the DT
wont matter. I'll give this a test when I have access to hardware again
and respin.
Many thanks for the review!
Jamie
next prev parent reply other threads:[~2011-08-20 6:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 10:10 [PATCH 0/3] Device Tree support for Picochip picoXcell Jamie Iles
2011-08-09 10:10 ` Jamie Iles
2011-08-09 10:10 ` [PATCH 1/3] picoxcell: support for Picochip picoxcell devices Jamie Iles
2011-08-09 10:10 ` Jamie Iles
2011-08-20 6:31 ` Grant Likely
2011-08-20 6:31 ` Grant Likely
2011-08-20 6:52 ` Jamie Iles [this message]
2011-08-20 6:52 ` Jamie Iles
2011-08-20 14:37 ` Grant Likely
2011-08-20 14:37 ` Grant Likely
2011-08-09 10:11 ` [PATCH 2/3] picoxcell: add the DTS for pc3x2 and pc3x3 devices Jamie Iles
2011-08-09 10:11 ` Jamie Iles
2011-08-09 10:11 ` [PATCH 3/3] picoxcell: add the DTS for the PC7302 board Jamie Iles
2011-08-09 10:11 ` Jamie Iles
2011-08-18 16:02 ` [PATCH 0/3] Device Tree support for Picochip picoXcell Jamie Iles
2011-08-18 16:02 ` Jamie Iles
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=20110820065251.GB18892@gallagher \
--to=jamie@jamieiles.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.