From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: Backlight device class redesign Date: Thu, 3 Dec 2009 14:55:02 +0000 Message-ID: <20091203145502.GA23212@srcf.ucam.org> References: <1259827274.27069.50.camel@rzhang1-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:34815 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751474AbZLCOzO (ORCPT ); Thu, 3 Dec 2009 09:55:14 -0500 Content-Disposition: inline In-Reply-To: <1259827274.27069.50.camel@rzhang1-desktop> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Zhang Rui Cc: =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , Linux ACPI , Linux Kernel Mailing List , Henrique de Moraes Holschuh , Richard Purdie 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@srcf.ucam.org