dt-bindings: dma: ti: k3-udma: Update for atype support (virtualization) (8c8b07cb) · Commits · 戴 / test

In UDMA each channel can use different ATYPE value which tells UDMA how the addresses in the descriptors should be treated: 0: pointers are physical addresses (no translation) 1: pointers are intermediate addresses (PVU) 2: pointers are virtual addresses (SMMU) When virtualized environment is used then the dma binding should use additional cell to configure the desired ATYPE for the channel. Signed-off-by:

Peter Ujfalusi <peter.ujfalusi@ti.com> Reviewed-by:

Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/20200218143126.11361-2-peter.ujfalusi@ti.com Signed-off-by:

Vinod Koul <vkoul@kernel.org>

Documentation/devicetree/bindings/dma/ti/k3-udma.yaml

+18 −1

Original line number	Diff line number	Diff line
		@@ -45,7 +45,8 @@ allOf:

		properties:
		"#dma-cells":
		const: 1
		minimum: 1
		maximum: 2
		description: \|
		The cell is the PSI-L thread ID of the remote (to UDMAP) end.
		Valid ranges for thread ID depends on the data movement direction:
		@@ -55,6 +56,8 @@ properties:
		Please refer to the device documentation for the PSI-L thread map and also
		the PSI-L peripheral chapter for the correct thread ID.

		When #dma-cells is 2, the second parameter is the channel ATYPE.

		compatible:
		enum:
		- ti,am654-navss-main-udmap
		@@ -131,6 +134,20 @@ required:
		- ti,sci-rm-range-rchan
		- ti,sci-rm-range-rflow

		if:
		properties:
		"#dma-cells":
		const: 2
		then:
		properties:
		ti,udma-atype:
		description: ATYPE value which should be used by non slave channels
		allOf:
		- $ref: /schemas/types.yaml#/definitions/uint32

		required:
		- ti,udma-atype

		examples:
		- \|+
		cbass_main {

Admin message