On 29.01.2015 16:29, Catalin Marinas wrote:
On Tue, Jan 27, 2015 at 04:12:08PM +, Grant Likely wrote:
On Fri, Jan 16, 2015 at 2:37 PM, Marc Zyngier wrote:
@@ -78,6 +79,10 @@ void __init set_handle_irq(void (*handle_irq)(struct pt_regs
*))
void __init init_IRQ(void)
{
On Tue, Jan 27, 2015 at 04:12:08PM +, Grant Likely wrote:
> On Fri, Jan 16, 2015 at 2:37 PM, Marc Zyngier wrote:
> @@ -78,6 +79,10 @@ void __init set_handle_irq(void (*handle_irq)(struct
> pt_regs *))
> void __init init_IRQ(void)
> {
> irqchip_init();
> +
On Tue, Jan 27, 2015 at 04:12:08PM +, Grant Likely wrote:
On Fri, Jan 16, 2015 at 2:37 PM, Marc Zyngier marc.zyng...@arm.com wrote:
@@ -78,6 +79,10 @@ void __init set_handle_irq(void (*handle_irq)(struct
pt_regs *))
void __init init_IRQ(void)
{
irqchip_init();
+
+ if
On 29.01.2015 16:29, Catalin Marinas wrote:
On Tue, Jan 27, 2015 at 04:12:08PM +, Grant Likely wrote:
On Fri, Jan 16, 2015 at 2:37 PM, Marc Zyngier marc.zyng...@arm.com wrote:
@@ -78,6 +79,10 @@ void __init set_handle_irq(void (*handle_irq)(struct pt_regs
*))
void __init init_IRQ(void)
On Fri, Jan 16, 2015 at 2:37 PM, Marc Zyngier wrote:
@@ -78,6 +79,10 @@ void __init set_handle_irq(void (*handle_irq)(struct
pt_regs *))
void __init init_IRQ(void)
{
irqchip_init();
+
+ if (!handle_arch_irq)
+ acpi_gic_init();
+
>>>
On Fri, Jan 16, 2015 at 2:37 PM, Marc Zyngier marc.zyng...@arm.com wrote:
@@ -78,6 +79,10 @@ void __init set_handle_irq(void (*handle_irq)(struct
pt_regs *))
void __init init_IRQ(void)
{
irqchip_init();
+
+ if (!handle_arch_irq)
+ acpi_gic_init();
+
Why isn't this
On 2015年01月22日 22:46, Marc Zyngier wrote:
Hi Hanjun,
On 22/01/15 12:46, Hanjun Guo wrote:
Hi Marc,
We (Tomasz, Suravee and me) are working on supporting stacked domain on
ACPI, and rework GIC ACPI related patch, before we going further, we
need your guidance to see if we are going the right
On 2015年01月22日 22:46, Marc Zyngier wrote:
Hi Hanjun,
On 22/01/15 12:46, Hanjun Guo wrote:
Hi Marc,
We (Tomasz, Suravee and me) are working on supporting stacked domain on
ACPI, and rework GIC ACPI related patch, before we going further, we
need your guidance to see if we are going the right
Hi Hanjun,
On 22/01/15 12:46, Hanjun Guo wrote:
> Hi Marc,
>
> We (Tomasz, Suravee and me) are working on supporting stacked domain on
> ACPI, and rework GIC ACPI related patch, before we going further, we
> need your guidance to see if we are going the right direction.
>
>- You said that
Hi Marc,
We (Tomasz, Suravee and me) are working on supporting stacked domain on
ACPI, and rework GIC ACPI related patch, before we going further, we
need your guidance to see if we are going the right direction.
- You said that we spread GIC related code every where, so how
about put all
Hi Marc,
We (Tomasz, Suravee and me) are working on supporting stacked domain on
ACPI, and rework GIC ACPI related patch, before we going further, we
need your guidance to see if we are going the right direction.
- You said that we spread GIC related code every where, so how
about put all
Hi Hanjun,
On 22/01/15 12:46, Hanjun Guo wrote:
Hi Marc,
We (Tomasz, Suravee and me) are working on supporting stacked domain on
ACPI, and rework GIC ACPI related patch, before we going further, we
need your guidance to see if we are going the right direction.
- You said that we
On 01/20/2015 05:40 AM, Tomasz Nowicki wrote:
> Hi Marc,
>
> On 16.01.2015 12:15, Marc Zyngier wrote:
>> On 14/01/15 15:05, Hanjun Guo wrote:
>>> From: Tomasz Nowicki
>>>
>>> ACPI kernel uses MADT table for proper GIC initialization. It needs to
>>> parse GIC related subtables, collect CPU
Hi Marc,
On 16.01.2015 12:15, Marc Zyngier wrote:
On 14/01/15 15:05, Hanjun Guo wrote:
From: Tomasz Nowicki
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization
Hi Marc,
On 16.01.2015 12:15, Marc Zyngier wrote:
On 14/01/15 15:05, Hanjun Guo wrote:
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call
On 01/20/2015 05:40 AM, Tomasz Nowicki wrote:
Hi Marc,
On 16.01.2015 12:15, Marc Zyngier wrote:
On 14/01/15 15:05, Hanjun Guo wrote:
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect
On 16/01/15 13:54, Grant Likely wrote:
> On Fri, Jan 16, 2015 at 11:15 AM, Marc Zyngier wrote:
>> On 14/01/15 15:05, Hanjun Guo wrote:
>>> From: Tomasz Nowicki
>>>
>>> ACPI kernel uses MADT table for proper GIC initialization. It needs to
>>> parse GIC related subtables, collect CPU interface
On Fri, Jan 16, 2015 at 11:15 AM, Marc Zyngier wrote:
> On 14/01/15 15:05, Hanjun Guo wrote:
>> From: Tomasz Nowicki
>>
>> ACPI kernel uses MADT table for proper GIC initialization. It needs to
>> parse GIC related subtables, collect CPU interface and distributor
>> addresses and call driver
On 14/01/15 15:05, Hanjun Guo wrote:
> From: Tomasz Nowicki
>
> ACPI kernel uses MADT table for proper GIC initialization. It needs to
> parse GIC related subtables, collect CPU interface and distributor
> addresses and call driver initialization function (which is hardware
> abstraction
On 14/01/15 15:05, Hanjun Guo wrote:
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
On Fri, Jan 16, 2015 at 11:15 AM, Marc Zyngier marc.zyng...@arm.com wrote:
On 14/01/15 15:05, Hanjun Guo wrote:
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and
On 16/01/15 13:54, Grant Likely wrote:
On Fri, Jan 16, 2015 at 11:15 AM, Marc Zyngier marc.zyng...@arm.com wrote:
On 14/01/15 15:05, Hanjun Guo wrote:
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related
On 01/14/2015 09:05 AM, Hanjun Guo wrote:
From: Tomasz Nowicki
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
abstraction agnostic).
On 01/14/2015 09:05 AM, Hanjun Guo wrote:
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
From: Tomasz Nowicki
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
abstraction agnostic). In a similar way, FDT initialize GICv1/2.
From: Tomasz Nowicki tomasz.nowi...@linaro.org
ACPI kernel uses MADT table for proper GIC initialization. It needs to
parse GIC related subtables, collect CPU interface and distributor
addresses and call driver initialization function (which is hardware
abstraction agnostic). In a similar way,
26 matches
Mail list logo
