From: Ben Dooks <ben.dooks@sifive.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sudip Mukherjee <sudip.mukherjee@sifive.com>,
Jude Onyenegecha <jude.onyenegecha@sifive.com>
Subject: Re: [PATCH] of/irq: parse interrupts-extended during irq init heirarchy calculation
Date: Mon, 11 Jul 2022 08:16:57 +0100 [thread overview]
Message-ID: <b9c97f5e-ca61-ee91-0cb7-a426a921474c@sifive.com> (raw)
In-Reply-To: <CAL_Jsq+TZpAK-X02ANoYBMfUKkwPh3Z-gjGjim6WwFwsMa7zSA@mail.gmail.com>
On 08/07/2022 22:49, Rob Herring wrote:
> On Fri, Jul 8, 2022 at 10:52 AM Ben Dooks <ben.dooks@sifive.com> wrote:
>>
>> When the irq controler code works out the heirarchy for initialialisation
>> it only looks at interrupt-parent properties, but controllers such as the
>> RISC-V PLIC use a extended-interrupt property and therefore do not get
>> properly considered during initialisation.
>>
>> This means that if anything changes in the driver initialisation order
>> then the PLIC can get called before the CLINT nodes, and thus interrupts
>> do not get configured properly and the init continues without noticing
>> the error until drivers fail due to having no interrupts delivered.
>>
>> Add code to the of_irq_init that checks for the extended-interrupt
>> property and adds these parent nodes so that they can be considered
>> during the calculations of whether an irq controller node can be
>> initialised.
>
> Isn't this already fixed by commit e91033621d56 ("of/irq: Use
> interrupts-extended to find parent")?
I didn't notice that commit, have been holding onto some of these
patches whilst sorting out permission to send.
The only thing my version does better is that it checks all of the
interrupt-extended contents so if there was a system with multiple
parents then we wouldn't consider them.
--
Ben
prev parent reply other threads:[~2022-07-11 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 16:52 Ben Dooks
2022-07-08 21:49 ` Rob Herring
2022-07-11 7:16 ` Ben Dooks [this message]
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=b9c97f5e-ca61-ee91-0cb7-a426a921474c@sifive.com \
--to=ben.dooks@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jude.onyenegecha@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sudip.mukherjee@sifive.com \
/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
all inboxes | Powered by JetHome®