On Monday 09 May 2016 02:42 PM, Jose Abreu wrote:
> Can you apply this to arc-next? Main driver was already merged into clk-next.
> We
> still have to check how to deal with the parent clock frequency that will
> change
> in the next firmware release.
Done ! although note that this might *not*
On Friday 13 May 2016 03:55 PM, Marc Zyngier wrote:
> On 13/05/16 10:51, Arnd Bergmann wrote:
>> On Friday 13 May 2016 14:05:41 Vineet Gupta wrote:
>>> On Friday 13 May 2016 01:54 PM, Marc Zyngier wrote:
On 12/05/16 22:03, Arnd Bergmann wrote:
>>> ...
>
> config EZNPS_GIC
>
On 13/05/16 10:51, Arnd Bergmann wrote:
> On Friday 13 May 2016 14:05:41 Vineet Gupta wrote:
>> On Friday 13 May 2016 01:54 PM, Marc Zyngier wrote:
>>> On 12/05/16 22:03, Arnd Bergmann wrote:
>> ...
config EZNPS_GIC
bool "NPS400 Global Interrupt Manager (GIM)"
+
On Friday 13 May 2016 14:05:41 Vineet Gupta wrote:
> On Friday 13 May 2016 01:54 PM, Marc Zyngier wrote:
> > On 12/05/16 22:03, Arnd Bergmann wrote:
> ...
> >>
> >> config EZNPS_GIC
> >> bool "NPS400 Global Interrupt Manager (GIM)"
> >> +depends on ARC || (COMPILE_TEST && !64BIT)
> >>
On 13/05/16 09:35, Vineet Gupta wrote:
> On Friday 13 May 2016 01:54 PM, Marc Zyngier wrote:
>> On 12/05/16 22:03, Arnd Bergmann wrote:
> ...
>>>
>>> config EZNPS_GIC
>>> bool "NPS400 Global Interrupt Manager (GIM)"
>>> + depends on ARC || (COMPILE_TEST && !64BIT)
>>> select
On Friday 13 May 2016 04:34 AM, Vince Weaver wrote:
> On Thu, 12 May 2016, Peter Zijlstra wrote:
>
>> Ah.. which might be a hint that nobody is actually explicitly testing
>> for this and we might just get away with changing the ABI.
>>
>> Vince, what say you; shall we try and get away with it?
On Friday 13 May 2016 01:54 PM, Marc Zyngier wrote:
> On 12/05/16 22:03, Arnd Bergmann wrote:
...
>>
>> config EZNPS_GIC
>> bool "NPS400 Global Interrupt Manager (GIM)"
>> +depends on ARC || (COMPILE_TEST && !64BIT)
>> select IRQ_DOMAIN
>> help
>>Support the EZchip
