linux-kernel - Re: Backlight control only in the kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 7 Aug 2013 13:04:06 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Matthew Garrett <matthew.garrett@...ula.com>
Cc:	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"seth.forshee@...onical.com" <seth.forshee@...onical.com>,
	"joeyli.kernel@...il.com" <joeyli.kernel@...il.com>,
	"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
	"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"lenb@...nel.org" <lenb@...nel.org>, "rjw@...k.pl" <rjw@...k.pl>,
	Aaron Lu <aaron.lu@...el.com>
Subject: Re: Backlight control only in the kernel?

On Wed, Aug 07, 2013 at 10:36:08AM +0000, Matthew Garrett wrote:
> Not really. The ACPI driver is able to do this because the events and
> the backlight are associated with the same device.

Well, it doesn't work at least in my case.

I need to echo stuff into /sys/class/backlight/intel_backlight :(

> We could potentially make something work with GPU backlight drivers
> since their PCI device should also be associated with the backlight
> device, but things get complicated quickly - once ddcci support
> is hooked up you'll also have kernel backlight devices for some
> external monitors, and now you need to make a policy decision about
> which display should be controlled in response to the keypress. One
> reasonable choice would be whichever display contains the currently
> focused window, which is obviously out of scope for the kernel.
>
> So if we're going to do this then we need a generalised mechanism
> in-kernel for connecting input devices to backlight devices, and we
> need a mechanism for disabling it when userspace knows better. This
> sounds like a lot of work for something that should really just be
> handled by userspace already.

That's easy: single-monitor setups have it enabled by default. So every
laptop out there will just work, without any userspace intervention.

More complicated situations are presented with the opportunity to
disable the kernel-side control and do it themselves.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/