st,stm32u5-dma
Description
These nodes are “dma” bus nodes.
STM32U5 DMA controller
LPDMA/GPDMA/HPDMA direct memory access controllers; first found in STM32U5.
These DMA controllers contain various channels as well as a request multiplexer
that allows any of the DMA request lines to trigger an arbitrary channel, in a
similar fashion to the combined (DMA1/DMA2)+DMAMUX found in some STM32 series.
The DMA cells are used as follows:
- channel: DMA channel to use
(between 0 and (<dma-channels> - 1))
- slot: ID of request that should trigger the channel
(between 0 and (<dma-requests> - 1))
- channel-config: 32-bit configuration bitmask
(refer to include/zephyr/dt-bindings/dma/stm32_dma.h for details)
Examples
/* Definition example: STM32U5 SoC DTSI */
gpdma1: dma@40020000 {
compatible = "st,stm32u5-dma";
#dma-cells = <3>;
reg = <0x40020000 DT_SIZE_K(1)>;
clocks = <&rcc STM32_CLOCK(AHB1, 0)>;
interrupts = <29 0>, <30 0>, <31 0>, <32 0>,
<33 0>, <34 0>, <35 0>, <36 0>,
<80 0>, <81 0>, <82 0>, <83 0>,
<84 0>, <85 0>, <86 0>, <87 0>;
dma-channels = <16>;
dma-requests = <114>;
};
/*
* Usage example: SPI1 Rx/Tx via GPDMA on STM32U585
*
* Allocates channel 0/1 to Rx/Tx (request ID 6/7).
* Refer to your product's Reference Manual for
* the list and mapping of available DMA requests.
*/
&spi1 {
dmas = <&gpdma 0 6 (STM32_DMA_PERIPH_RX | STM32_DMA_PRIORITY_MEDIUM)>,
<&gpdma 1 7 (STM32_DMA_PERIPH_TX | STM32_DMA_PRIORITY_MEDIUM)>;
dma-names = "rx", "tx";
};
Properties
Properties not inherited from the base binding file.
Name |
Type |
Details |
|---|---|---|
|
|
Number of items to expect in a DMA specifier
This property is required. Constant value: |
|
|
Bitmask of available DMA channels in ascending order that are
not reserved by firmware and are available to the
kernel. i.e. first channel corresponds to LSB.
|
|
|
Number of DMA channels supported by the controller
|
|
|
Number of DMA request signals supported by the controller.
|
|
|
Memory address alignment requirement for DMA buffers used by the controller.
|
|
|
Memory size alignment requirement for DMA buffers used by the controller.
|
|
|
Minimal chunk of data possible to be copied by the controller.
|
Deprecated properties not inherited from the base binding file.
(None)
Properties inherited from the base binding file, which defines common properties that may be set on many nodes. Not all of these may apply to the “st,stm32u5-dma” compatible.
Name |
Type |
Details |
|---|---|---|
|
|
One interrupt cell per channel, in order of channel numbers.
For example, if channel 0 has IRQn 74 and channel 1 has IRQn 47:
interrupts = <74 0>, <47 0>;
This property is required. See Important properties for more information. |
|
|
Information used to address the device. The value is specific to
the device (i.e. is different depending on the compatible
property).
The "reg" property is typically a sequence of (address, length) pairs.
Each pair is called a "register block". Values are
conventionally written in hex.
For details, see "2.3.6 reg" in Devicetree Specification v0.4.
This property is required. See Important properties for more information. |
|
|
Indicates the operational status of the hardware or other
resource that the node represents. In particular:
- "okay" means the resource is operational and, for example,
can be used by device drivers
- "disabled" means the resource is not operational and the system
should treat it as if it is not present
For details, see "2.3.4 status" in Devicetree Specification v0.4.
Legal values: See Important properties for more information. |
|
|
This property is a list of strings that essentially define what
type of hardware or other resource this devicetree node
represents. Each device driver checks for specific compatible
property values to find the devicetree nodes that represent
resources that the driver should manage.
The recommended format is "vendor,device", The "vendor" part is
an abbreviated name of the vendor. The "device" is usually from
the datasheet.
The compatible property can have multiple values, ordered from
most- to least-specific. Having additional values is useful when the
device is a specific instance of a more general family, to allow the
system to match the most specific driver available.
For details, see "2.3.1 compatible" in Devicetree Specification v0.4.
This property is required. See Important properties for more information. |
|
|
Optional names given to each register block in the "reg" property.
For example:
/ {
soc {
#address-cells = <1>;
#size-cells = <1>;
uart@1000 {
reg = <0x1000 0x2000>, <0x3000 0x4000>;
reg-names = "foo", "bar";
};
};
};
The uart@1000 node has two register blocks:
- one with base address 0x1000, size 0x2000, and name "foo"
- another with base address 0x3000, size 0x4000, and name "bar"
|
|
|
Extended interrupt specifier for device, used as an alternative to
the "interrupts" property.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Optional names given to each interrupt generated by a device.
The interrupts themselves are defined in either "interrupts" or
"interrupts-extended" properties.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
If present, this refers to the node which handles interrupts generated
by this device.
For details, see "2.4 Interrupts and Interrupt Mapping" in
Devicetree Specification v0.4.
|
|
|
Human readable string describing the device. Use of this property is
deprecated except as needed on a case-by-case basis.
For details, see "4.1.2 Miscellaneous Properties" in Devicetree
Specification v0.4.
See Important properties for more information. |
|
|
Information about the device's clock providers. In general, this property
should follow conventions established in the dt-schema binding:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/clock/clock.yaml
|
|
|
Optional names given to each clock provider in the "clocks" property.
|
|
|
This property encodes the number of <u32> cells used by address fields
in "reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
This property encodes the number of <u32> cells used by size fields in
"reg" properties in this node's children.
For details, see "2.3.5 #address-cells and #size-cells" in Devicetree
Specification v0.4.
|
|
|
Indicates that the device is capable of coherent DMA operations.
For details, see "2.3.10 dma-coherent" in Devicetree Specification v0.4.
|
|
|
DMA channel specifiers relevant to the device.
|
|
|
Optional names given to the DMA channel specifiers in the "dmas" property.
|
|
|
IO channel specifiers relevant to the device.
|
|
|
Optional names given to the IO channel specifiers in the "io-channels" property.
|
|
|
Mailbox / IPM channel specifiers relevant to the device.
|
|
|
Optional names given to the mbox specifiers in the "mboxes" property.
|
|
|
Power domain specifiers relevant to the device.
|
|
|
Optional names given to the power domain specifiers in the "power-domains" property.
|
|
|
Number of cells in power-domains property
|
|
|
HW spinlock id relevant to the device.
|
|
|
Optional names given to the hwlock specifiers in the "hwlocks" property.
|
|
|
Do not initialize device automatically on boot. Device should be manually
initialized using device_init().
|
|
|
Property to identify that a device can be used as wake up source.
When this property is provided a specific flag is set into the
device that tells the system that the device is capable of
wake up the system.
Wake up capable devices are disabled (interruptions will not wake up
the system) by default but they can be enabled at runtime if necessary.
|
|
|
Automatically configure the device for runtime power management after the
init function runs.
|
|
|
List of power states that will disable this device power.
|
Specifier cell names
dma cells: channel, slot, channel-config