Intel internal test shows this:
kernel: [ 9610.645108] rt715 sdw:3:25d:715:0: [rt715_sdw_write] 3124 <= 0004
kernel: [ 9610.645238] rt715 sdw:3:25d:715:0: [rt715_sdw_write] 3125 <= 0005
kernel: [ 9610.840387] rt711 sdw:0:25d:711:0: Slave impl defined interrupt
kernel: [ 9610.840391] rt711 sdw:0:25d:711:0: rt711_interrupt_callback control_port_stat=4
kernel: [ 9611.092971] rt711 sdw:0:25d:711:0: [rt711_sdw_read] b921 0000 => 80000000
kernel: [ 9611.093470] rt711 sdw:0:25d:711:0: [rt711_sdw_read] 7520 85a0 9c20 aca0 => 00000af4
kernel: [ 9611.093991] rt711 sdw:0:25d:711:0: [rt711_sdw_read] 7520 85a0 9c20 aca0 => 00000800
kernel: [ 9611.094493] rt711 sdw:0:25d:711:0: [rt711_sdw_read] 7520 85a0 9c20 aca0 => 00000030
kernel: [ 9611.094495] rt711 sdw:0:25d:711:0: in rt711_jack_detect_handler, jack_type=0x3
kernel: [ 9611.094496] rt711 sdw:0:25d:711:0: in rt711_jack_detect_handler, btn_type=0x0
kernel: [ 9611.140187] sof-audio-pci 0000:00:1f.3: ipc rx: 0x90020000: GLB_TRACE_MSG
kernel: [ 9611.140207] sof-audio-pci 0000:00:1f.3: ipc rx done: 0x90020000: GLB_TRACE_MSG
kernel: [ 9611.640140] sof-audio-pci 0000:00:1f.3: ipc rx: 0x90020000: GLB_TRACE_MSG
kernel: [ 9611.640161] sof-audio-pci 0000:00:1f.3: ipc rx done: 0x90020000: GLB_TRACE_MSG
kernel: [ 9613.236847] intel-sdw intel-sdw.2: Msg ignored for Slave 15
kernel: [ 9613.236850] soundwire sdw-master-2: ClockStopNow Broadcast msg ignored -61
kernel: [ 9613.875333] intel-sdw intel-sdw.3: Msg ignored for Slave 1
kernel: [ 9613.875336] rt715 sdw:3:25d:715:0: Clock Stop prepare failed for slave: -61
kernel: [ 9613.875340] rt715 sdw:3:25d:715:0: pre-prepare failed:-61
kernel: [ 9613.875342] intel-sdw intel-sdw.3: prepare clock stop failed -61
kernel: [ 9613.875344] intel-sdw intel-sdw.3: cannot enable clock stop on suspend
dmesg_rt715_clock_stop_error.txt
@jack-cy-yu do you see any control value or writes that would cause the device to reply COMMAND_IGNORED?
Intel internal test shows this:
dmesg_rt715_clock_stop_error.txt
@jack-cy-yu do you see any control value or writes that would cause the device to reply COMMAND_IGNORED?