Hi, Daniel > From: Daniel Drake [mailto:drake@xxxxxxxxxxxx] > Subject: Re: [PATCH] ACPI / EC: handle ECDT EC and DSDT EC simultaneously > > Hi Lv, > > On Fri, Apr 28, 2017 at 6:52 AM, Daniel Drake <drake@xxxxxxxxxxxx> wrote: > > In the DSDT you were looking at the H_EC device, but for whatever > > reason, there are two ECs in this DSDT and the one that Linux picks up > > is the 2nd one, \_SB_.PCI0.LPCB.EC0. > > > > This device has no _STA but does have valid _CRS, and the debug patch > > results agree: > > > > ACPI : EC: acpi_ec_dsdt_probe: search for DSDT EC > > ACPI : EC: ec_parse_device: _STA status 5 val 0 > > ACPI : EC: ec_parse_device: _CRS status 0 command 66 data 62 > > ACPI : EC: EC stopped > > ACPI : EC: EC started > > ACPI: \_SB_.PCI0.LPCB.EC0_: Used as first EC > > How do we proceed here? Any other options we can try that don't > involve DMI quirking? Quirk seems to be required: 1. We do not know the order windows invokes _INI/_STA, there are several possible solutions 1. EC opregion handler is installed when EC device is enumerated. Before that, just complains errors. 2. EC opregion access triggers Linux to probe EC device driver. We have tried 1, and as I mentioned before, someone reported a regression for the new errors. 2 also looked scary, as EC._STA may still contain BIOS provided initialization code that cannot be invoked such earlier. 2. Even the above one doesn't matter (for example, 2 is working for all platforms), Linux still don't know the preference of the GPE settings. Maybe I could help to present some demo code. Let's file a kernel Bugzilla entry to work on this issue together: https://bugzilla.kernel.org/show_bug.cgi?id=195651 Thanks and best regards Lv > > Thanks > Daniel ��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
