All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Burian <michael.burian@sbg.at>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: No backlight since linux-4.2.4 - drivers/gpu/drm/radeon/atombios_encoders.c
Date: Tue, 27 Oct 2015 11:06:39 +0100	[thread overview]
Message-ID: <562F4CAF.1050505@sbg.at> (raw)
In-Reply-To: <562F411A.60906@daenzer.net>

On 10/27/15 10:17, Michel Dänzer wrote:
> 
> I'm not familiar with the ATOM bytecode, but since the number of
> bytecode instructions executed seems the same in both cases, I suspect
> that dig->backlight_level == 0 => ATOM_LCD_BLOFF is executed. (The
> debugging output in my patch would have provided all of this information
> and more, but there wasn't any of it in the dmesg you provided)
> 
> I guess the question then becomes how dig->backlight_level is (supposed
> to be) initialized.
> 
> What values do the following files contain in the broken and working cases?
> 
> /sys/class/backlight/radeon_bl0/bl_power
> /sys/class/backlight/radeon_bl0/brightness
> /sys/class/backlight/radeon_bl0/actual_brightness
> /sys/class/backlight/radeon_bl0/max_brightness
> 
> 

These files do not exist on my system,
I can offer /sys/class/backlight/acpi_video0/

content is identical in both cases

bl_power        0
brightness      10
actual_brightness       10
max_brightness  10


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-10-27 10:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <562BDB47.5000301@sbg.at>
2015-10-26  9:32 ` No backlight since linux-4.2.4 - drivers/gpu/drm/radeon/atombios_encoders.c Michel Dänzer
2015-10-26 21:21   ` Alex Deucher
     [not found]   ` <562E0473.5060404@sbg.at>
2015-10-27  2:36     ` Michel Dänzer
2015-10-27  8:44       ` Michael Burian
2015-10-27  9:17         ` Michel Dänzer
2015-10-27 10:06           ` Michael Burian [this message]
2015-10-27 15:10             ` Alex Deucher
2015-10-27 16:23               ` Michael Burian
2015-10-27 16:43                 ` Alex Deucher
2015-10-27 17:02                   ` Michael Burian
2015-10-28  7:11                   ` Michel Dänzer
2015-10-28 19:03                     ` Alex Deucher
2015-10-28 20:46                       ` Michael Burian
2015-10-29  3:18                       ` Michel Dänzer

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=562F4CAF.1050505@sbg.at \
    --to=michael.burian@sbg.at \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michel@daenzer.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 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.