From: Lukas Wunner <lukas@wunner.de>
To: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>
Cc: hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v3] apple-gmux: preserve brightness using EFI
Date: Sun, 15 Mar 2026 15:28:00 +0100 [thread overview]
Message-ID: <abbB8F9WE0kUUzrZ@wunner.de> (raw)
In-Reply-To: <20260314224503.12022-1-atharvatiwarilinuxdev@gmail.com>
On Sun, Mar 15, 2026 at 04:15:03AM +0530, Atharva Tiwari wrote:
> > This version moves the EFI handling back to the gmux driver. Why?
>
> Because the platform maintainer just NACKed the EFI backend driver, so i
> cant do anything
>
> https://lore.kernel.org/all/c2d14818-1c34-47c7-a210-1f7c737f0bc9@kernel.org/
The NAK was only because of writing to the EFI variable in frequent
intervals. I'd assume Hans is fine if it is synced only once on
shutdown.
Splitting out the EFI handling into a separate component in
drivers/firmware/efi/ as you did in this version:
https://lore.kernel.org/all/20260206125641.12983-2-atharvatiwarilinuxdev@gmail.com/
... is much cleaner as it allows code reuse by i915 and other drivers
which may be controlling brightness on MacBooks or iMacs without a gmux.
So I'd really prefer if you went back to that, but sync only on shutdown
and only if brightness has changed, per Hans' request.
BTW, I did another test on my MacBook9,1 with brightness set to maximum
on macOS, then booting into Linux. The EFI variable as set by macOS
contains:
07 00 00 80 ff 03
... but /sys/class/backlight/gmux_backlight/brightness contains the
value 110400 (0x1af40), which obviously exceeds USHRT_MAX. So I'm not
convinced that writing that raw value to the EFI variable actually yields
correct results.
Thanks,
Lukas
next prev parent reply other threads:[~2026-03-15 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 9:26 [PATCH v3] apple-gmux: preserve brightness using EFI Atharva Tiwari
2026-02-11 12:01 ` Hans de Goede
2026-02-11 12:30 ` Atharva Tiwari
2026-02-11 12:32 ` Hans de Goede
2026-03-13 19:39 ` Atharva Tiwari
2026-03-14 20:06 ` Lukas Wunner
2026-02-11 12:48 ` Lukas Wunner
2026-03-14 22:45 ` Atharva Tiwari
2026-03-14 23:11 ` Armin Wolf
2026-03-15 22:08 ` Atharva Tiwari
2026-03-15 22:54 ` Armin Wolf
2026-03-16 15:37 ` Atharva Tiwari
2026-03-15 14:28 ` Lukas Wunner [this message]
2026-03-15 22:05 ` Atharva Tiwari
2026-02-11 17:03 ` kernel test robot
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=abbB8F9WE0kUUzrZ@wunner.de \
--to=lukas@wunner.de \
--cc=atharvatiwarilinuxdev@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox