From: Hans de Goede <hdegoede@redhat.com>
To: Jiri Slaby <jirislaby@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
hmh@hmh.eng.br, Mark Pearson <mpearson-lenovo@squebb.ca>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: WARNING at drivers/acpi/platform_profile.c:74 in platform_profile_show()
Date: Mon, 25 Sep 2023 10:57:52 +0200 [thread overview]
Message-ID: <74ad10fa-f0f6-f80f-7db3-fb01aae6f2d5@redhat.com> (raw)
In-Reply-To: <207922c7-7a56-499b-bbfd-9e8d6a0a06df@kernel.org>
+Cc Mark Pearson for thinkpad_acpi dytc support
Jiri,
On 9/25/23 09:38, Jiri Slaby wrote:
> On 25. 09. 23, 9:19, Jiri Slaby wrote:
>> But convert_dytc_to_profile() doesn't handle this at all. Do I have a newer DYTC interface? Or a broken one?
>
> Case (0x00)
> {
> Local1 = 0x0100
> Local1 |= 0x80000000
> Local1 |= 0x00
> Local1 |= 0x01
> }
>
> I.e. version 8.0, it seems.
>
> Full DSDT for reference:
> https://decibel.fi.muni.cz/~xslaby/n/DSDT.dsl
Mark, can you please take a look at this (it is a thinkpad_acpi dytc issue)?
Jiri, Thank you for all the debugging you have done on this. Can you please file
a bug with the details / summary here:
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers
Using Platform_x86 as component so that Mark has all the info in one place ?
Regards,
Hans
p.s.
Mark, maybe should add you to the MAINTAINERS section for thinkpad_acpi ?
next prev parent reply other threads:[~2023-09-25 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 5:35 Jiri Slaby
2023-09-25 5:42 ` Jiri Slaby
2023-09-25 7:19 ` Jiri Slaby
2023-09-25 7:38 ` Jiri Slaby
2023-09-25 8:57 ` Hans de Goede [this message]
2023-09-25 9:15 ` Jiri Slaby
2023-09-25 12:56 ` Mark Pearson
2023-09-25 12:58 ` Mark Pearson
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=74ad10fa-f0f6-f80f-7db3-fb01aae6f2d5@redhat.com \
--to=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=jirislaby@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®