diff options
| author | Bin Meng <bmeng.cn@gmail.com> | 2021-04-30 21:16:58 +0800 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2021-06-05 07:35:34 -0600 |
| commit | 139eaa7a2b5f25e42307a672849eba0e5b4cddf0 (patch) | |
| tree | 3eedf1e2ce3481018ef1325ea358747d3893eaf8 /doc/README.nand | |
| parent | c003d2cd6b415319c3e40db42b48c2815acda3d3 (diff) | |
| download | u-boot-139eaa7a2b5f25e42307a672849eba0e5b4cddf0.tar.gz u-boot-139eaa7a2b5f25e42307a672849eba0e5b4cddf0.tar.xz u-boot-139eaa7a2b5f25e42307a672849eba0e5b4cddf0.zip | |
of: addr: Translate 'dma-ranges' for parent nodes missing 'dma-ranges'
'dma-ranges' frequently exists without parent nodes having 'dma-ranges'.
While this is an error for 'ranges', this is fine because DMA capable
devices always have a translatable DMA address. Also, with no
'dma-ranges' at all, the assumption is that DMA addresses are 1:1 with
no restrictions unless perhaps the device itself has implicit
restrictions.
This keeps in sync with Linux kernel commit:
81db12ee15cb: of/address: Translate 'dma-ranges' for parent nodes missing 'dma-ranges'
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc/README.nand')
0 files changed, 0 insertions, 0 deletions