linux-kernel - Re: Backlight device class redesign

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091203145502.GA23212@srcf.ucam.org>
Date:	Thu, 3 Dec 2009 14:55:02 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Zhang Rui <rui.zhang@...el.com>
Cc:	Rafał Miłecki <zajec5@...il.com>,
	Linux ACPI <linux-acpi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Henrique de Moraes Holschuh <hmh@....eng.br>,
	Richard Purdie <rpurdie@...ys.net>
Subject: Re: Backlight device class redesign

On Thu, Dec 03, 2009 at 04:01:14PM +0800, Zhang Rui wrote:

> IMO, we should create one device for one display.
> For example, device /sys/class/backlight/panel0 is created the first
> time a backlight_ops for this display is registered.

For anything other than the simple case (one display per machine), how 
do you know whether the firmware, platform and gpu are referring to the 
same display device?

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/