From: Aaron Lu <aaron.lu@intel.com>
To: John Marsden <john.d.marsden@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: PROBLEM: [Toshiba Portege Z835] Brightness control lost after suspend
Date: Wed, 30 Jul 2014 16:32:48 +0800 [thread overview]
Message-ID: <20140730083248.GA31763@aaronlu.sh.intel.com> (raw)
In-Reply-To: <CACiopZCQpGeBw6V7qFpcV6u22stOQC8X9Aiwya3wE_cBZzL+PQ@mail.gmail.com>
On Tue, Jul 29, 2014 at 07:20:59PM +0100, John Marsden wrote:
> On 29 July 2014 15:28, Aaron Lu <aaron.lu@intel.com> wrote:
> > Please attach acpidump to the Ubuntu bug page.
>
> I installed acpidump from the Ubuntu Software Centre and tried running
> it with the following result:
> sudo acpidump -z
>
> Intel ACPI Component Architecture
> ACPI Binary Table Dump Utility version 20140214-64 [Mar 29 2014]
> Copyright (c) 2000 - 2014 Intel Corporation
>
> Cannot map /dev/mem
> Could not map table at 0x00000000000F0030 length FEDA0000
> Could not get ACPI tables, AE_ACCESS
Hmm, no idea why this occured.
The acpidump utility is available in the kernel tree:
linux/tools/power/acpi
>
> I'm out of my depth with this. However, with Google's help I found
> https://www.kernel.org/doc/Documentation/acpi/initrd_table_override.txt
> at the end of which it says:
> "Alternatively, used ACPI tables can be retrieved via sysfs in latest
> kernels: /sys/firmware/acpi/tables"
> Using this hint I've saved the binary files from sysfs and then used
> "acpidump -f filename" to create the file I've uploaded to the Ubuntu
> bug. Please advise if I need to follow some other procedure to get
> what you want.
It works, thanks.
>
> > BTW, do you always have this problem or it starts to occur
> > from some kernel version?
>
> While triaging the bug on Ubuntu we've gone as far back as Ubuntu
> 12.04.0 (Precise) which is what I first installed on the computer in
> question. It's been present in all versions we tested.
>
> > Please also list your /sys/class/backlight with v3.16-rc kernel.
> I trust this is what you require:
>
> ls -l /sys/class/backlight
> total 0
> lrwxrwxrwx 1 root root 0 Jul 29 17:06 acpi_video0 ->
> ../../devices/pci0000:00/0000:00:02.0/backlight/acpi_video0
> lrwxrwxrwx 1 root root 0 Jul 29 17:06 intel_backlight ->
> ../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/intel_backlight
> lrwxrwxrwx 1 root root 0 Jul 29 17:06 toshiba ->
> ../../devices/LNXSYSTM:00/LNXSYBUS:00/TOS6208:00/backlight/toshiba
>
> /sys/class/backlight/acpi_video0/* {cat or ls -l}
> actual_brightness: 7
> bl_power: 0
> brightness: 7
> device -> ../../../0000:00:02.0
> max_brightness: 7
> power/async: disabled
> power/autosuspend_delay_ms - Input/output error
> power/control: auto
> power/runtime_active_kids: 0
> power/runtime_active_time: 0
> power/runtime_enabled: disabled
> power/runtime_status: unsupported
> power/runtime_suspended_time: 0
> power/runtime_usage: 0
> subsystem -> ../../../../../class/backlight
> type: firmware
> uevent:
>
> /sys/class/backlight/intel_backlight/* {cat or ls -l}
> actual_brightness: 249
> bl_power: 0
> brightness: 249
> device -> ../../card0-LVDS-1
> max_brightness: 4539
> power/async: disabled
> power/autosuspend_delay_ms - Input/output error
> power/control: auto
> power/runtime_active_kids: 0
> power/runtime_active_time: 0
> power/runtime_enabled: disabled
> power/runtime_status: unsupported
> power/runtime_suspended_time: 0
> power/runtime_usage: 0
> subsystem -> ../../../../../../../class/backlight
> type: raw
> uevent:
>
> /sys/class/backlight/toshiba/* {cat or ls -l}
> actual_brightness: 7
> bl_power: 0
> brightness: 7
> device -> ../../../TOS6208:00
> max_brightness: 7
> power/async: disabled
> power/autosuspend_delay_ms - Input/output error
> power/control: auto
> power/runtime_active_kids: 0
> power/runtime_active_time: 0
> power/runtime_enabled: disabled
> power/runtime_status: unsupported
> power/runtime_suspended_time: 0
> power/runtime_usage: 0
> subsystem -> ../../../../../../class/backlight
> type: platform
> uevent:
>
>
> Thank you for your help. John
You are welcome.
I checked the dsdt table, the ACPI backlight interface makes use of SMI
to do the backlight control(because of the 0xb2 io port write). It's
beyond our control so I don't know how to fix the problem.
Does the other interface work after resume? I mean the intel_backlight
and the toshiba one?
Thanks,
Aaron
next prev parent reply other threads:[~2014-07-30 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 20:52 PROBLEM: [Toshiba Portege Z835] Brightness control lost after suspend John Marsden
2014-07-29 14:28 ` Aaron Lu
2014-07-29 18:20 ` John Marsden
2014-07-30 8:32 ` Aaron Lu [this message]
2014-07-30 17:11 ` John Marsden
2014-07-31 8:09 ` Aaron Lu
2014-07-31 21:05 ` John Marsden
2014-08-01 2:42 ` Aaron Lu
2014-08-04 20:32 ` John Marsden
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=20140730083248.GA31763@aaronlu.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=john.d.marsden@gmail.com \
--cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox