linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joeyli <jlee@suse.com>
To: Alex Hung <alex.hung@canonical.com>
Cc: rui.zhang@intel.com, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] acpi: fix brightness level is initialized to zero when BIOS does not restore the brightness value to _BQC.
Date: Mon, 01 Oct 2012 16:34:10 +0800	[thread overview]
Message-ID: <1349080450.24232.35.camel@linux-s257.site> (raw)
In-Reply-To: <1349075823.24232.30.camel@linux-s257.site>

於 一,2012-10-01 於 15:17 +0800,joeyli 提到:
> 於 一,2012-10-01 於 15:03 +0800,Alex Hung 提到:
> > On 10/01/2012 02:47 PM, joeyli wrote:
> > > Hi Alex,
> > >
> > > 於 一,2012-10-01 於 13:39 +0800,Alex Hung 提到:
> > >> Signed-off-by: Alex Hung <alex.hung@canonical.com>
> > >> ---
> > >>   drivers/acpi/video.c |    4 ++++
> > >>   1 files changed, 4 insertions(+), 0 deletions(-)
> > >>
> > >> diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
> > >> index 42b226e..eaa9573 100644
> > >> --- a/drivers/acpi/video.c
> > >> +++ b/drivers/acpi/video.c
> > >> @@ -724,6 +724,10 @@ acpi_video_init_brightness(struct acpi_video_device *device)
> > >>   				if (level_old == br->levels[i])
> > >>   					level = level_old;
> > >>   		}
> > >> +
> > >> +		if (level == 0)
> > >> +			level = br->levels[(br->count) / 2 + 1];
> > >
> > > Looks here used the 50% brightness level.
> > >
> > > Per comment in video.c, we want set the backlight to max_level when
> > > level_old is invalid:
> > >
> > >          if (!br->flags._BQC_use_index) {
> > >                  /*
> > >                   * Set the backlight to the initial state.
> > >                   * On some buggy laptops, _BQC returns an uninitialized value
> > >                   * when invoked for the first time, i.e. level_old is invalid.
> > >                   * set the backlight to max_level in this case
> > >                   */
> > >
> > > I think here used max_level to fulfill it, e.g.
> > > 	
> > > +		if (level == 0)
> > > +			level = max_level;
> > >
> > > How do you think?
> > Hi Joey,
> > 
> > I was debating with myself which level to be set, ex. 50%, ~75% or 100%, 
> > and I think 50% *might* be closer to normal use-case (just a personal 
> > guess).
> > 
> > However, "max_level" seems to fit best if we treat the initial zero 
> > brightness in invalid. I can modify it according it that's preferred.
> > 
> > Thanks for the feedback.
> > 
> > Cheers,
> > Alex Hung
> > 
> 
> hm.... I have a question for what's the BIOS's problem that causes
> 'level == 0'?
> That implied the issue machine's max_level is 0?
> 
> 		/*
> 		 * Set the level to maximum and check if _BQC uses indexed value
> 		 */
> 		result = acpi_video_device_lcd_set_level(device, max_level);		/* write max_level purposely, then read level back, compare them */
> 		...
> 		result = acpi_video_device_lcd_get_level_current(device, &level, 0);
> 		...
> 		br->flags._BQC_use_index = (level == max_level ? 0 : 1);
> 		if (!br->flags._BQC_use_index) {				/* _BQC_use_index is 0 will run into if, means level == max_level */
> 
> So, looks the 'level == max_level == 0' when level_old is invalid.
> 
> Just wonder what's defect of BIOS (in _BCL?) causes problem.
> 
> 

Sorry for my misunderstood!

I think that's possible the level_old is 0 and there have a 0 value in
the return package from _BCL. 

Could you please share the _BCL in DSDT from issue machine? Does there
have 0 value in _BCL?


Thanks a lot!
Joey Lee


--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-10-01  8:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01  5:39 [PATCH] acpi: fix brightness level is initialized to zero when BIOS does not restore the brightness value to _BQC Alex Hung
2012-10-01  6:47 ` joeyli
2012-10-01  7:03   ` Alex Hung
2012-10-01  7:17     ` joeyli
2012-10-01  8:34       ` joeyli [this message]
2012-10-01  9:11         ` Alex Hung
2012-10-01  9:19           ` joeyli
2012-10-01 13:36             ` Zhang, Rui
2012-10-01 15:26               ` Alex Hung
2012-10-08  4:34                 ` Zhang, Rui
2012-10-08  4:39                   ` Alex Hung

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=1349080450.24232.35.camel@linux-s257.site \
    --to=jlee@suse.com \
    --cc=alex.hung@canonical.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).