From: Marc Zyngier <maz@kernel.org>
To: Sander Vanheule <sander@svanheule.net>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Birger Koblitz <mail@birger-koblitz.de>,
Bert Vermeulen <bert@biot.com>, John Crispin <john@phrozen.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/3] Per-parent domains for realtek-rtl IRQ driver
Date: Wed, 09 Feb 2022 13:58:57 +0000 [thread overview]
Message-ID: <874k585efy.wl-maz@kernel.org> (raw)
In-Reply-To: <cover.1644165421.git.sander@svanheule.net>
On Sun, 06 Feb 2022 16:41:50 +0000,
Sander Vanheule <sander@svanheule.net> wrote:
>
> The original implementation for this interrupt controller/router used
> an interrupt-map parser to determine which parent interrupts were
> present. However, this controller is not transparent, so a list of
> parent interrupts seems more appropriate, while also getting rid of the
> assumed routing to parent interrupts.
>
> Additionally, N real cascaded interrupts are implemented, instead of
> handling all input interrupts with one cascaded interrupt. Otherwise it
> is possible that the priority of the parent interrupts is not respected.
Just to be clear: this means that although you allow the new driver to
somehow still work with the old DT, the opposite (old kernel, new DT)
will probably fail horribly.
Is everyone comfortable with that?
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-02-09 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 16:41 [PATCH v4 0/3] Per-parent domains for realtek-rtl IRQ driver Sander Vanheule
2022-02-06 16:41 ` [PATCH v4 1/3] dt-bindings: interrupt-controller: realtek,rtl-intc: require parents Sander Vanheule
2022-02-07 20:24 ` Rob Herring
2022-02-06 16:41 ` [PATCH v4 2/3] irqchip/realtek-rtl: use parent interrupts Sander Vanheule
2022-02-06 16:41 ` [PATCH v4 3/3] irqchip/realtek-rtl: use per-parent domains Sander Vanheule
2022-02-09 14:10 ` Marc Zyngier
2022-02-09 21:22 ` Sander Vanheule
2022-02-09 13:58 ` Marc Zyngier [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=874k585efy.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=bert@biot.com \
--cc=devicetree@vger.kernel.org \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@birger-koblitz.de \
--cc=robh+dt@kernel.org \
--cc=sander@svanheule.net \
--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;
as well as URLs for NNTP newsgroup(s).