Home
last modified time | relevance | path

Searched +full:psoc6 +full:- +full:intmux (Results 1 – 3 of 3) sorted by relevance

/Zephyr-latest/dts/arm/infineon/cat1a/legacy/
Dpsoc6_cm0.dtsi4 * SPDX-License-Identifier: Apache-2.0
7 #include <arm/armv6-m.dtsi>
8 #include <infineon/cat1a/legacy/psoc6.dtsi>
13 compatible = "arm,cortex-m0+";
16 /delete-node/ cpu@1;
20 intmux: intmux@40210020 { label
21 /* see cypress,psoc6-int-mux.yaml */
22 compatible = "cypress,psoc6-intmux";
26 #address-cells = <1>;
27 #size-cells = <1>;
[all …]
/Zephyr-latest/dts/bindings/interrupt-controller/
Dcypress,psoc6-intmux-ch.yaml3 # SPDX-License-Identifier: Apache-2.0
8 see cypress,psoc6-intmux
10 compatible: "cypress,psoc6-intmux-ch"
12 include: [interrupt-controller.yaml, base.yaml]
21 interrupt-cells:
22 - irq
23 - priority
Dcypress,psoc6-intmux.yaml3 # SPDX-License-Identifier: Apache-2.0
8 The PSOC 6 Cortex-M0+ NVIC can handle up to 32 interrupts. This means that
10 to be processed in the Cortex-M0+ CPU.
12 At CPU Sub System (CPUSS) there are 8 special registers (intmux[0~7]) to
13 configure the 32 NVIC lines for Cortex-M0+ CPU. Each register handles up to
14 4 interrupt sources by grouping intmux channels. These means that each byte
15 from intmux[0~7] store a 'vector number' which selects the peripheral
17 Cortex-M0+ NVIC controller. Note that Cortex-M4 have all interrupt sources
21 configuration and how the Cortex-M0+ NVIC sources are organized. Each
22 channel chX represents a Cortex-M0+ NVIC line and it stores a vector number.
[all …]