From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 215730] New: acpi_bus_register_driver() does not work on Alder Lake
Date: Wed, 23 Mar 2022 03:28:30 +0000 [thread overview]
Message-ID: <bug-215730-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215730
Bug ID: 215730
Summary: acpi_bus_register_driver() does not work on Alder Lake
Product: Drivers
Version: 2.5
Kernel Version: 5.13, 5.16, maybe all.
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: xuemin.wu@dbh.dynabook.com
Regression: No
e.g.
in drivers/platform/x86/toshiba_acpi.c
acpi_bus_register_driver(&toshiba_acpi_driver);
does not work:
when execute acpi_bus_register_driver(&toshiba_acpi_driver).
the ".add" function is not called to add the driver.
and dmesg no errors/warnings have been reported when insmod this driver.
This issue exists on Alder Lake.
This issue does not exist on Tiger Lake.
Thank you.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-03-23 3:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 3:28 bugzilla-daemon [this message]
2022-03-23 3:34 ` [Bug 215730] acpi_bus_register_driver() does not work on Alder Lake bugzilla-daemon
2022-03-23 5:36 ` bugzilla-daemon
2022-03-23 5:46 ` bugzilla-daemon
2022-03-23 6:13 ` bugzilla-daemon
2022-03-23 9:24 ` bugzilla-daemon
2022-03-23 9:31 ` bugzilla-daemon
2022-03-23 9:36 ` bugzilla-daemon
2022-03-23 9:47 ` bugzilla-daemon
2022-03-23 19:10 ` bugzilla-daemon
2022-03-24 2:44 ` bugzilla-daemon
2022-03-24 3:58 ` bugzilla-daemon
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=bug-215730-215701@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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 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.