linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: zynq: Support GIC OF initialization
Date: Mon, 18 Jun 2012 14:10:52 +0200	[thread overview]
Message-ID: <4FDF1ACC.2040208@monstr.eu> (raw)
In-Reply-To: <4FDF19CF.8010303@gmail.com>

On 06/18/2012 02:06 PM, Rob Herring wrote:
> On 06/18/2012 06:11 AM, Michal Simek wrote:
>> Zynq is OF driven platfrom which requires OF initialization.
>>
>> Signed-off-by: Michal Simek<monstr@monstr.eu>
>> ---
>>   arch/arm/mach-zynq/common.c |    7 ++++++-
>>   1 files changed, 6 insertions(+), 1 deletions(-)
>>
>> diff --git a/arch/arm/mach-zynq/common.c b/arch/arm/mach-zynq/common.c
>> index 17d68d6..7941544 100644
>> --- a/arch/arm/mach-zynq/common.c
>> +++ b/arch/arm/mach-zynq/common.c
>> @@ -56,12 +56,17 @@ static void __init xilinx_init_machine(void)
>>   	of_platform_bus_probe(NULL, zynq_of_bus_ids, NULL);
>>   }
>>
>> +static const struct of_device_id zynq_dt_irq_match[] __initconst = {
>> +	{ .compatible = "arm,cortex-a9-gic", .data = gic_of_init },
>> +	{ }
>> +};
>> +
>>   /**
>>    * xilinx_irq_init() - Interrupt controller initialization for the GIC.
>>    */
>>   static void __init xilinx_irq_init(void)
>>   {
>> -	gic_init(0, 29, SCU_GIC_DIST_BASE, SCU_GIC_CPU_BASE);
>
> And delete the corresponding defines?

Agree, Will create v2.

BTW: Who is responsible for zynq? I think John Linn and who is maintainer I should ask for pulling.

Thanks,
Michal




-- 
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian

  reply	other threads:[~2012-06-18 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 11:11 [PATCH] arm: zynq: Support GIC OF initialization Michal Simek
2012-06-18 12:06 ` Rob Herring
2012-06-18 12:10   ` Michal Simek [this message]
2012-06-18 15:45     ` John Linn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FDF1ACC.2040208@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).