diff options
| author | Takashi Iwai <tiwai@suse.de> | 2016-04-17 09:39:41 +0200 |
|---|---|---|
| committer | Takashi Iwai <tiwai@suse.de> | 2016-04-17 09:39:41 +0200 |
| commit | 50fd4987c4f3c3ebf0ce94d932732011bbdc7c71 (patch) | |
| tree | 104aebcb7c9bb293fdf1aa0c38ddf4da1c871455 /tools/perf/scripts/python/bin | |
| parent | c44da62b55bb453052869ab095bcda7aa0bd6bba (diff) | |
| download | kernel-50fd4987c4f3c3ebf0ce94d932732011bbdc7c71.tar.gz | |
ALSA: hda - Don't trust the reported actual power state
We've got a regression report that the recording on Mac with a cirrus
codec doesn't work any longer. This turned out to be the missing
power up to D0 by power_save_node enablement.
After analyzing the traces, we found out that the culprit is that the
codec advertises the "actual" power state of a few nodes to be D0
while the "target" power state is D3. This inconsistency is usually
OK, as it implies the power transition. But in the case of cirrus
codec, this seems to be stuck to D3 while it's not actually D0.
This patch addresses the issue by checking the power state difference
more strictly. It sends the power-state change verb unless both the
target and the actual power states show the given value.
We may introduce yet another flag indicating the possible broken
hardware power state, but it's anyway safer to set the proper power
state even in a transition (at least it's harmless as long as the
target state is same). So this simpler change was applied now.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=116171
Cc: <stable@vger.kernel.org> # v4.4+
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions