diff options
| author |   Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> | 2017-03-07 05:30:06 +0000 |
|---|---|---|
| committer |   Simon Horman <horms+renesas@verge.net.au> | 2017-03-07 07:51:11 +0100 |
| commit | b5a8ffad0eb0c1e5e601253edac163b2da9e855d (patch) | |
| tree | a818742afceff4a0f37e22197cfefb422515e44f /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | arm64: dts: r8a7795: salvator-x: Set drive-strength for ravb pins (diff) | |
| download | linux-rng-b5a8ffad0eb0c1e5e601253edac163b2da9e855d.tar.xz linux-rng-b5a8ffad0eb0c1e5e601253edac163b2da9e855d.zip | |
arm64: dts: r8a7795: Tidyup Audio-DMAC channel for DVC
Current Audio-DMAC is assigned "rx" as Audio-DMAC0, "tx" as Audio-DMAC1.
Thus, DVC "tx" should be assigned as Audio-DMAC1, instead of Audio-DMAC0.
Because of this, current platform board (using SRC/DVC/SSI)
Playback/Capture both will use same Audio-DMAC0
(but it depends on audio data path).
First note is that this "rx" and "tx" are from each IP point,
it doesn't mean Playback/Capture.
Second note is that Audio DMAC assigned on DT is only for
Audio-DMAC, Audio-DMAC-peri-peri has no entry.
=> Audio-DMAC
-> Audio-DMAC-peri-peri
-- HW connection
Playback case
[Mem] => [SRC]--[DVC] -> [SSI]--[Codec]
rx ~~~~~~~~~~~~
Capture
[Mem] <= [DVC]--[SRC] <- [SSI]--[Codec]
tx ~~~~~~~~~~~~
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions