mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Linux ACPI <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Richard Purdie <rpurdie@rpsys.net>
Subject: Re: Backlight device class redesign
Date: Sun, 29 Nov 2009 22:51:31 +0100	[thread overview]
Message-ID: <b170af450911291351r443e355fraf1828dc1163e9e3@mail.gmail.com> (raw)
In-Reply-To: <b170af450911291209o33ebfc36n850826e54096f3b4@mail.gmail.com>

W dniu 29 listopada 2009 21:09 użytkownik Rafał Miłecki
<zajec5@gmail.com> napisał:
> So I think we have to register every device and just keep symlink
> /sys/class/backlight/display_name pointing best device. We could
> register devices in
> 1) /sys/class/backlight/.devicename (hidden)
> 2) some /sys/class/internal-usage/devicename
>
> Do you agree on this?

Please, see attached patch. TODO:
1) Add METHOD (enum { ACPI, GPU, PLATFORM} ) as
backlight_device_register parameter
2) Add display name as backlight_device_register parameter
3) Use given METHODs in backlight_best_device
4) Fix symlinks to be created in /sys/class/backlight/ instead of
/sys/dev/char/ (how?!)

What about proposed solution?

-- 
Rafał

  reply	other threads:[~2009-11-29 21:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28  0:30 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
2009-11-29 20:09 ` Rafał Miłecki
2009-11-29 21:51   ` Rafał Miłecki [this message]
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=b170af450911291351r443e355fraf1828dc1163e9e3@mail.gmail.com \
    --to=zajec5@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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

all inboxes | Powered by JetHome®