Jaroslav Kysela

Original Jablotron O-link software. I was lucky - I found and disassembled this checksum code. Looking to your implementation, it is not perfect (seems just "guessing" on some lines).

Thank you for the clarification. The _getting started_ guide use `load` + `reset init` sequences which works only for the flash programs. The RAM loading / booting requires the `reset...

It seems that `monitor reset init` and `monitor reset halt` do both the right job. The only difference is initial PC address (0xf0 or 0x2700). The order of `monitor reset`...

It looks like a bug. Could you show the plugin chain (using `snd_pcm_dump` or so) ? Or are you using direct `hw:X` device?

There should be more information (lines after `Slave:`).

So it's basically equivalent to `hw:X` device so it appears like a kernel issue, but the kernel changes the trigger tstamp only if the state changes. It may be possible...

Is trigger timestamp identical before and after drop?

I'd like to keep this open until resolved.

Latched timestamps were added in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2b79d7a6bf341ebeffb85fc2b3577d0cfa810c49 . Just fix the trigger callback in hda_controller.c.

Please, sent a proposed commit with a good description to [email protected] mailing list with Cc to all relevant maintainers of affected drivers (including sound/soc/intel tree). Here is not a right...