Created attachment 157611
dmesg on linux-next without quirk showing bug persisting over several suspend cycles
Of the three suspend/resume cycles shown in this dmesg, I trigger the EC bug during the first suspend time.
It comes back with SCI_EVT=1 set the first time, but the 2nd and 3rd resumes do not have this. In a moment I will confirm if this persists across power cycles.
It seems the right behaviour for affected Samsung machines is to send QR_EC until data is 0x00 not just if we get SCI_EVT=1, but additionally on boot or resume.
Created attachment 157611
dmesg on linux-next without quirk showing bug persisting over several suspend cycles
Of the three suspend/resume cycles shown in this dmesg, I trigger the EC bug during the first suspend time.
It comes back with SCI_EVT=1 set the first time, but the 2nd and 3rd resumes do not have this. In a moment I will confirm if this persists across power cycles.
It seems the right behaviour for affected Samsung machines is to send QR_EC until data is 0x00 not just if we get SCI_EVT=1, but additionally on boot or resume.