All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Maulik Shah <quic_mkshah@quicinc.com>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] irqchip fixes for 6.6, take #1
Date: Sun, 24 Sep 2023 10:41:05 +0100	[thread overview]
Message-ID: <20230924094105.2361754-1-maz@kernel.org> (raw)

Hi Thomas,

Here's the first cut of irqchip fixes that have graced my Inbox.
The most interesting thing is the fix for some Qualcomm HW, which
has a workaround for broken device trees that do not correctly
describe the hardware. The rest is a couple of fixes for the
Renesas RZG2L irqchip.

Please pull,

	M.

The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:

  Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 9b8df572ba3f4e544366196820a719a40774433e:

  irqchip: renesas-rzg2l: Fix logic to clear TINT interrupt source (2023-09-24 10:18:19 +0100)

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

- Fix QC PDC v3.2 support by working around broken firmware tables

- Fix rzg2l-irqc missing #interrupt-cells description in the DT binding

- Fix rzg2l-irqc interrupt masking

----------------------------------------------------------------
Biju Das (1):
      irqchip: renesas-rzg2l: Fix logic to clear TINT interrupt source

Dmitry Baryshkov (1):
      arm64: dts: qcom: sm8150: extend the size of the PDC resource

Lad Prabhakar (1):
      dt-bindings: interrupt-controller: renesas,rzg2l-irqc: Update description for '#interrupt-cells' property

Neil Armstrong (1):
      irqchip/qcom-pdc: Add support for v3.2 HW

 .../interrupt-controller/renesas,rzg2l-irqc.yaml   |  5 +-
 arch/arm64/boot/dts/qcom/sm8150.dtsi               |  2 +-
 drivers/irqchip/irq-renesas-rzg2l.c                |  2 +-
 drivers/irqchip/qcom-pdc.c                         | 69 ++++++++++++++++------
 4 files changed, 56 insertions(+), 22 deletions(-)

             reply	other threads:[~2023-09-24  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24  9:41 Marc Zyngier [this message]
2023-09-28 21:10 ` [tip: irq/urgent] Merge tag 'irqchip-fixes-6.6-1' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent tip-bot2 for Thomas Gleixner
2023-09-28 21:12 ` [GIT PULL] irqchip fixes for 6.6, take #1 Ingo Molnar
2023-09-28 21:17 ` Ingo Molnar
2023-09-29 12:31   ` Geert Uytterhoeven
2023-09-29 21:05     ` Ingo Molnar

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=20230924094105.2361754-1-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=geert+renesas@glider.be \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=quic_mkshah@quicinc.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.