Alex,
I got some reply, please let me know if you have other questions:
1. On burst timeout:
A: the driver should send optional ACPI Normal mode (Disable burst) command and then send the burst enable command followed by the read/write
2. if burst timeout, does EC firmware abort current read/write transaction?
A: Yes. If the timeout occurs before KSC receives the command and all the data bytes, EC aborts the transaction and goes back to normal mode.
3. what's the difference between burst mode and non-burst mode from the EC firmware point of view?
A: In burst mode, EC goes into a special mode where it disables interrupts and running all the tasks except responding to OSPM commands.
4. EC doesn't allow us to clean up GPE status bit, as soon as we set enable bit (at the end of interrupt handler), it fires new interrupt, how to avoid such case? We saw EC interrupt storm in a lot of systems.
A: EC generates SCI for every OBF or IBF. It also generates SCI even when EC disengage the burst. The driver should check the BURST_MODE bit in STATUS register on every SCI to see if it is in burst mode or not.
��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
