All of lore.kernel.org
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: Artur Flinta <aflinta@gmail.com>
Cc: linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: Fwd: [Bugreport] Screen backllight issues on FirePro M5950 (HP EliteBook 8560w)
Date: Tue, 24 Jan 2012 08:58:40 +0800	[thread overview]
Message-ID: <1327366720.7090.7.camel@linux-s257.site> (raw)
In-Reply-To: <CAEPe-G+jNsa5VScrk-Nii2e=0U5bVWtcCT5apOy0BAJrjKri4Q@mail.gmail.com>

On Mon, 2012-01-23 at 15:45 +0100, Artur Flinta wrote:
> Hi!
> 
> On Mon, Jan 23, 2012 at 12:55 AM, joeyli <jlee@suse.com> wrote:
> > Yes! we still need fix the problem with backlight control. Please kindly
> > give me the result after add the following debug parameter:
> >        acpi.debug_level=0xF acpi.debug_layer=0xFFFFFFFF log_buf_len=5M
> >
> 
> I did it and log is in attachment.
> 

Thanks, but looks like your kernel didn't enable 
	CONFIG_ACPI_DEBUG=y

So, doesn't show up any acpi debug log in messages.

> > And,
> > Did you try the following kernel parameter?
> >        acpi_backlight=vendor
> 
> Sure, but after applying it, backlight control keys doesn't work
> anymore, there is also no any message in the log.
> 

Does it work set backlight level by sysfs?
	echo 9 > /sys/class/backlight/acpi_video0/brightness

> I've also checked command: watch -n 1 cat
> /sys/firmware/acpi/interrupts/gpe[012][0123456789ABCDEF]
> but nothing changed too.
> 
> Regards
> Artur

I think don't neet test gpe anymore, because we already know function
key emit scancode.


Thanks a lot!
Joey Lee




  parent reply	other threads:[~2012-01-24  1:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 20:34 [Bugreport] Screen backllight issues on FirePro M5950 (HP EliteBook 8560w) Artur Flinta
     [not found] ` <CAGB3EUR750VpHdvrZ25mn9bcS-4ZT+BSJ_zD4-sRncyYNT=0Zg@mail.gmail.com>
2011-12-09 14:54   ` Fwd: " joeyli
     [not found]     ` <CAEPe-G+iooX_BOD=5m1nMgn+t63XGsLR+4JCfvHKOyTx98qydg@mail.gmail.com>
2011-12-21  4:55       ` joeyli
2011-12-21  9:42         ` Artur Flinta
2012-01-20  3:35           ` joeyli
     [not found]             ` <CAEPe-G+H6CDDzg9-fXZK4MJbKw_-MJFSMheCL9=yN4Gt=fmaTQ@mail.gmail.com>
2012-01-22  1:45               ` joeyli
     [not found]                 ` <CAEPe-GKff7y1g4qc5gSz4vuhz5P0XpGgPTO570YzkjO6AZNV4A@mail.gmail.com>
2012-01-22 23:55                   ` joeyli
     [not found]                     ` <CAEPe-G+jNsa5VScrk-Nii2e=0U5bVWtcCT5apOy0BAJrjKri4Q@mail.gmail.com>
2012-01-24  0:58                       ` joeyli [this message]
     [not found]                         ` <CAEPe-GLe9d7V9YLq+gGpb8N+a-9ELzeuvLbr=gKFbWU4JJxV-Q@mail.gmail.com>
2012-01-25  1:52                           ` joeyli
2012-01-26  6:43                             ` Artur Flinta
2012-01-26 16:40                               ` joeyli

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=1327366720.7090.7.camel@linux-s257.site \
    --to=jlee@suse.com \
    --cc=aflinta@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.