threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
45 lines
1.1 KiB
Plaintext
45 lines
1.1 KiB
Plaintext
* CSR SiRFSoC DMA controller
|
|
|
|
See dma.txt first
|
|
|
|
Required properties:
|
|
- compatible: Should be "sirf,prima2-dmac", "sirf,atlas7-dmac" or
|
|
"sirf,atlas7-dmac-v2"
|
|
- reg: Should contain DMA registers location and length.
|
|
- interrupts: Should contain one interrupt shared by all channel
|
|
- #dma-cells: must be <1>. used to represent the number of integer
|
|
cells in the dmas property of client device.
|
|
- clocks: clock required
|
|
|
|
Example:
|
|
|
|
Controller:
|
|
dmac0: dma-controller@b00b0000 {
|
|
compatible = "sirf,prima2-dmac";
|
|
reg = <0xb00b0000 0x10000>;
|
|
interrupts = <12>;
|
|
clocks = <&clks 24>;
|
|
#dma-cells = <1>;
|
|
};
|
|
|
|
|
|
Client:
|
|
Fill the specific dma request line in dmas. In the below example, spi0 read
|
|
channel request line is 9 of the 2nd dma controller, while write channel uses
|
|
4 of the 2nd dma controller; spi1 read channel request line is 12 of the 1st
|
|
dma controller, while write channel uses 13 of the 1st dma controller:
|
|
|
|
spi0: spi@b00d0000 {
|
|
compatible = "sirf,prima2-spi";
|
|
dmas = <&dmac1 9>,
|
|
<&dmac1 4>;
|
|
dma-names = "rx", "tx";
|
|
};
|
|
|
|
spi1: spi@b0170000 {
|
|
compatible = "sirf,prima2-spi";
|
|
dmas = <&dmac0 12>,
|
|
<&dmac0 13>;
|
|
dma-names = "rx", "tx";
|
|
};
|