On Thu, Nov 28, 2013 at 12:17 AM, Grant Likely wrote:
> On Wed, 27 Nov 2013 19:06:35 +1000, Peter Crosthwaite
> wrote:
>> On Mon, Nov 25, 2013 at 7:32 AM, Grant Likely
>> wrote:
>> > On Sun, 24 Nov 2013 17:04:52 +1000, Peter Crosthwaite
>> > wrote:
>> >> On Wed, Nov 13, 2013 at 4:14 PM, Gran
On Wed, 27 Nov 2013 19:06:35 +1000, Peter Crosthwaite
wrote:
> On Mon, Nov 25, 2013 at 7:32 AM, Grant Likely wrote:
> > On Sun, 24 Nov 2013 17:04:52 +1000, Peter Crosthwaite
> > wrote:
> >> On Wed, Nov 13, 2013 at 4:14 PM, Grant Likely
> >> wrote:
> >> > On Wed, 13 Nov 2013 09:17:01 +1000, P
On Mon, Nov 25, 2013 at 7:32 AM, Grant Likely wrote:
> On Sun, 24 Nov 2013 17:04:52 +1000, Peter Crosthwaite
> wrote:
>> On Wed, Nov 13, 2013 at 4:14 PM, Grant Likely
>> wrote:
>> > On Wed, 13 Nov 2013 09:17:01 +1000, Peter Crosthwaite
>> > wrote:
>> >> It's going to get a little verbose onc
On Sun, 24 Nov 2013 17:04:52 +1000, Peter Crosthwaite
wrote:
> On Wed, Nov 13, 2013 at 4:14 PM, Grant Likely wrote:
> > On Wed, 13 Nov 2013 09:17:01 +1000, Peter Crosthwaite
> > wrote:
> >> It's going to get a little verbose once you start making multiple
> >> connections as you need one mux p
On Wed, Nov 13, 2013 at 4:14 PM, Grant Likely wrote:
> On Wed, 13 Nov 2013 09:17:01 +1000, Peter Crosthwaite
> wrote:
>> On Tue, Nov 12, 2013 at 6:50 PM, Grant Likely
>> wrote:
>> > On Tue, 12 Nov 2013 17:49:37 +1000, Peter Crosthwaite
>> > wrote:
>> >> Hi Grant,
>> >>
>> >> On Tue, Nov 12,
On Wed, 13 Nov 2013 09:17:01 +1000, Peter Crosthwaite
wrote:
> On Tue, Nov 12, 2013 at 6:50 PM, Grant Likely wrote:
> > On Tue, 12 Nov 2013 17:49:37 +1000, Peter Crosthwaite
> > wrote:
> >> Hi Grant,
> >>
> >> On Tue, Nov 12, 2013 at 4:54 PM, Grant Likely
> >> wrote:
> >> > On Tue, 12 Nov 20
On Tue, Nov 12, 2013 at 6:50 PM, Grant Likely wrote:
> On Tue, 12 Nov 2013 17:49:37 +1000, Peter Crosthwaite
> wrote:
>> Hi Grant,
>>
>> On Tue, Nov 12, 2013 at 4:54 PM, Grant Likely
>> wrote:
>> > On Tue, 12 Nov 2013 08:58:15 +1000, Peter Crosthwaite
>> > wrote:
>> >> Hi Grant,
>> >>
>> >>
On Tue, 12 Nov 2013 17:49:37 +1000, Peter Crosthwaite
wrote:
> Hi Grant,
>
> On Tue, Nov 12, 2013 at 4:54 PM, Grant Likely wrote:
> > On Tue, 12 Nov 2013 08:58:15 +1000, Peter Crosthwaite
> > wrote:
> >> Hi Grant,
> >>
> >> On Wed, Oct 16, 2013 at 6:39 AM, Grant Likely
> >> wrote:
> >> > Th
Hi Grant,
On Tue, Nov 12, 2013 at 4:54 PM, Grant Likely wrote:
> On Tue, 12 Nov 2013 08:58:15 +1000, Peter Crosthwaite
> wrote:
>> Hi Grant,
>>
>> On Wed, Oct 16, 2013 at 6:39 AM, Grant Likely
>> wrote:
>> > The standard interrupts property in device tree can only handle
>> > interrupts comin
On Tue, 12 Nov 2013 08:58:15 +1000, Peter Crosthwaite
wrote:
> Hi Grant,
>
> On Wed, Oct 16, 2013 at 6:39 AM, Grant Likely wrote:
> > The standard interrupts property in device tree can only handle
> > interrupts coming from a single interrupt parent. If a device is wired
> > to multiple interr
Hi Grant,
On Wed, Oct 16, 2013 at 6:39 AM, Grant Likely wrote:
> The standard interrupts property in device tree can only handle
> interrupts coming from a single interrupt parent. If a device is wired
> to multiple interrupt controllers, then it needs to be attached to a
> node with an interrupt
On Mon, 28 Oct 2013 01:54:38 -0500, Kumar Gala wrote:
>
> On Oct 15, 2013, at 3:39 PM, Grant Likely wrote:
>
> > The standard interrupts property in device tree can only handle
> > interrupts coming from a single interrupt parent. If a device is wired
> > to multiple interrupt controllers, then
On Mon, 2013-10-28 at 15:47 -0600, Stephen Warren wrote:
> "interrupts-ex" would be shorter, although I guess slightly harder to
> guess its purpose, unless you're familiar with "ex" in symbol names.
>
> ...
> >> +A device node may contain either "interrupts" or "interrupts-extended",
> >> but n
On Mon, Oct 28, 2013 at 09:47:44PM +, Stephen Warren wrote:
> On 10/27/2013 07:46 AM, Grant Likely wrote:
> > On Tue, 15 Oct 2013 21:39:23 +0100, Grant Likely
> > wrote:
> >> The standard interrupts property in device tree can only handle
> >> interrupts coming from a single interrupt parent.
On 10/27/2013 07:46 AM, Grant Likely wrote:
> On Tue, 15 Oct 2013 21:39:23 +0100, Grant Likely
> wrote:
>> The standard interrupts property in device tree can only handle
>> interrupts coming from a single interrupt parent. If a device is wired
>> to multiple interrupt controllers, then it needs
On Oct 27, 2013, at 10:16 PM, Mark Rutland wrote:
> On Sun, Oct 27, 2013 at 08:24:08PM +, Rob Herring wrote:
>> On Sun, Oct 27, 2013 at 8:46 AM, Grant Likely
>> wrote:
>>> On Tue, 15 Oct 2013 21:39:23 +0100, Grant Likely
>>> wrote:
The standard interrupts property in device tree can
On Oct 15, 2013, at 3:39 PM, Grant Likely wrote:
> The standard interrupts property in device tree can only handle
> interrupts coming from a single interrupt parent. If a device is wired
> to multiple interrupt controllers, then it needs to be attached to a
> node with an interrupt-map property
On Sun, Oct 27, 2013 at 08:24:08PM +, Rob Herring wrote:
> On Sun, Oct 27, 2013 at 8:46 AM, Grant Likely wrote:
> > On Tue, 15 Oct 2013 21:39:23 +0100, Grant Likely
> > wrote:
> >> The standard interrupts property in device tree can only handle
> >> interrupts coming from a single interrupt
On Sun, Oct 27, 2013 at 8:46 AM, Grant Likely wrote:
> On Tue, 15 Oct 2013 21:39:23 +0100, Grant Likely
> wrote:
>> The standard interrupts property in device tree can only handle
>> interrupts coming from a single interrupt parent. If a device is wired
>> to multiple interrupt controllers, then
On Tue, 15 Oct 2013 21:39:23 +0100, Grant Likely
wrote:
> The standard interrupts property in device tree can only handle
> interrupts coming from a single interrupt parent. If a device is wired
> to multiple interrupt controllers, then it needs to be attached to a
> node with an interrupt-map pr
* Grant Likely [131015 13:43]:
> The standard interrupts property in device tree can only handle
> interrupts coming from a single interrupt parent. If a device is wired
> to multiple interrupt controllers, then it needs to be attached to a
> node with an interrupt-map property to demux the interr
The standard interrupts property in device tree can only handle
interrupts coming from a single interrupt parent. If a device is wired
to multiple interrupt controllers, then it needs to be attached to a
node with an interrupt-map property to demux the interrupt specifiers
which is confusing. It wo
22 matches
Mail list logo
