From: Jan Beulich <jbeulich@suse.com>
To: "Sébastien Chaumat" <euidzero@gmail.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD
Date: Tue, 19 Dec 2023 14:33:22 +0100 [thread overview]
Message-ID: <629d9e79-e7be-4bf2-9052-42e653c5513c@suse.com> (raw)
In-Reply-To: <CAKm-UmYejm8CW-Enc_Y-aefcLPsRhQO8w2P-fNdu1zXMMjUAoA@mail.gmail.com>
On 05.12.2023 21:31, Sébastien Chaumat wrote:
>> [ 2.464598] amd_gpio AMDI0030:00: failed to enable wake-up interrupt
>
> Is it expected that IRQ7 goes from fasteoi (kernel 6.6.4 ) to
> ioapic-edge and IRQ9 to ioapic-level ?
>
> IR-IO-APIC 7-fasteoi pinctrl_amd
> IR-IO-APIC 9-fasteoi acpi
>
> to (xen 4.18.0)
>
> xen-pirq -ioapic-edge pinctrl_amd
> xen-pirq -ioapic-level acpi
>
> ?
So we need to come back to here: If the IRQ is indeed treated as level
triggered in the native kernel, it needs sorting where that information
is coming from there, and why different information is used under Xen.
Clearly xen_register_gsi() is passed ACPI_EDGE_SENSITIVE (and
ACPI_ACTIVE_LOW), supposedly coming from ACPI.
Jan
prev parent reply other threads:[~2023-12-19 13:33 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 9:56 [BUG]i2c_hid_acpi broken with 4.17.2 on Framework Laptop 13 AMD Sébastien Chaumat
2023-12-04 9:06 ` Jan Beulich
2023-12-04 19:17 ` Sébastien Chaumat
2023-12-05 8:17 ` Jan Beulich
2023-12-05 8:50 ` Sébastien Chaumat
2023-12-05 9:26 ` Sébastien Chaumat
2023-12-05 14:14 ` Sébastien Chaumat
2023-12-05 14:18 ` Jan Beulich
2023-12-05 16:19 ` Sébastien Chaumat
2023-12-05 20:31 ` Sébastien Chaumat
2023-12-06 7:15 ` Jan Beulich
2023-12-11 9:18 ` Sébastien Chaumat
2023-12-11 11:09 ` Sébastien Chaumat
2023-12-11 11:27 ` Jan Beulich
2023-12-11 14:17 ` Sébastien Chaumat
2023-12-11 14:21 ` Sébastien Chaumat
2023-12-18 16:21 ` Sébastien Chaumat
2023-12-18 16:44 ` Jan Beulich
2023-12-18 17:04 ` Sébastien Chaumat
2023-12-18 18:35 ` Sébastien Chaumat
2023-12-19 9:38 ` Jan Beulich
2023-12-19 13:15 ` Jan Beulich
2023-12-19 13:25 ` Jan Beulich
2023-12-19 15:15 ` Sébastien Chaumat
2023-12-19 19:03 ` Sébastien Chaumat
2023-12-19 23:06 ` Sébastien Chaumat
2023-12-19 23:11 ` Sébastien Chaumat
2023-12-19 23:50 ` Sébastien Chaumat
2023-12-20 0:23 ` Sébastien Chaumat
2023-12-20 10:06 ` Jan Beulich
2023-12-20 16:34 ` Sébastien Chaumat
2023-12-21 9:09 ` Jan Beulich
2023-12-21 12:40 ` Jan Beulich
2023-12-21 13:29 ` Juergen Gross
2023-12-21 15:22 ` Jan Beulich
2023-12-21 20:41 ` Sébastien Chaumat
2023-12-22 8:46 ` Jan Beulich
[not found] ` <CAKm-UmY126AfdGhWcZ3s9vwN9+ksVRRFEhOu0ZFMoDvxrqOibw@mail.gmail.com>
2023-12-22 14:38 ` Sébastien Chaumat
2023-12-27 10:20 ` Sébastien Chaumat
2023-12-27 11:43 ` Sébastien Chaumat
2024-01-02 20:23 ` Sébastien Chaumat
2024-01-16 15:52 ` Sébastien Chaumat
2024-01-16 16:18 ` Jan Beulich
2024-01-17 2:15 ` Mario Limonciello
2024-01-22 17:06 ` Sébastien Chaumat
2024-01-22 20:59 ` Mario Limonciello
2024-02-01 12:30 ` Sébastien Chaumat
2024-02-01 16:51 ` Sébastien Chaumat
2024-02-06 16:04 ` Sébastien Chaumat
2024-03-06 17:28 ` Sébastien Chaumat
2024-03-06 17:33 ` Mario Limonciello
2024-03-06 18:05 ` Sébastien Chaumat
2024-03-06 18:08 ` Mario Limonciello
2024-03-06 18:49 ` Sébastien Chaumat
2024-03-06 18:51 ` Mario Limonciello
2024-03-06 20:34 ` Sébastien Chaumat
2024-03-06 20:37 ` Mario Limonciello
2024-03-06 21:31 ` Marek Marczykowski-Górecki
2024-03-06 22:04 ` Mario Limonciello
2024-03-07 8:39 ` Jan Beulich
2024-03-08 9:55 ` Sébastien Chaumat
2024-10-10 14:45 ` David Woodhouse
2023-12-19 13:33 ` Jan Beulich [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=629d9e79-e7be-4bf2-9052-42e653c5513c@suse.com \
--to=jbeulich@suse.com \
--cc=euidzero@gmail.com \
--cc=xen-devel@lists.xenproject.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 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.