zara/zephyr - zephyr - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Jun Lin	0bf4ec6d7b	drivers: gpio: npcx: workaround both trigger issue for npcx9m7fb Apply the workaround for the issue "MIWU Any Edge Trigger Condition" in the NPCX99nFB_Errata. Signed-off-by: Jun Lin <CHLin56@nuvoton.com>	1 year ago
Kumar Gala	8423f23b9c	drivers: intc: Update drivers to use devicetree Kconfig symbol Update intc drivers to use DT_HAS_<compat>_ENABLED Kconfig symbol to expose the driver and enable it by default based on devicetree. We remove 'depend on' Kconfig for symbols that would be implied by the devicetree node existing. Signed-off-by: Kumar Gala <galak@kernel.org>	3 years ago
Nazar Kazakov	9713f0d47c	everywhere: fix typos Fix a lot of typos Signed-off-by: Nazar Kazakov <nazar.kazakov.work@gmail.com>	3 years ago
Mulin Chao	14b98135fd	driver: npcx7: fixed typo in Kconfig.npcx files. Fixed typo in Kconfig.npcx files. Signed-off-by: Mulin Chao <mlchao@nuvoton.com>	5 years ago
Mulin Chao	84d90e456a	driver: intc: add MIWU driver support in NPCX series. The device Multi-Input Wake-Up Unit (MIWU) supports the embedded controller (EC) to exit 'Sleep' or 'Deep Sleep' power state which allows chip has better power consumption. Also, it provides signal conditioning such as 'Level' and 'Edge' trigger type and grouping of external interrupt sources of NVIC. The NPCX series has three identical MIWU modules: MIWU0, MIWU1, MIWU2. Together, they support a total of over 140 internal and/or external wake-up sources. In this CL, we use device tree files to present the relationship bewteen MIWU and the other devices in different npcx series. For npcx7 series, it include: 1. npcx7-miwus-int-map.dtsi: it presents relationship between MIWU group and NVIC interrupt in npcx7. Please notice it isn't 1-to-1 mapping. 2. npcx7-miwus-wui-map.dtsi: it presents relationship between input of MIWU and its source device such as gpio, timer, eSPI VWs and so on. This CL also includes: 1. Add MIWU device tree declarations. 2. MIWU api function declarations and implementation to configure signal conditions and callback function mechanism. They can be be classified into two types. One is for GPIO which connects original gpio callback implemetation and the other is for generic devices such as timer, eSPI, and so on. Signed-off-by: Mulin Chao <MLChao@nuvoton.com>	5 years ago