summaryrefslogtreecommitdiff
path: root/include/dt-bindings/memory
diff options
context:
space:
mode:
authorMiles Chen <miles.chen@mediatek.com>2020-09-04 13:40:38 +0300
committerJoerg Roedel <jroedel@suse.de>2020-09-04 14:20:36 +0300
commitc2c59456e1fcad3f464761c5839399176e3a934a (patch)
treee5c2e6e114d5b4195f518e9251b7ede6344e8caf /include/dt-bindings/memory
parentf53dd97874e6d916ce7d3a487a1073ef5c10e153 (diff)
downloadlinux-c2c59456e1fcad3f464761c5839399176e3a934a.tar.xz
iommu/mediatek: Check 4GB mode by reading infracfg
In previous discussion [1] and [2], we found that it is risky to use max_pfn or totalram_pages to tell if 4GB mode is enabled. Check 4GB mode by reading infracfg register, remove the usage of the un-exported symbol max_pfn. This is a step towards building mtk_iommu as a kernel module. [1] https://lore.kernel.org/lkml/20200603161132.2441-1-miles.chen@mediatek.com/ [2] https://lore.kernel.org/lkml/20200604080120.2628-1-miles.chen@mediatek.com/ [3] https://lore.kernel.org/lkml/20200715205120.GA778876@bogus/ Cc: Mike Rapoport <rppt@linux.ibm.com> Cc: David Hildenbrand <david@redhat.com> Cc: Yong Wu <yong.wu@mediatek.com> Cc: Yingjoe Chen <yingjoe.chen@mediatek.com> Cc: Christoph Hellwig <hch@lst.de> Cc: Rob Herring <robh@kernel.org> Cc: Matthias Brugger <matthias.bgg@gmail.com> Cc: Joerg Roedel <joro@8bytes.org> Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com> Signed-off-by: Miles Chen <miles.chen@mediatek.com> Link: https://lore.kernel.org/r/20200904104038.4979-1-miles.chen@mediatek.com Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'include/dt-bindings/memory')
0 files changed, 0 insertions, 0 deletions