diff options
author | Takashi Iwai <tiwai@suse.de> | 2013-04-04 15:35:24 +0200 |
---|---|---|
committer | Takashi Iwai <tiwai@suse.de> | 2013-04-04 15:35:39 +0200 |
commit | 8fc24426f15d967d585af7062b7be3c46bbce571 (patch) | |
tree | ae99f026484bbd912abfed8fb5e565f5a3a7a900 /Documentation/fb/intel810.txt | |
parent | ALSA: hda - fix typo in proc output (diff) | |
download | linux-8fc24426f15d967d585af7062b7be3c46bbce571.tar.xz linux-8fc24426f15d967d585af7062b7be3c46bbce571.zip |
Revert "ALSA: hda - Allow power_save_controller option override DCAPS"
This reverts commit 6ab317419c62850a71e2adfd1573e5ee87d8774f.
The commit [6ab317419c: ALSA: hda - Allow power_save_controller option
override DCAPS] changed the behavior of power_save_controller so that
it can override the driver capability. This assumed that this option
is rarely changed dynamically unlike power_save option. Too naive.
It turned out that the user-space power-management tool tries to set
power_save_controller option to 1 together with power_save option
without knowing what's actually doing. This enabled forcibly the
runtime PM of the controller, which is known to be broken om many
chips thus disabled as default.
So, the only sane fix is to revert this commit again. It was intended
to ease debugging/testing for runtime PM enablement, but obviously we
need another way for it.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=56171
Reported-and-tested-by: Nikita Tsukanov <keks9n@gmail.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'Documentation/fb/intel810.txt')
0 files changed, 0 insertions, 0 deletions