From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT PULL] IRQ subsystem changes for v6.8
Date: Mon, 8 Jan 2024 12:43:37 +0100 [thread overview]
Message-ID: <ZZvf6ck/fO3NUXPN@gmail.com> (raw)
In-Reply-To: <ZZvLCmUqAriMV/Va@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
> Linus,
>
> Please pull the latest irq/core git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-2024-01-08
> .../bindings/interrupt-controller/qcom,mpm.yaml | 52 ++++++----
Forgot to mention that there's a merge conflict with your tree here,
between this new commit that restructures the MPM device-tree bindings:
ca596295f4c9 dt-bindings: interrupt-controller: mpm: Pass MSG RAM slice through phandle
... and this recent upstream commit that extended the bindings:
c0a2755aced9 dt-bindings: interrupt-controller: Allow #power-domain-cells
My resolution was:
mpm: interrupt-controller {
compatible = "qcom,mpm";
qcom,rpm-msg-ram = <&apss_mpm>;
interrupts = <GIC_SPI 197 IRQ_TYPE_EDGE_RISING>;
mboxes = <&apcs_glb 1>;
interrupt-controller;
#interrupt-cells = <2>;
interrupt-parent = <&intc>;
qcom,mpm-pin-count = <96>;
qcom,mpm-pin-map = <2 275>,
<5 296>,
<12 422>,
<24 79>,
<86 183>,
<91 260>;
#power-domain-cells = <0>;
};
But I didn't/couldn't test it. No complaints from linux-next testing so
far, FWIW.
Thanks,
Ingo
next prev parent reply other threads:[~2024-01-08 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:14 [GIT PULL] IRQ subsystem changes for v6.8 Ingo Molnar
2024-01-08 11:43 ` Ingo Molnar [this message]
2024-01-09 4:04 ` pr-tracker-bot
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=ZZvf6ck/fO3NUXPN@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox