LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru> To: toshiba_acpi@memebeam.org, linux-acpi@vger.kernel.org Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: ACPI video.c brightness handler conflicts with toshiba_acpi Date: Sat, 6 Sep 2008 11:08:33 +0400 [thread overview] Message-ID: <200809061108.34877.arvidjaar@mail.ru> (raw) [-- Attachment #1: Type: text/plain, Size: 748 bytes --] I have now two different devices that refer to the same hardware: lrwxrwxrwx 1 root root 0 2008-09-06 11:04 acpi_video0 -> ../../devices/virtual/backlight/acpi_video0/ lrwxrwxrwx 1 root root 0 2008-09-06 11:04 toshiba -> ../../devices/virtual/backlight/toshiba/ Unfortunately, due to ACPI implementation the acpi_video0 one is much inferior (as it provides only effectively two levels instead of 8); and user level tools are apparently quite confused which one to select. Is there any mechanism that would allow tochiba_acpi to claim brightness for internal LCD screen that video would not attempt to grab it too? Of course manually disabling brightness handling in video is always possible, still is nice for this to be handled automatically. [-- Attachment #2: This is a digitally signed message part. --] [-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-09-06 7:08 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-09-06 7:08 Andrey Borzenkov [this message] 2008-09-06 7:19 ` ACPI video.c brightness handler conflicts with toshiba_acpi Andrey Borzenkov 2008-09-08 1:01 ` Thomas Renninger 2008-09-08 17:24 ` Andrey Borzenkov 2008-10-27 16:52 ` Andrey Borzenkov 2008-10-28 13:26 ` Thomas Renninger 2008-10-28 15:15 ` Rafael J. Wysocki 2008-10-28 16:22 ` Andrey Borzenkov 2008-10-29 15:54 ` Thomas Renninger 2008-10-29 16:22 ` Andrey Borzenkov 2008-10-29 17:13 ` Andi Kleen 2008-10-29 21:01 ` Thomas Renninger 2008-11-08 3:29 ` Len Brown 2008-10-28 18:08 ` Thomas Renninger 2008-09-08 1:13 ` Zhang Rui
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=200809061108.34877.arvidjaar@mail.ru \ --to=arvidjaar@mail.ru \ --cc=linux-acpi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=toshiba_acpi@memebeam.org \ /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: linkBe 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; as well as URLs for NNTP newsgroup(s).