zephyr/dts/bindings/interrupt-controller/openisa,rv32m1-intmux-ch.yaml

# Copyright (c) 2019, Linaro Limited
# SPDX-License-Identifier: Apache-2.0

description: RV32M1 INTMUX channel

compatible: "openisa,rv32m1-intmux-ch"

include: [interrupt-controller.yaml, base.yaml]

properties:
  reg:
    required: true

  interrupts:
    required: true

interrupt-cells:
  - irq
dts: rv32m1: Rework interrupt mux dts descriptions Each intmux block acts like 8 interrupt controllers in which we can have multiple device interrupts on a single channel and that channel than interrupt than chained to another interrupt controller (in the case of the RISC-V cores, it is the event unit). So to describe things better to properly be able to walk the interrupt chain in the device tree we treat each channel in the interrupt mux as an interrupt controller rather than the intmux as a single interrupt controller. In the future this will allow the device tree generation code to walk the interrupt chain from the device and up through any interrupt controllers to generate the IRQ value that Zephyr expects (rather than us hard coding this into the DTS). Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-08-08 21:30:08 +02:00			`# Copyright (c) 2019, Linaro Limited`
			`# SPDX-License-Identifier: Apache-2.0`

dts: bindings: Remove 'title:' and put all info. into 'description:' Add any useful information from 'title:' to the 'description:' strings (e.g. explanations of acronyms), and remove 'title:' as well as any copy-pasted "this binding gives a ..." boilerplate. Also clean some description strings up a bit. Some other things could probably be cleaned up (replacing 'GPIO node' with 'GPIO controller' on controllers for consistency, for example), but I kept things close to the original to avoid accidentally messing up. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-11-19 08:39:11 +01:00			`description: RV32M1 INTMUX channel`
dts: rv32m1: Rework interrupt mux dts descriptions Each intmux block acts like 8 interrupt controllers in which we can have multiple device interrupts on a single channel and that channel than interrupt than chained to another interrupt controller (in the case of the RISC-V cores, it is the event unit). So to describe things better to properly be able to walk the interrupt chain in the device tree we treat each channel in the interrupt mux as an interrupt controller rather than the intmux as a single interrupt controller. In the future this will allow the device tree generation code to walk the interrupt chain from the device and up through any interrupt controllers to generate the IRQ value that Zephyr expects (rather than us hard coding this into the DTS). Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-08-08 21:30:08 +02:00
			`compatible: "openisa,rv32m1-intmux-ch"`

			`include: [interrupt-controller.yaml, base.yaml]`

			`properties:`
			`reg:`
yamllint: indentation: fix dts/bindings/ Fix the YAML files indentation for files in dts/bindings/. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com> 2023-01-03 20:21:25 +01:00			`required: true`
dts: rv32m1: Rework interrupt mux dts descriptions Each intmux block acts like 8 interrupt controllers in which we can have multiple device interrupts on a single channel and that channel than interrupt than chained to another interrupt controller (in the case of the RISC-V cores, it is the event unit). So to describe things better to properly be able to walk the interrupt chain in the device tree we treat each channel in the interrupt mux as an interrupt controller rather than the intmux as a single interrupt controller. In the future this will allow the device tree generation code to walk the interrupt chain from the device and up through any interrupt controllers to generate the IRQ value that Zephyr expects (rather than us hard coding this into the DTS). Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-08-08 21:30:08 +02:00
			`interrupts:`
yamllint: indentation: fix dts/bindings/ Fix the YAML files indentation for files in dts/bindings/. Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com> 2023-01-03 20:21:25 +01:00			`required: true`
dts: rv32m1: Rework interrupt mux dts descriptions Each intmux block acts like 8 interrupt controllers in which we can have multiple device interrupts on a single channel and that channel than interrupt than chained to another interrupt controller (in the case of the RISC-V cores, it is the event unit). So to describe things better to properly be able to walk the interrupt chain in the device tree we treat each channel in the interrupt mux as an interrupt controller rather than the intmux as a single interrupt controller. In the future this will allow the device tree generation code to walk the interrupt chain from the device and up through any interrupt controllers to generate the IRQ value that Zephyr expects (rather than us hard coding this into the DTS). Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-08-08 21:30:08 +02:00
scripts: dts: Generalize '#cells' to allow multiple sources Implement a nice generalization suggested by Bobby Noelte. Instead of having a generic #cells key in bindings, have source-specific -cells keys. Some examples: interrupt-cells: - irq - priority - flags gpio-cells: - pin - flags pwm-cells: - channel - period This makes bindings a bit easier to read, and allows a node to be a controller for many different 'phandle-array' properties. The prefix before -cells is derived from the property name, meaning there's no fixed set of *-cells keys. This is possible because of the earlier 'phandle-array' generalization. The older #cells key is supported for backwards compatibility, but generates a deprecation warning. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-09-26 20:34:13 +02:00			`interrupt-cells:`
dts: rv32m1: Rework interrupt mux dts descriptions Each intmux block acts like 8 interrupt controllers in which we can have multiple device interrupts on a single channel and that channel than interrupt than chained to another interrupt controller (in the case of the RISC-V cores, it is the event unit). So to describe things better to properly be able to walk the interrupt chain in the device tree we treat each channel in the interrupt mux as an interrupt controller rather than the intmux as a single interrupt controller. In the future this will allow the device tree generation code to walk the interrupt chain from the device and up through any interrupt controllers to generate the IRQ value that Zephyr expects (rather than us hard coding this into the DTS). Signed-off-by: Kumar Gala <kumar.gala@linaro.org> 2019-08-08 21:30:08 +02:00			`- irq`