aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/dt-bindings
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2017-06-23 16:33:43 +0200
committerArnd Bergmann <arnd@arndb.de>2017-06-23 16:37:22 +0200
commit2b29ca22ed8a79ef1942b6546ccab5953678028d (patch)
tree99c0aa11cea115c172cc66b57d9c2eab0d740586 /include/dt-bindings
parentMerge tag 'mvebu-fixes-4.12-1' of git://git.infradead.org/linux-mvebu into next/dt64 (diff)
downloadwireguard-linux-2b29ca22ed8a79ef1942b6546ccab5953678028d.tar.xz
wireguard-linux-2b29ca22ed8a79ef1942b6546ccab5953678028d.zip
Revert "arm64: dts: marvell: add dma-mask in crypto nodes for 7k/8k"
As I found by chance while merging another patch, the usage of a dma-mask in this DT node is wrong for multiple reasons: - dma-masks are a Linux specific concept, not a general hardware feature - In DT, we use the "dma-ranges" property to describe how DMA addresses related between devices. - The 40-bit mask appears to be completely unnecessary here, as the SoC cannot address that much memory anyway, so simply asking for a 64-bit mask (as supported by the device) should succeed anyway. The patch to remove the parsing of the property is getting merged through the crypto tree. Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Diffstat (limited to 'include/dt-bindings')
0 files changed, 0 insertions, 0 deletions