From: Hans de Goede <hdegoede@redhat.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Aditya Garg <gargaditya08@live.com>,
Mark Gross <mgross@linux.intel.com>,
linux-acpi@vger.kernel.org, Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 0/3] ACPI: video/apple-gmux: Improve apple-gmux backlight detection
Date: Mon, 23 Jan 2023 13:38:37 +0100 [thread overview]
Message-ID: <255bf66e-eb27-af2b-9a13-8b7d4b7b3c46@redhat.com> (raw)
In-Reply-To: <20230123120900.GA1924@wunner.de>
Hi,
On 1/23/23 13:09, Lukas Wunner wrote:
> On Mon, Jan 23, 2023 at 12:37:47PM +0100, Hans de Goede wrote:
>> Some apple laptop models have an ACPI device with a HID of APP000B
>> and that device has an IO resource (so it does not describe the new
>> unsupported MMIO based gmux type), but there actually is no gmux
>> in the laptop at all.
>>
>> This patch-series improves the drivers/acpi/video_detect.c so that
>> it no longer tries to use the non present gmux in this case.
>>
>> Note I'm still waiting for testing feedback from the reporter of
>> this problem. But from the logs the problem is clear
>> (the logs show: "apple_gmux: gmux device not present")
>
> Please provide a link to the original report. I would also like to
> know the exact MacBook model used and I would like to see full dmesg
> output as well as an acpidump.
I only have a report by private email. This does include full dmesg
output and an acpidump. I will forward this to you in a private
email.
The reporter describes their model as a macbookpro8,1.
> What you're saying here is that there's a fake APP000B device present
> in DSDT
Yes that is exactly what I'm saying.
> and I have a hard time believng that.
Yes that seems to be exactly what is happening. If you look at
the drivers/platform/x86/apple-gmux.c code that is pretty much
the only scenario which leads to the:
apple_gmux: gmux device not present
message getting logged; and it seems to me that the reason that
check is there likely is exactly because of such machines
actually existing.
And /sys/class/backlight contains only intel_backlight
suggesting that this is not a hybrid gfx machine. Which also
matches with the specs which I can find for the macbookpro8,1.
Yet there is an APP000B device present in the DSDT, here is
the relevant bit of the DSDT:
Device (GMUX)
{
Name (_HID, EisaId ("APP000B")) // _HID: Hardware ID
Name (_CID, "gmux") // _CID: Compatible ID
Name (_STA, 0x0B) // _STA: Status
Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings
{
IO (Decode16,
0x0700, // Range Minimum
0x07FF, // Range Maximum
0x01, // Alignment
0xFF, // Length
)
})
Name (_PRW, Package (0x02) // _PRW: Power Resources for Wake
{
0x16,
0x03
})
Scope (\_GPE)
{
Method (_L16, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF
{
Notify (\_SB.PCI0.LPCB.GMUX, 0x80) // Status Change
}
}
Name (GMGP, 0x16)
Method (GMSP, 1, NotSerialized)
{
If ((Arg0 <= 0x01))
{
GP06 |= Arg0
}
}
Method (GMLV, 0, NotSerialized)
{
Return (GP06) /* \GP06 */
}
}
}
Regards,
Hans
next prev parent reply other threads:[~2023-01-23 12:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 11:37 [PATCH 0/3] ACPI: video/apple-gmux: Improve apple-gmux backlight detection Hans de Goede
2023-01-23 11:37 ` [PATCH 1/3] platform/x86: apple-gmux: Move port defines to apple-gmux.h Hans de Goede
2023-01-23 11:37 ` [PATCH 2/3] platform/x86: apple-gmux: Add apple_gmux_detect() helper Hans de Goede
2023-01-23 13:49 ` Lukas Wunner
2023-01-23 14:13 ` Hans de Goede
2023-01-23 14:23 ` Lukas Wunner
2023-01-23 15:05 ` Hans de Goede
2023-01-23 15:10 ` Hans de Goede
2023-01-23 16:35 ` Andy Shevchenko
2023-01-23 11:37 ` [PATCH 3/3] ACPI: video: Fix apple gmux detection Hans de Goede
2023-01-23 16:37 ` Andy Shevchenko
2023-01-23 17:25 ` Hans de Goede
2023-01-23 19:20 ` Rafael J. Wysocki
2023-01-23 12:09 ` [PATCH 0/3] ACPI: video/apple-gmux: Improve apple-gmux backlight detection Lukas Wunner
2023-01-23 12:38 ` Hans de Goede [this message]
2023-01-23 13:58 ` Lukas Wunner
2023-01-23 15:05 ` Hans de Goede
2023-01-23 14:53 ` Aditya Garg
2023-01-24 8:21 ` Orlando Chamberlain
2023-01-24 10:26 ` Aditya Garg
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=255bf66e-eb27-af2b-9a13-8b7d4b7b3c46@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@infradead.org \
--cc=gargaditya08@live.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mgross@linux.intel.com \
--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