[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <yw1x37tpmueo.fsf@unicorn.mansr.com>
Date: Fri, 22 Jan 2016 16:49:19 +0000
From: Måns Rullgård <mans@...sr.com>
To: Marc Gonzalez <marc_gonzalez@...madesigns.com>
Cc: Marc Zyngier <marc.zyngier@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
LKML <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Sebastian Frias <sf84@...oste.net>
Subject: Re: [RFC PATCH v3] irqchip: Add support for Tango interrupt controller
Marc Gonzalez <marc_gonzalez@...madesigns.com> writes:
> On 22/01/2016 17:39, Måns Rullgård wrote:
>
>> Marc Gonzalez <marc_gonzalez@...madesigns.com> writes:
>>
>>> On 22/01/2016 17:35, Måns Rullgård wrote:
>>>
>>>> Marc Gonzalez <marc_gonzalez@...madesigns.com> writes:
>>>>
>>>>> With your latest patch, can I drop the ranges property?
>>>>
>>>> Why would you want to do that?
>>>
>>> <confused> I thought that was the whole point of the v4 improvement?
>>
>> The point was to make it work right *if* someone were to do that even
>> though having it there better reflects what the hardware actually looks
>> like.
>
> That's the part I'm struggling to understand. Who other than you or me
> would write a device tree from scratch for this interrupt controller?
I wouldn't discount the possibility.
--
Måns Rullgård
Powered by blists - more mailing lists