mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luming Yu" <luming.yu@gmail.com>
To: "Danny Kukawka" <dkukawka@suse.de>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	luming.yu@intel.com
Subject: Re: [PATCH] ACPI video: Don't export sysfs backlight interface if query _BCL fail
Date: Sun, 6 May 2007 17:35:52 +0800	[thread overview]
Message-ID: <3877989d0705060235p7bb7e58j1cf3172f3971c7c5@mail.gmail.com> (raw)
In-Reply-To: <200704271218.07411.dkukawka@suse.de>

Ack!


On 4/27/07, Danny Kukawka <dkukawka@suse.de> wrote:
> Hi,
>
> currently the acpi video module export the backlight interface to sysfs also
> if acpi_video_device_lcd_query_levels() fails to read _BLC method (e.g.
> because the method is not available). In this case the userspace don't know
> which brightness level are supported and can't set a brightness level (echo
> return with: "write error: Invalid Argument"). This happend e.g. on a ASUS
> RF1 (correct supported by the asus-laptop module).
>
> The video module should not export the backlight interface if query _BLC fail,
> because you can't set anything from userspace and this make it useless.
>
> See also: http://bugzilla.kernel.org/show_bug.cgi?id=8375
>
> Danny
>
> From: Danny Kukawka <dkukawka@suse.de>
> Subject: ACPI video: Don't export sysfs backlight interface if query _BLC fail
>
> if qeuery _BCL fail (e.g. because the method is missing in BIOS) don't
> export the backlight interface to sysfs.
>
> Signed-off-by: Danny Kukawka <dkukawka@suse.de>
> ---
>  video.c |   78 ++++++++++++++++++++++++++++--------------------------
>  1 file changed, 41 insertions(+), 37 deletions(-)
>
> --- linux-2.6.21/drivers/acpi/video.c   2007-04-26 13:50:51.000000000 +0200
> +++ linux-2.6.21/drivers/acpi/video.c   2007-04-26 13:50:53.000000000 +0200
> @@ -531,7 +531,6 @@

      reply	other threads:[~2007-05-06  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 10:18 Danny Kukawka
2007-05-06  9:35 ` Luming Yu [this message]

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=3877989d0705060235p7bb7e58j1cf3172f3971c7c5@mail.gmail.com \
    --to=luming.yu@gmail.com \
    --cc=dkukawka@suse.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luming.yu@intel.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

all inboxes | Powered by JetHome®