mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: Atharva Tiwari <atharvatiwarilinuxdev@gmail.com>, lukas@wunner.de
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 00:11:05 +0100	[thread overview]
Message-ID: <21b44fb3-238a-417d-b414-e7903b8fdc18@gmx.de> (raw)
In-Reply-To: <20260314224503.12022-1-atharvatiwarilinuxdev@gmail.com>

Am 14.03.26 um 23:45 schrieb Atharva Tiwari:

>> 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/
>
After reading this, i wonder why this functionality should live inside the kernel after all.
Systemd seems to already store the backlight brightness during shutdown/reboot, so maybe
having a small oneshot service that synchronizes those values with the EFI variable during
shutdown/reboot might be easier?

Thanks,
Armin Wolf


  reply	other threads:[~2026-03-14 23:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  9:26 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 [this message]
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
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=21b44fb3-238a-417d-b414-e7903b8fdc18@gmx.de \
    --to=w_armin@gmx.de \
    --cc=atharvatiwarilinuxdev@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --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
all inboxes | Powered by JetHome®