From: Lukas Wunner <lukas@wunner.de>
To: Hans de Goede <hdegoede@redhat.com>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
Aditya Garg <gargaditya08@live.com>
Subject: Re: [PATCH] ACPI: video: Fix Apple GMUX backlight detection
Date: Thu, 15 Dec 2022 11:22:11 +0100 [thread overview]
Message-ID: <20221215102211.GA5147@wunner.de> (raw)
In-Reply-To: <20221215094138.7120-1-hdegoede@redhat.com>
On Thu, Dec 15, 2022 at 10:41:38AM +0100, Hans de Goede wrote:
> The apple-gmux driver only binds to old GMUX devices which have an
> IORESOURCE_IO resource (using inb()/outb()) rather then memory-mapped
> IO (IORESOURCE_MEM).
>
> T2 MacBooks use the new style GMUX devices (with IORESOURCE_MEM access),
> so these are not supported by the apple-gmux driver. This is not a problem
> since they have working ACPI video backlight support.
Interesting.
> +static bool apple_gmux_backlight_present(void)
> +{
> + struct acpi_device *adev;
> + struct device *dev;
> +
> + adev = acpi_dev_get_first_match_dev(GMUX_ACPI_HID, NULL, -1);
> + if (!adev)
> + return false;
> +
> + dev = acpi_get_first_physical_node(adev);
> + if (!dev)
> + return false;
> +
> + /*
> + * drivers/platform/x86/apple-gmux.c only supports old style
> + * Apple GMUX with an IO-resource.
> + */
> + return pnp_get_resource(to_pnp_dev(dev), IORESOURCE_IO, 0) != NULL;
> +}
The T2 is represented by a PCI device with ID 106B:1802.
Instead of the above, how about amending apple_gmux_present()
with a simple check like this:
/* T2 Macs drive GMUX via MMIO, which is unsupported for now */
if (pci_dev_present({{PCI_DEVICE(PCI_VENDOR_ID_APPLE, 0x1802)}, {}}))
return false;
Thanks,
Lukas
next prev parent reply other threads:[~2022-12-15 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:41 [PATCH] ACPI: video: Fix Apple GMUX backlight detection Hans de Goede
2022-12-15 10:22 ` Lukas Wunner [this message]
2022-12-15 10:50 ` Hans de Goede
2022-12-22 16:44 ` Rafael J. Wysocki
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=20221215102211.GA5147@wunner.de \
--to=lukas@wunner.de \
--cc=gargaditya08@live.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--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 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.