public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Anup Patel <anup@brainfault.org>,
	Atish Patra <atish.patra@wdc.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Christian Zigotzky <chzigotzky@xenosoft.de>,
	Guo Ren <guoren@linux.alibaba.com>,
	Nikita Shubin <nikita.shubin@maquefel.me>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Rob Herring <robh@kernel.org>,
	Vincent Pelletier <plr.vincent@gmail.com>,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] irqchip fixes for 5.16, take #1
Date: Fri, 12 Nov 2021 17:34:59 +0000	[thread overview]
Message-ID: <20211112173459.4015233-1-maz@kernel.org> (raw)

Hi Thomas,

Here's a small set of fixes for 5.16.

The most interesting one is a fix for the SiFive PLIC, which happens
to ignore an EOI if the interrupt has been masked during the
handling. Ouch. We also have a fix for the csky interrupt controller
which was mixing mask/unmask with disabled/enabled, and a another for
a regression in the OF irq parsing (this last one is carrying Rob's
 Reviewed-by: tag).

Note that the branch is on the same base as tip/irq/urgent
(debe436e77c7).

Please pull,

	M.

The following changes since commit debe436e77c72fcee804fb867f275e6d31aa999c:

  Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2021-11-10 17:05:37 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git tags/irqchip-fixes-5.16-1

for you to fetch changes up to 10a20b34d735fb4a4af067919b9c0a1c870dac99:

  of/irq: Don't ignore interrupt-controller when interrupt-map failed (2021-11-12 16:10:00 +0000)

----------------------------------------------------------------
irqchip fixes for 5.16, take #1

- Address an issue with the SiFive PLIC being unable to EOI
  a masked interrupt

- Move the disable/enable methods in the CSky mpintc to
  mask/unmask

- Fix a regression in the OF irq code where an interrupt-controller
  property in the same node as an interrupt-map property would get
  ignored

----------------------------------------------------------------
Guo Ren (2):
      irqchip/csky-mpintc: Fixup mask/unmask implementation
      irqchip/sifive-plic: Fixup EOI failed when masked

Marc Zyngier (1):
      of/irq: Don't ignore interrupt-controller when interrupt-map failed

 drivers/irqchip/irq-csky-mpintc.c |  8 ++++----
 drivers/irqchip/irq-sifive-plic.c |  8 +++++++-
 drivers/of/irq.c                  | 19 ++++++++++++++++---
 3 files changed, 27 insertions(+), 8 deletions(-)

             reply	other threads:[~2021-11-12 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 17:34 Marc Zyngier [this message]
2021-11-14 13:03 ` [tip: irq/urgent] Merge tag 'irqchip-fixes-5.16-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent tip-bot2 for Thomas Gleixner

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=20211112173459.4015233-1-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=anup@brainfault.org \
    --cc=atish.patra@wdc.com \
    --cc=bhelgaas@google.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=guoren@linux.alibaba.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita.shubin@maquefel.me \
    --cc=palmer@dabbelt.com \
    --cc=plr.vincent@gmail.com \
    --cc=robh@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