Linux-ACPI Archive mirror
 help / color / mirror / Atom feed
From: kovalev@altlinux.org
To: stable@vger.kernel.org
Cc: rafael@kernel.org, lenb@kernel.org, pavel@ucw.cz,
	hdegoede@redhat.com, linux-acpi@vger.kernel.org,
	kovalev@altlinux.org
Subject: [PATCH 6.1.y 14/14] ACPI: resource: Use IRQ override on Maibenben X565
Date: Mon,  8 Apr 2024 13:32:07 +0300	[thread overview]
Message-ID: <20240408103207.197423-15-kovalev@altlinux.org> (raw)
In-Reply-To: <20240408103207.197423-1-kovalev@altlinux.org>

From: Sergey Kalinichev <kalinichev.so.0@gmail.com>

commit 00efe7fcf9ceeff0808bca9460afb49e7ada6068 upstream.

Use ACPI IRQ override on Maibenben X565 laptop to make the internal
keyboard work.

Add a new entry to the irq1_edge_low_force_override structure, similar
to the existing ones.

Signed-off-by: Sergey Kalinichev <kalinichev.so.0@gmail.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Signed-off-by: Vasiliy Kovalev <kovalev@altlinux.org>
---
 drivers/acpi/resource.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
index 42b594f5127e4a..e2db4d5883ca40 100644
--- a/drivers/acpi/resource.c
+++ b/drivers/acpi/resource.c
@@ -623,6 +623,13 @@ static const struct dmi_system_id irq1_edge_low_force_override[] = {
 			DMI_MATCH(DMI_BOARD_NAME, "X577"),
 		},
 	},
+	{
+		/* Maibenben X565 */
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "MAIBENBEN"),
+			DMI_MATCH(DMI_BOARD_NAME, "X565"),
+		},
+	},
 	{ }
 };
 
-- 
2.33.8


      parent reply	other threads:[~2024-04-08 10:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 10:31 [PATCH v6.1.y 0/14 ] ACPI: resource: Add IRQ override quirks (backport changes from v6.9-rc3) kovalev
2024-04-08 10:31 ` [PATCH 6.1.y 01/14] ACPI: resource: Skip IRQ override on Asus Expertbook B2402FBA kovalev
2024-04-08 10:31 ` [PATCH 6.1.y 02/14] ACPI: resource: Skip IRQ override on ASUS ExpertBook B1502CBA kovalev
2024-04-08 10:31 ` [PATCH 6.1.y 03/14] ACPI: resource: Always use MADT override IRQ settings for all legacy non i8042 IRQs kovalev
2024-04-08 10:31 ` [PATCH 6.1.y 04/14] ACPI: resource: Honor MADT INT_SRC_OVR settings for IRQ1 on AMD Zen kovalev
2024-04-08 10:31 ` [PATCH 6.1.y 05/14] ACPI: resource: Add IRQ override quirk for PCSpecialist Elimina Pro 16 M kovalev
2024-04-08 10:31 ` [PATCH 6.1.y 06/14] ACPI: resource: Fix " kovalev
2024-04-08 10:32 ` [PATCH 6.1.y 07/14] ACPI: resource: Consolidate IRQ trigger-type override DMI tables kovalev
2024-04-08 10:32 ` [PATCH 6.1.y 08/14] ACPI: resource: Drop .ident values from dmi_system_id tables kovalev
2024-04-08 10:32 ` [PATCH 6.1.y 09/14] ACPI: resource: Add TongFang GM6BGEQ, GM6BG5Q and GM6BG0Q to irq1_edge_low_force_override[] kovalev
2024-04-08 10:32 ` [PATCH 6.1.y 10/14] ACPI: resource: Add DMI quirks for ASUS Vivobook E1504GA and E1504GAB kovalev
2024-04-08 10:32 ` [PATCH 6.1.y 11/14] ACPI: resource: Skip IRQ override on ASUS ExpertBook B1502CGA kovalev
2024-04-08 10:32 ` [PATCH 6.1.y 12/14] ACPI: resource: Skip IRQ override on ASUS ExpertBook B1502CVA kovalev
2024-04-08 10:32 ` [PATCH 6.1.y 13/14] ACPI: resource: Add IRQ override quirk for ASUS ExpertBook B2502FBA kovalev
2024-04-08 10:32 ` kovalev [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=20240408103207.197423-15-kovalev@altlinux.org \
    --to=kovalev@altlinux.org \
    --cc=hdegoede@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=stable@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).