From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 98677] New: [NVAC] iMac9, 1 effective backlight brightness range changes after S3
Date: Thu, 10 Nov 2016 17:33:18 +0000 [thread overview]
Message-ID: <bug-98677-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2752 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98677
Bug ID: 98677
Summary: [NVAC] iMac9,1 effective backlight brightness range
changes after S3
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: jefferym-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 127900
--> https://bugs.freedesktop.org/attachment.cgi?id=127900&action=edit
dmesg output after the resume with some nouveau trace options
I have an iMac 9,1 where the behaviour of the backlight of the built in screen
works differently between the first boot and after a suspend to ram.
It appears to be darker at lower values before a suspend than after.
kernel: 4.8.6-300.fc25.x86_64
lspci adapter: VGA adapter NVIDIA Corporation C79 [GeForce 9400] [10de:0867]
DMI: Apple Inc. iMac9,1/Mac-F2218EA9
I've been booting in EFI mode.
I do not know of a regression. I've only tried 4.4 and this 4.8 kernels.
I've observed this with X running but I've been testing this without starting a
graphical environment.
I've been testing by setting setting backlight values via the
/sys/backlight/nv_backlight/brightness interface.
Before a suspend I can set values such as 40, 70, 100 and the brightness seems
to be reasonable on the screen.
I then suspend to ram via the /sys/power/state interface.
Upon resuming the backlight appears to be at 100 percent. If I set the
brightness to values such as 30 and 60 the screen remains dark. It is barely
visible as a flicker at 70. At 100 it is visible.
I've observed that the value of NV50_PDISP_SOR_PWM_DIV (0x0061c080) is 0x1
after a boot but is set to 0x84 after a resume.
It appears there's an init script in the bios dump which sets it to the value
of 0x84. I have confirmed if I use the nouveau option
nouveau.config=NvForcePost=1 that the behavior after booting is the same as
after a resume. The value of 0x61c080 is 0x84.
If I `nvapoke 0x061c080 0x1` after a resume the backlight seems to work fairly
well. I created patch to test this. I expect it isn't the proper solution.
I'm attaching the dmesg which includes a resume with the nouveau driver.
I'll also attach the vbios dump, acpidump, dmidecode, lspci,
I've gathered an mmiotrace of the binary driver as it sets a few brightness
values as well.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4252 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2016-11-10 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 17:33 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-98677-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-11-10 17:35 ` [Bug 98677] [NVAC] iMac9, 1 effective backlight brightness range changes after S3 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 17:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 17:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 17:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 17:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 17:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 17:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-10 21:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-11 22:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-11 22:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-11-12 1:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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=bug-98677-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.