On 06/08/15 11:05, Julien Grall wrote:
>> But Ian suggested to export gicv3_host_irq_end instead of calling
>> gicv3_eoi_irq()
>
> And Ian said "Exposing those two gicv3 functions is a bit unfortunate,
> but I think it will do for now.".
>
> Which means he was opposed to the previous solution.
*
On 06/08/15 09:15, Vijay Kilari wrote:
> On Tue, Aug 4, 2015 at 7:15 PM, Julien Grall wrote:
>> Hi Vijay,
>>
>> On 27/07/15 12:11, vijay.kil...@gmail.com wrote:
>>> +
>>> +static const hw_irq_controller its_host_lpi_type = {
>>> +.typename = "gic-its",
>>> +.startup = its_irq_star
On Tue, Aug 4, 2015 at 7:15 PM, Julien Grall wrote:
> Hi Vijay,
>
> On 27/07/15 12:11, vijay.kil...@gmail.com wrote:
>> +
>> +static const hw_irq_controller its_host_lpi_type = {
>> +.typename = "gic-its",
>> +.startup = its_irq_startup,
>> +.shutdown = its_irq_shutdown,
>
Hi Vijay,
On 27/07/15 12:11, vijay.kil...@gmail.com wrote:
> From: Vijaya Kumar K
>
> Implements hw_irq_controller api's required
> to handle LPI's
You need to explain in your commit message why you switched to callback.
Relevant maintainers should be CCed too (see scripts/get_maintainers.pl).
From: Vijaya Kumar K
Implements hw_irq_controller api's required
to handle LPI's
Signed-off-by: Vijaya Kumar K
---
v5: - Fixed review comments
- Exposed gicv3_[host|guest]_irq_end and hook to its
v4: - Implement separate hw_irq_controller for LPIs
- Drop setting LPI affinity
- virq
