Vincent Palatin 24beb9976a do not store the keyboard state on the stack
As our stack for the keyboard scanning task might be small (256 bytes on
STM32), we store the full keyboard state in a global instead of the
stack to avoid consuming 16 bytes there.

Signed-off-by: Vincent Palatin <vpalatin@chromium.org>

BRANCH=none
BUG=chrome-os-partner:19389
TEST=run on Spring with CONFIG_OVERFLOW_DETECT and see that the KEYSCAN task
is now consuming 248 bytes of stack instead of 264.

Change-Id: I2dd7815f36e6807e7b9e88d59f8fd8a14b1988ab
Reviewed-on: https://gerrit.chromium.org/gerrit/51028
Reviewed-by: Vic Yang <victoryang@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Queue: Vincent Palatin <vpalatin@chromium.org>
Tested-by: Vincent Palatin <vpalatin@chromium.org>
2013-05-14 10:17:13 -07:00
2013-05-14 08:35:16 -07:00
2013-05-14 09:25:03 -07:00
2013-05-14 09:25:03 -07:00
2013-05-14 09:25:03 -07:00
2013-05-14 09:24:59 -07:00
2013-04-29 23:31:28 -07:00
2012-05-11 09:11:52 -07:00
2013-04-29 03:47:50 -07:00
2013-05-14 00:31:40 -07:00
2011-12-08 19:18:06 +00:00
2013-04-05 14:28:42 -07:00

- 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.       |
  +--------------------+


Build Options
=============

- CONFIG_WATCHDOG_HELP

	Try to detect a watchdog that is about to fire, and print a trace.
	This is needed on STM32, where the independent watchdog has no early
	warning feature and the windowed watchdog has a very short period.

- CONFIG_PANIC_HELP

	Report extra information about a panic, such as the fault address,
	here shown as bfar. This shows the reason for the fault and may help
	to determine the cause.

	=== EXCEPTION: 03 ====== xPSR: 01000000 ===========
	r0 :0000000b r1 :00000047 r2 :60000000 r3 :200013dd
	r4 :00000000 r5 :080053f4 r6 :200013d0 r7 :00000002
	r8 :00000000 r9 :200013de r10:00000000 r11:00000000
	r12:00000000 sp :200009a0 lr :08002b85 pc :08003a8a
	Precise data bus error, Forced hard fault, Vector catch, bfar = 60000000
	mmfs = 00008200, shcsr = 00000000, hfsr = 40000000, dfsr = 00000008

- CONFIG_ASSERT_HELP

	Report assertion failures in a vebose manner to aid debugging. When
	enabled an ASSERT() which fails will produce message in the form:

		ASSERTION FAILURE '<expr>' in function() at file:line

- CONFIG_AC_POWER_STATUS

	Monitor the state of the AC power input and drive out a GPIO to
	the AP indicating this state. The GPIO will be driven low when
	AC power is not connected, and high when it is connected. This
	uses GPIO_AC_STATUS for this purpose.

- CONFIG_PMU_FORCE_FET

	Force switching on and off the FETs on the PMU controlling various
	power rails during AP startup and shutdown sequences.
	This is mainly useful for bringup when we don't have the corresponding
	sequences in the AP code.

- CONFIG_KEYBOARD_TEST

	Turn on keyboard testing functionality. This enables a message which
	received a list of keyscan events from the AP and processes them.
	This will cause keypresses to appear on the AP through the same
	mechanism as a normal keyboard press.

Description
No description provided
Readme 1.4 GiB
Languages
C 64.7%
Lasso 20.7%
ASL 3.6%
JavaScript 3.2%
C# 2.9%
Other 4.6%