mirror of
https://github.com/Telecominfraproject/OpenCellular.git
synced 2025-12-30 18:41:11 +00:00
a77d59b19a
For legacy issue, the keyboard controller defaults to turn on XLATE (translate) bit (which means EC generates scan codeset 1 althought it internally supports codeset 2). In normal case, the BIOS/OS would clear the XLATE bit to ask EC to generate codeset 2. However, when EC jumps happens, the internal keyboard state doesn't know this and always reset XLATE as on. This makes the EC generate garbage to OS. So, this patch fixes would clear the XLATE if the EC reboot is a warmboot based on the assumption that moderm OSes clear the XLATE bit. BUG=chrome-os-partner:9102 TEST=on link % ectool reboot_ec A (from r438 to r438) Expect keyboard is hang (r438 is still buggy) % chromeos-firmwareupdater --mode=recovery Expect fail at gec_need_2nd_pass() % ectool reboot_ec RO Keyboard is still working! Bug fixed! % ectool reboot_ec RO Again. Still working. Change-Id: If47bd8d7bbbb03b810d3b464ba3d92f8ff548237
- EC Lib
This wraps Blizzard driverlib and implements the EC chip interface defined
by Google. See below diagram for architecture.
+--------------------+
| Host BIOS/OS |
+--------------------+
---- host interface ----
+--------------------+
| Google EC features |
+--------------------+
---- chip interface ---- The interface is defined in
src/platform/ec/chip_interface/*.
+--------------------+ But the real implementation is in EC Lib.
| EC Lib |
+--------------------+
| Blizzard low level |
| driver, the |
| driverlib. |
+--------------------+