From mboxrd@z Thu Jan 1 00:00:00 1970 From: Henrique de Moraes Holschuh Subject: Re: Backlight device class redesign Date: Sat, 28 Nov 2009 15:21:27 -0200 Message-ID: <20091128172127.GC28189@khazad-dum.debian.net> References: <20091128122229.GB17894@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from out4.smtp.messagingengine.com ([66.111.4.28]:42852 "EHLO out4.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752415AbZK1RVW (ORCPT ); Sat, 28 Nov 2009 12:21:22 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Rafa?? Mi??ecki Cc: Linux ACPI , Linux Kernel Mailing List , Richard Purdie On Sat, 28 Nov 2009, Rafa?? Mi??ecki wrote: > > Meanwhile, I'd like a LOT to know how I could parent the backlight device I > > export in a platform driver to the correct PCI or ACPI device for the main > > GPU... > > Is actually "parent" used for something? I can see it used in many > modules, but not sure where we use that pointer (if we do). For one, you get symlinks in sysfs, which would let userspace know what backlight is related to what PCI/video/whatever device. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh