public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Rafa?? Mi??ecki <zajec5@gmail.com>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Richard Purdie <rpurdie@rpsys.net>
Subject: Re: Backlight device class redesign
Date: Sat, 28 Nov 2009 15:21:27 -0200	[thread overview]
Message-ID: <20091128172127.GC28189@khazad-dum.debian.net> (raw)
In-Reply-To: <b170af450911280458v66c3741dy2a1d9c5297c8faf5@mail.gmail.com>

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

  reply	other threads:[~2009-11-28 17:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28  0:30 Backlight device class redesign Rafał Miłecki
2009-11-28 10:30 ` Rafał Miłecki
2009-11-28 12:22   ` Henrique de Moraes Holschuh
2009-11-28 12:58     ` Rafał Miłecki
2009-11-28 17:21       ` Henrique de Moraes Holschuh [this message]
2009-11-29 20:09 ` Rafał Miłecki
2009-11-29 21:51   ` Rafał Miłecki
2009-11-29 21:51     ` Rafał Miłecki
2009-11-30  0:04       ` Henrique de Moraes Holschuh
2009-12-03  8:01   ` Zhang Rui
2009-12-03 10:52     ` Henrique de Moraes Holschuh
2009-12-04  1:50       ` Zhang Rui
2009-12-03 14:55     ` Matthew Garrett

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=20091128172127.GC28189@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=zajec5@gmail.com \
    /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