| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | zephyr: pwm: fix init priority | Yuval Peress | 2021-05-02 | 1 | -0/+9 |
| | | | | | | | | | | | | | | | | | | | Currently, the Zephyr pwm drivers were initialized at <PRE_KERNEL_1, KERNEL_INIT_PRIORITY_DEVICE (50)> which is the same priority as the shimmed pwm module. Zephyr does not guarantee any ordering if there's a tie in the priority. I believe that this may be the cause for the black screen after software sync (or at the very least error prone). BRANCH=none BUG=b:186458444 TEST=zmake testall Signed-off-by: Yuval Peress <peress@chromium.org> Change-Id: I63758c6e11bc7b158fa27dd637f88dddd5d162cb Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2855993 Reviewed-by: Keith Short <keithshort@chromium.org> | ||||
| * | zephyr: fix initialization priority to be forward compatible | Yuval Peress | 2021-04-07 | 1 | -0/+17 |
| In upstream Zephyr the initialization of the GPIO module (and most other drivers) was changed. This breaks our gpio and in return also flash initialization. Update both gpio and flash initialization to work with Kconfig and add a compile time validation to be able to catch this sooner in the future. BRANCH=none BUG=none TEST=zmake testall Signed-off-by: Yuval Peress <peress@chromium.org> Change-Id: I44e5867dbf4cb3d5934bf0d0807dcc1aa6c778e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2808335 Reviewed-by: Simon Glass <sjg@chromium.org> | |||||
 |
index : delta/coreboot/chrome-ec.git | |
| review.coreboot.org: chrome-ec.git |
| summaryrefslogtreecommitdiff |