From: hs@denx.de (Heiko Schocher)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/7] ARM: davinci, intc: Add OF support for TI interrupt controller
Date: Wed, 29 Feb 2012 07:42:51 +0100 [thread overview]
Message-ID: <4F4DC8EB.7010201@denx.de> (raw)
In-Reply-To: <4F44DE24.30606@mvista.com>
Hello Sergei,
Sergei Shtylyov wrote:
> On 22-02-2012 10:50, Heiko Schocher wrote:
>
>> Add a function to initialize the davinci interrupt controller (INTC)
>> using a device tree node.
>
> cp_intc is not DaVinci interrupt controller, it's only used in
> OMAP-L1x SoCs. cp_intc stands for Common Platform Interrupt Controller.
Ah, Ok! Thanks for the explanation.
> I don't see where you are initializiing the DaVinci interrupt controller
> itself. You should understand that there are two disctinct types of
> interrupt controllers used in the SoCs supported by arch/arm/mach-davinci/.
board code:
MACHINE_START(ENBW_CMC, "EnBW CMC")
[...]
.init_irq = davinci_init_irq,
and in arch/arm/mach-davinci/cp_intc.c
for the of case:
void __init davinci_init_irq(void)
{
of_irq_init(irq_match);
}
in drivers/of/irq.c:
/**
* of_irq_init - Scan and init matching interrupt controllers in DT
* @matches: 0 terminated array of nodes to match and init function to call
*
* This function scans the device tree for matching interrupt controller nodes,
* and calls their initialization functions in order with parents first.
*/
void __init of_irq_init(const struct of_device_id *matches)
Ok, the name of davinci_init_irq() is missleading ...
Should I name it "cp_intc_of_init" ?
>> Signed-off-by: Heiko Schocher<hs@denx.de>
>> Cc: davinci-linux-open-source at linux.davincidsp.com
>> Cc: linux-arm-kernel at lists.infradead.org
>> Cc: devicetree-discuss at lists.ozlabs.org
>> Cc: Grant Likely<grant.likely@secretlab.ca>
>> Cc: Sekhar Nori<nsekhar@ti.com>
>> Cc: Wolfgang Denk<wd@denx.de>
>
> [...]
>
>> diff --git a/Documentation/devicetree/bindings/arm/davinci/intc.txt
>> b/Documentation/devicetree/bindings/arm/davinci/intc.txt
>> new file mode 100644
>> index 0000000..dac2f69
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/davinci/intc.txt
>> @@ -0,0 +1,26 @@
>> +* TI Davinci Interrupt Controller
>> +
>> +davinci are using a TI interrupt controller that can support several
>> +configurable number of interrupts.
>> +
>> +Main node required properties:
>> +
>> +- compatible : should be:
>> + "ti,davinci-intc"
>
> The right "compatible" prop would be "ti,cp_intc" in this case.
Ok, change this.
Thanks for the review!
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Schocher <hs@denx.de>
To: Sergei Shtylyov <sshtylyov@mvista.com>
Cc: devicetree-discuss@lists.ozlabs.org,
Grant Likely <grant.likely@secretlab.ca>,
davinci-linux-open-source@linux.davincidsp.com,
Wolfgang Denk <wd@denx.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/7] ARM: davinci, intc: Add OF support for TI interrupt controller
Date: Wed, 29 Feb 2012 07:42:51 +0100 [thread overview]
Message-ID: <4F4DC8EB.7010201@denx.de> (raw)
In-Reply-To: <4F44DE24.30606@mvista.com>
Hello Sergei,
Sergei Shtylyov wrote:
> On 22-02-2012 10:50, Heiko Schocher wrote:
>
>> Add a function to initialize the davinci interrupt controller (INTC)
>> using a device tree node.
>
> cp_intc is not DaVinci interrupt controller, it's only used in
> OMAP-L1x SoCs. cp_intc stands for Common Platform Interrupt Controller.
Ah, Ok! Thanks for the explanation.
> I don't see where you are initializiing the DaVinci interrupt controller
> itself. You should understand that there are two disctinct types of
> interrupt controllers used in the SoCs supported by arch/arm/mach-davinci/.
board code:
MACHINE_START(ENBW_CMC, "EnBW CMC")
[...]
.init_irq = davinci_init_irq,
and in arch/arm/mach-davinci/cp_intc.c
for the of case:
void __init davinci_init_irq(void)
{
of_irq_init(irq_match);
}
in drivers/of/irq.c:
/**
* of_irq_init - Scan and init matching interrupt controllers in DT
* @matches: 0 terminated array of nodes to match and init function to call
*
* This function scans the device tree for matching interrupt controller nodes,
* and calls their initialization functions in order with parents first.
*/
void __init of_irq_init(const struct of_device_id *matches)
Ok, the name of davinci_init_irq() is missleading ...
Should I name it "cp_intc_of_init" ?
>> Signed-off-by: Heiko Schocher<hs@denx.de>
>> Cc: davinci-linux-open-source@linux.davincidsp.com
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: devicetree-discuss@lists.ozlabs.org
>> Cc: Grant Likely<grant.likely@secretlab.ca>
>> Cc: Sekhar Nori<nsekhar@ti.com>
>> Cc: Wolfgang Denk<wd@denx.de>
>
> [...]
>
>> diff --git a/Documentation/devicetree/bindings/arm/davinci/intc.txt
>> b/Documentation/devicetree/bindings/arm/davinci/intc.txt
>> new file mode 100644
>> index 0000000..dac2f69
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/davinci/intc.txt
>> @@ -0,0 +1,26 @@
>> +* TI Davinci Interrupt Controller
>> +
>> +davinci are using a TI interrupt controller that can support several
>> +configurable number of interrupts.
>> +
>> +Main node required properties:
>> +
>> +- compatible : should be:
>> + "ti,davinci-intc"
>
> The right "compatible" prop would be "ti,cp_intc" in this case.
Ok, change this.
Thanks for the review!
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2012-02-29 6:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 6:50 [PATCH v2 0/7] ARM: davinci: add support for the am1808 based enbw_cmc board Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` [PATCH v2 1/7] ARM: davinci, intc: Add OF support for TI interrupt controller Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 12:23 ` Sergei Shtylyov
2012-02-22 12:23 ` Sergei Shtylyov
2012-02-29 6:42 ` Heiko Schocher [this message]
2012-02-29 6:42 ` Heiko Schocher
2012-02-29 10:22 ` Sergei Shtylyov
2012-02-29 10:22 ` Sergei Shtylyov
2012-02-22 6:50 ` [PATCH v2 2/7] ARM: davinci: configure davinci aemif chipselects through OF Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` [PATCH v2 3/7] ARM: davinci: mux: add OF support Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` [PATCH v2 4/7] ARM: davinci: net: davinci_emac: " Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` [PATCH v2 6/7] ARM: mtd: nand: davinci: add OF support for davinci nand controller Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
[not found] ` <1329893410-24413-1-git-send-email-hs-ynQEQJNshbs@public.gmane.org>
2012-02-22 6:50 ` [PATCH v2 5/7] ARM: davinci: i2c: add OF support Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` [PATCH v2 7/7] ARM: davinci: add support for the am1808 based enbw_cmc board Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
2012-02-22 6:50 ` Heiko Schocher
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=4F4DC8EB.7010201@denx.de \
--to=hs@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.