From: "irqchip-bot for Jianmin Lv" <tip-bot2@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Jianmin Lv <lvjianmin@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>,
Marc Zyngier <maz@kernel.org>,
tglx@linutronix.de
Subject: [irqchip: irq/irqchip-next] ACPI / PCI: fix LPIC IRQ model default PCI IRQ polarity
Date: Sat, 26 Nov 2022 13:34:44 -0000 [thread overview]
Message-ID: <166946968496.4906.3078056706775236509.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20221022075955.11726-2-lvjianmin@loongson.cn>
The following commit has been merged into the irq/irqchip-next branch of irqchip:
Commit-ID: d0c50cc4b957b2cf6e43cec4998d212b5abe9220
Gitweb: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms/d0c50cc4b957b2cf6e43cec4998d212b5abe9220
Author: Jianmin Lv <lvjianmin@loongson.cn>
AuthorDate: Sat, 22 Oct 2022 15:59:52 +08:00
Committer: Marc Zyngier <maz@kernel.org>
CommitterDate: Sat, 26 Nov 2022 12:57:18
ACPI / PCI: fix LPIC IRQ model default PCI IRQ polarity
On LoongArch based systems, the PCI devices (e.g. SATA controllers and
PCI-to-PCI bridge controllers) in Loongson chipsets output high-level
interrupt signal to the interrupt controller they are connected (see
Loongson 7A1000 Bridge User Manual v2.00, sec 5.3, "For the bridge chip,
AC97 DMA interrupts are edge triggered, gpio interrupts can be configured
to be level triggered or edge triggered as needed, and the rest of the
interrupts are level triggered and active high."), while the IRQs are
active low from the perspective of PCI (see Conventional PCI spec r3.0,
sec 2.2.6, "Interrupts on PCI are optional and defined as level sensitive,
asserted low."), which means that the interrupt output of PCI devices plugged
into PCI-to-PCI bridges of Loongson chipset will be also converted to high-level.
So high level triggered type is required to be passed to acpi_register_gsi()
when creating mappings for PCI devices.
Signed-off-by: Jianmin Lv <lvjianmin@loongson.cn>
Reviewed-by: Huacai Chen <chenhuacai@loongson.cn>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20221022075955.11726-2-lvjianmin@loongson.cn
---
drivers/acpi/pci_irq.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/pci_irq.c b/drivers/acpi/pci_irq.c
index 08e1577..ff30cec 100644
--- a/drivers/acpi/pci_irq.c
+++ b/drivers/acpi/pci_irq.c
@@ -387,13 +387,15 @@ int acpi_pci_irq_enable(struct pci_dev *dev)
u8 pin;
int triggering = ACPI_LEVEL_SENSITIVE;
/*
- * On ARM systems with the GIC interrupt model, level interrupts
+ * On ARM systems with the GIC interrupt model, or LoongArch
+ * systems with the LPIC interrupt model, level interrupts
* are always polarity high by specification; PCI legacy
* IRQs lines are inverted before reaching the interrupt
* controller and must therefore be considered active high
* as default.
*/
- int polarity = acpi_irq_model == ACPI_IRQ_MODEL_GIC ?
+ int polarity = acpi_irq_model == ACPI_IRQ_MODEL_GIC ||
+ acpi_irq_model == ACPI_IRQ_MODEL_LPIC ?
ACPI_ACTIVE_HIGH : ACPI_ACTIVE_LOW;
char *link = NULL;
char link_desc[16];
next prev parent reply other threads:[~2022-11-26 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 7:59 [PATCH V5 0/4] irqchip: Support to set irq type for ACPI path Jianmin Lv
2022-10-22 7:59 ` [PATCH V5 1/4] ACPI / PCI: fix LPIC IRQ model default PCI IRQ polarity Jianmin Lv
2022-11-26 13:34 ` irqchip-bot for Jianmin Lv [this message]
2022-10-22 7:59 ` [PATCH V5 2/4] irqchip/loongson-pch-pic: fix translate callback for DT path Jianmin Lv
2022-11-26 13:34 ` [irqchip: irq/irqchip-next] irqchip/loongson-pch-pic: Fix " irqchip-bot for Jianmin Lv
2022-10-22 7:59 ` [PATCH V5 3/4] irqchip/loongson-pch-pic: Support to set IRQ type for ACPI path Jianmin Lv
2022-11-26 13:34 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianmin Lv
2022-10-22 7:59 ` [PATCH V5 4/4] irqchip/loongson-liointc: " Jianmin Lv
2022-11-26 13:34 ` [irqchip: irq/irqchip-next] " irqchip-bot for Jianmin Lv
2022-10-22 8:05 ` [PATCH V5 0/4] irqchip: Support to set irq " Huacai Chen
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=166946968496.4906.3078056706775236509.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=chenhuacai@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=maz@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 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.