diff options
| author | Mark Brown <broonie@kernel.org> | 2026-07-31 20:32:27 +0100 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2026-07-31 20:32:27 +0100 |
| commit | 13dd6c1f73104512550e681df06e6912020c338b (patch) | |
| tree | 215163e90fc63c79d0ed3f62ffa3d0ef1c66e7a1 /tools/perf/scripts/python/flamegraph.py | |
| parent | 8338deeb8fc28925257a9a3bfad1dc78c8d74cef (diff) | |
| parent | 31fd7a0bbfa4b7e8aff11f278e817664c6a5f68b (diff) | |
ASoC: SOF: Intel: hda/mtl: Handle powered on DSP on boot
Peter Ujfalusi <peter.ujfalusi@linux.intel.com> says:
It is expected that the DSP is in power down state when the firmware boot
is attempted.
If the DSP for any reason was left powered up then the DSP boot will
fail since the ROM boot sequence might not be able to run.
Make sure that the DSP is off before proceeding to boot it up.
We have seen reports that for some undetermined reasons the DSP was on
during system boot and this caused firmware boot failure as the DSP
cannot be booted up - it was already in booted up state.
Link: https://patch.msgid.link/20260730122857.5294-1-peter.ujfalusi@linux.intel.com
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions