From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 213297] ideapad-laptop: DYTC interface not found, several functionalities missing
Date: Tue, 01 Jun 2021 19:23:08 +0000 [thread overview]
Message-ID: <bug-213297-215701-NbrV9Hfg8M@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213297-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213297
--- Comment #5 from Barnabás Pőcze (pobrn@protonmail.com) ---
The DSDT contains the following:
Method (DYTC, 1, Serialized)
{
Local0 = Arg0
DYTP = Local0
Local1 = Zero
Switch (ToInteger ((Local0 & 0x01FF)))
{
Case (Zero)
{
Local1 = 0x0100
Local1 |= 0x40000000
Local1 |= Zero
Local1 |= One
}
...
and you can also see that the DYTC method returns "Local1", which is set to
0x40000101 (I think - but the important part is the 0x40...). And you can also
determine from the driver that the version is in bits 28-31 of the return value
of the DYTC method when called with 0 as its first argument. And those bits are
exactly 4.
--
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 prev parent reply other threads:[~2021-06-01 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 13:36 [Bug 213297] New: ideapad-laptop: DYTC interface not found, several functionalities missing bugzilla-daemon
2021-05-31 13:38 ` [Bug 213297] " bugzilla-daemon
2021-05-31 13:38 ` bugzilla-daemon
2021-05-31 14:26 ` bugzilla-daemon
2021-06-01 19:00 ` bugzilla-daemon
2021-06-01 19:23 ` bugzilla-daemon [this message]
2021-06-01 19:45 ` bugzilla-daemon
2022-06-21 21:19 ` bugzilla-daemon
2022-06-22 8:51 ` bugzilla-daemon
2022-06-22 9:46 ` bugzilla-daemon
2022-06-23 12:00 ` bugzilla-daemon
2022-06-23 15:14 ` bugzilla-daemon
2022-06-27 14:23 ` 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-213297-215701-NbrV9Hfg8M@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.