On 12/04/16 09:50, Jon Hunter wrote:
>
> On 11/04/16 16:39, Marc Zyngier wrote:
>> On 11/04/16 16:31, Jon Hunter wrote:
>>> On 09/04/16 11:58, Marc Zyngier wrote:
>
> [snip]
>
I think we need to phase things. Let's start with warning people for a
few kernel releases. Actively maintaine
On 11/04/16 16:39, Marc Zyngier wrote:
> On 11/04/16 16:31, Jon Hunter wrote:
>> On 09/04/16 11:58, Marc Zyngier wrote:
[snip]
>>> I think we need to phase things. Let's start with warning people for a
>>> few kernel releases. Actively maintained platforms will quickly address
>>> the issue (fix
On 11/04/16 16:31, Jon Hunter wrote:
> Hi Mark,
>
> On 09/04/16 11:58, Marc Zyngier wrote:
>> On Thu, 17 Mar 2016 15:04:01 +
>> Jon Hunter wrote:
>>
>>>
>>> On 17/03/16 14:51, Thomas Gleixner wrote:
On Thu, 17 Mar 2016, Jon Hunter wrote:
> Setting the interrupt type for private
Hi Mark,
On 09/04/16 11:58, Marc Zyngier wrote:
> On Thu, 17 Mar 2016 15:04:01 +
> Jon Hunter wrote:
>
>>
>> On 17/03/16 14:51, Thomas Gleixner wrote:
>>> On Thu, 17 Mar 2016, Jon Hunter wrote:
>>>
Setting the interrupt type for private peripheral interrupts (PPIs) may
not be suppo
On Thu, 17 Mar 2016 15:04:01 +
Jon Hunter wrote:
>
> On 17/03/16 14:51, Thomas Gleixner wrote:
> > On Thu, 17 Mar 2016, Jon Hunter wrote:
> >
> >> Setting the interrupt type for private peripheral interrupts (PPIs) may
> >> not be supported by a given GIC because it is IMPLEMENTATION DEFINE
Setting the interrupt type for private peripheral interrupts (PPIs) may
not be supported by a given GIC because it is IMPLEMENTATION DEFINED
whether this is allowed. There is no way to know if setting the type is
supported for a given GIC and so the value written is read back to
verify it matches t
On 17/03/16 14:51, Thomas Gleixner wrote:
> On Thu, 17 Mar 2016, Jon Hunter wrote:
>
>> Setting the interrupt type for private peripheral interrupts (PPIs) may
>> not be supported by a given GIC because it is IMPLEMENTATION DEFINED
>> whether this is allowed. There is no way to know if setting th
Hi Jon,
On Fri, Mar 18, 2016 at 10:54 AM, Jon Hunter wrote:
> On 18/03/16 09:20, Geert Uytterhoeven wrote:
>> On Thu, Mar 17, 2016 at 5:20 PM, Jon Hunter wrote:
>>> On 17/03/16 15:18, Jason Cooper wrote:
On Thu, Mar 17, 2016 at 03:04:01PM +, Jon Hunter wrote:
> On 17/03/16 14:51, Th
On Thu, Mar 17, 2016 at 5:20 PM, Jon Hunter wrote:
> On 17/03/16 15:18, Jason Cooper wrote:
>> On Thu, Mar 17, 2016 at 03:04:01PM +, Jon Hunter wrote:
>>> On 17/03/16 14:51, Thomas Gleixner wrote:
On Thu, 17 Mar 2016, Jon Hunter wrote:
> Setting the interrupt type for private peripher
On 17/03/16 15:18, Jason Cooper wrote:
> On Thu, Mar 17, 2016 at 03:04:01PM +, Jon Hunter wrote:
>>
>> On 17/03/16 14:51, Thomas Gleixner wrote:
>>> On Thu, 17 Mar 2016, Jon Hunter wrote:
>>>
Setting the interrupt type for private peripheral interrupts (PPIs) may
not be supported by
On 18/03/16 09:20, Geert Uytterhoeven wrote:
> On Thu, Mar 17, 2016 at 5:20 PM, Jon Hunter wrote:
>> On 17/03/16 15:18, Jason Cooper wrote:
>>> On Thu, Mar 17, 2016 at 03:04:01PM +, Jon Hunter wrote:
On 17/03/16 14:51, Thomas Gleixner wrote:
> On Thu, 17 Mar 2016, Jon Hunter wrote:
>
On Thu, 17 Mar 2016, Jon Hunter wrote:
> Setting the interrupt type for private peripheral interrupts (PPIs) may
> not be supported by a given GIC because it is IMPLEMENTATION DEFINED
> whether this is allowed. There is no way to know if setting the type is
> supported for a given GIC and so the v
On Thu, Mar 17, 2016 at 03:04:01PM +, Jon Hunter wrote:
>
> On 17/03/16 14:51, Thomas Gleixner wrote:
> > On Thu, 17 Mar 2016, Jon Hunter wrote:
> >
> >> Setting the interrupt type for private peripheral interrupts (PPIs) may
> >> not be supported by a given GIC because it is IMPLEMENTATION D
13 matches
Mail list logo
