mirror of
https://github.com/Telecominfraproject/OpenCellular.git
synced 2026-01-10 01:21:49 +00:00
64e38af781
No functional changes, just documenting and renaming. All boards which use the PMU must provide pmu_board_init(). This was already true - except that Daisy's pmu_board_init() was implemented as part of pmu_init() instead of its code living in board.c; I've moved the code there now. BUG=chrome-os-partner:18343 BRANCH=none TEST=build all platforms Change-Id: I85ad06dc3b6287ad917fe13acf83182f24a8f23d Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/62906 Reviewed-by: Vic Yang <victoryang@chromium.org>
75 lines
2.3 KiB
Plaintext
75 lines
2.3 KiB
Plaintext
- 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
|
|
=============
|
|
|
|
NOTE: see include/config.h for the current list. The information
|
|
below will be moved there over time.
|
|
|
|
- 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_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.
|
|
|