Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1183352
| From | Stephen Warren <swarren@wwwdotorg.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 3/4] irqchip: Add documentation for the bcm2836 interrupt controller. |
| Date | 2015-07-14 07:10 +0200 |
| Message-ID | <pM0DE-6tJ-7@gated-at.bofh.it> (permalink) |
| References | <pJIrv-2mE-3@gated-at.bofh.it> <pJIrv-2mE-15@gated-at.bofh.it> <pKW93-7Xs-13@gated-at.bofh.it> <pKW93-7Xs-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 07/11/2015 12:01 AM, Eric Anholt wrote:
> Stephen Warren <swarren@wwwdotorg.org> writes:
>
>> On 07/07/2015 03:13 PM, Eric Anholt wrote:
>>> This is a new per-cpu root interrupt controller on the
>>> Raspberry Pi 2, which will chain to the bcm2835 interrupt
>>> controller for peripheral interrupts.
>>
>>> diff --git
>>> a/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2836-l1-intc.txt
>>> b/Documentation/devicetree/bindings/interrupt-controller/brcm,bcm2836-l1-intc.txt
>>
>>>
>>>
+local_intc: local_intc {
>>
>>> + interrupt-parent = <&local_intc>;
>>
>> I think that property shouldn't be there?
>
> If you don't have it there, the core finds the interrupt-parent in
> the parent node, and waits for that one before initializing (which
> is in turn waiting for us). Note that for original 2835, you're
> finding the parent node as well.
Ah yes. It does indeed look like it's typical that the root IRQ
controller points at itself.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH 3/4] irqchip: Add documentation for the bcm2836 interrupt controller. Stephen Warren <swarren@wwwdotorg.org> - 2015-07-14 07:10 +0200
csiph-web