From: Lukas Wunner <lukas@wunner.de>
To: Hans de Goede <hdegoede@redhat.com>
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,
Emmanouil Kouroupakis <kartebi@gmail.com>
Subject: Re: [PATCH 0/3] ACPI: video/apple-gmux: Improve apple-gmux backlight detection
Date: Mon, 23 Jan 2023 14:58:27 +0100 [thread overview]
Message-ID: <20230123135827.GB2649@wunner.de> (raw)
In-Reply-To: <255bf66e-eb27-af2b-9a13-8b7d4b7b3c46@redhat.com>
On Mon, Jan 23, 2023 at 01:38:37PM +0100, Hans de Goede wrote:
> 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.
That's a 2011 13" MacBook Pro which indeed does not have dual GPUs.
I searched for other affected models and this seems to be more common
than I thought:
MacBookPro5,4
https://pastebin.com/8Xjq7RhS
MacBookPro8,1
https://linux-hardware.org/?probe=e513cfbadb&log=dmesg
MacBookPro9,2
https://bugzilla.kernel.org/attachment.cgi?id=278961
MacBookPro10,2
https://lkml.org/lkml/2014/9/22/657
MacBookPro11,2
https://forums.fedora-fr.org/viewtopic.php?id=70142
MacBookPro11,4
https://raw.githubusercontent.com/im-0/investigate-card-reader-suspend-problem-on-mbp11.4/master/test-16/dmesg
These are 13" and 15" models from the pre-retina and retina era
(2009 - 2015). None of them have dual GPUs. (Only a subset of
the 15" and 17" models had dual GPUs.) Apple sloppily included
a GMUX device on all of them and it wasn't a problem so far
because the gmux driver detects non-presence and bails out,
but it throws off the new backlight algorithm.
This is really sad. :(
Please add a Reported-by to your commits as well as the list I've
provided above so that we've got a complete record in the git history.
Thanks,
Lukas
next prev parent reply other threads:[~2023-01-23 13:58 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
2023-01-23 13:58 ` Lukas Wunner [this message]
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=20230123135827.GB2649@wunner.de \
--to=lukas@wunner.de \
--cc=andy@infradead.org \
--cc=gargaditya08@live.com \
--cc=hdegoede@redhat.com \
--cc=kartebi@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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