New issue
Advanced search Search tips

Issue 844657 link

Starred by 2 users
Status: WontFix
Owner:
groeck@chromium.org
Closed: Nov 1
Cc:
cychiang@chromium.org
chromeos-audio-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

chromeos-4.14: clapper: intel_sst_acpi firmware download failure

Project Member Reported by groeck@chromium.org, May 18 2018 
Seen when running chromeos-4.14 on clapper.

018-05-18T20:41:01.278078+00:00 ERR cras_server[1692]: Init chtmax98090: :1,0 failed, rc = -22
2018-05-18T20:41:01.278326+00:00 ERR kernel: [   26.685490] intel_sst_acpi 80860F28:00: wrong ram type0x3 in block0xb
2018-05-18T20:41:01.278340+00:00 ERR kernel: [   26.685503] intel_sst_acpi 80860F28:00: Failed to parse fw
2018-05-18T20:41:01.278350+00:00 ERR kernel: [   26.685534] intel_sst_acpi 80860F28:00: FW download fail -22
2018-05-18T20:41:01.278353+00:00 ERR kernel: [   26.686137]  Audio Port: ASoC: no backend DAIs enabled for Audio Port
2018-05-18T20:41:01.278356+00:00 ERR kernel: [   26.686605]  Audio Port: ASoC: no backend DAIs enabled for Audio Port
2018-05-18T20:41:01.278434+00:00 INFO bluetoothd[2068]: Player registered: sender=:1.18 path=/org/chromium/Cras/Bluetooth/DefaultPlayer
2018-05-18T20:41:01.287322+00:00 INFO kernel: [   26.696846] Bluetooth: sock.c:rfcomm_init_sockets() RFCOMM socket layer initialized
2018-05-18T20:41:01.287349+00:00 INFO kernel: [   26.696878] Bluetooth: core.c:rfcomm_init() RFCOMM ver 1.11
2018-05-18T20:41:01.354968+00:00 ERR mtpd[1622]: LIBMTP_Detect_Raw_Devices failed with 5
2018-05-18T20:41:01.404853+00:00 ERR mtpd[1622]: LIBMTP_Detect_Raw_Devices failed with 5
2018-05-18T20:41:02.092881+00:00 INFO bluetoothd[2068]: adapter /org/bluez/hci0 set power to 1
2018-05-18T20:41:02.279425+00:00 ERR kernel: [   27.688786]  Audio Port: ASoC: no backend DAIs enabled for Audio Port
2018-05-18T20:41:02.279131+00:00 ERR cras_server[1692]: hw_params: Invalid argument: rate: 48000, ret_rate: 48000, channel: 2, format: 2
2018-05-18T20:41:02.279547+00:00 ERR cras_server[1692]: hw_params: Invalid argument: rate: 48000, ret_rate: 48000, channel: 2, format: 2
2018-05-18T20:41:02.279875+00:00 ERR cras_server[1692]: Enable chtmax98090: :1,0 failed, rc = -22
2018-05-18T20:41:02.279893+00:00 ERR cras_server[1692]: Init device retry failed
2018-05-18T20:41:02.280538+00:00 ERR kernel: [   27.689224]  Audio Port: ASoC: no backend DAIs enabled for Audio Port

Comment 1 by groeck@chromium.org, May 18 2018 

On enguarde:

2018-05-18T20:42:04.884477+00:00 INFO kernel: [   31.883184] intel_sst_acpi 80860F28:00: BYT-CR not detected
2018-05-18T20:42:04.884605+00:00 INFO minijail0[1681]: libminijail[1681]: not running init loop, exiting immediately
2018-05-18T20:42:04.885042+00:00 INFO kernel: [   31.884728] intel_sst_acpi 80860F28:00: LPE base: 0xd0400000 size:0x200000
2018-05-18T20:42:04.885058+00:00 INFO kernel: [   31.884738] intel_sst_acpi 80860F28:00: IRAM base: 0xd04c0000
2018-05-18T20:42:04.885061+00:00 INFO kernel: [   31.884792] intel_sst_acpi 80860F28:00: DRAM base: 0xd0500000
2018-05-18T20:42:04.885063+00:00 INFO kernel: [   31.884803] intel_sst_acpi 80860F28:00: SHIM base: 0xd0540000
2018-05-18T20:42:04.885065+00:00 INFO kernel: [   31.884816] intel_sst_acpi 80860F28:00: Mailbox base: 0xd0544000
2018-05-18T20:42:04.885067+00:00 INFO kernel: [   31.884825] intel_sst_acpi 80860F28:00: DDR base: 0x20000000
2018-05-18T20:42:04.892329+00:00 INFO kernel: [   31.891798] intel_sst_acpi 80860F28:00: Got drv data max stream 25
2018-05-18T20:42:04.923045+00:00 ERR kernel: [   31.922908] intel_sst_acpi 80860F28:00: wrong ram type0x3 in block0xb
2018-05-18T20:42:04.923071+00:00 ERR kernel: [   31.922920] intel_sst_acpi 80860F28:00: Failed to parse fw

Comment 2 by groeck@chromium.org, May 25 2018 

The system laods firmware with sound/soc/intel/atom/sst/sst_loader.c. The problem is introduced with "UPSTREAM: ASoC: Intel: atom: use cht_bsw_max98090 for Baytrail Chromebooks", which switches the driver from byt-max98090 and also switches the firmware load procedure. 

Also see the following commits into chromeos-4.4, explaining at least part of the mystery.
73103f861a37 CHROMIUM: Revert "UPSTREAM: ASoC: Intel: sst: only select sst-firmware when DW DMAC is built-in"
6b32ffc2215a CHROMIUM: Revert "UPSTREAM: ASoC: Intel: Load the atom DPCM driver only"

I don't know at this time if an upstream based single-image solution (without revert) is available.

Comment 3 by groeck@chromium.org, Nov 1

Status: WontFix (was: Assigned)
Irrelevant; clapper or enguarge will never run chromeos-4.14.
►

Sign in to add a comment