From: Marc Zyngier <maz@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Rich Felker <dalias@libc.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip/jcore-aic: Fix missing allocation of IRQ descriptors
Date: Tue, 16 May 2023 11:06:29 +0100 [thread overview]
Message-ID: <86cz30mvyy.wl-maz@kernel.org> (raw)
In-Reply-To: <7e58646d7ae4cad32ae30e2e7b54806cc1272d63.camel@physik.fu-berlin.de>
On Thu, 11 May 2023 10:03:01 +0100,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
>
> On Thu, 2023-05-11 at 09:47 +0100, Marc Zyngier wrote:
> > On Thu, 11 May 2023 08:22:20 +0100,
> > John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> > >
> > > Hi Jason!
> >
> > ???
>
> Sorry, I was confused by this:
>
> > > > [- Jason]
> > > >
> > > > It really begs the question: how has it ever been working before?
> > >
> > > Users already used a locally patched kernel to work around this problem.
> >
> > You're not answering my question. Does it mean JCore never worked
> > upstream?
>
> It did still work which is why the previously suggested change was to make a
> failing call to irq_alloc_descs() non-fatal. The boards still booted
> up.
I don't get it. Either the descriptors are already allocated, and you
don't need this call, or they were never allocated and this never
worked. Which one is it?
>
> > > > Is there any plan to modernise the port and get it to allocate
> > > > irq_descs on demand, as we do on most architectures?
> > >
> > > Yes, there are plans to modernize the port. We're first working on
> > > upstreaming all kinds of patches that have been queuing up over the
> > > time.
> >
> > I'd rather you skip that step and focus on making it work as a modern
> > architecture. This really looks like ARM circa 2007... :-/
>
> We have a patch-set for switching it to device tree in the pipeline.
Again: why aren't we reviewing that instead of beating a long dead
horse?
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-05-16 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 16:33 [PATCH] irqchip/jcore-aic: Fix missing allocation of IRQ descriptors John Paul Adrian Glaubitz
2023-05-11 6:56 ` Marc Zyngier
2023-05-11 7:22 ` John Paul Adrian Glaubitz
2023-05-11 8:47 ` Marc Zyngier
2023-05-11 9:03 ` John Paul Adrian Glaubitz
2023-05-16 10:06 ` Marc Zyngier [this message]
2023-05-16 10:15 ` John Paul Adrian Glaubitz
2023-05-11 14:35 ` Geert Uytterhoeven
2023-05-11 14:47 ` John Paul Adrian Glaubitz
2023-05-12 3:21 ` Rob Landley
2023-06-17 7:02 ` [irqchip: irq/irqchip-next] " irqchip-bot for John Paul Adrian Glaubitz
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=86cz30mvyy.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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