Thierry Reding <thierry.red...@gmail.com> writes: > From: Thierry Reding <tred...@nvidia.com> > > The memory controller on NVIDIA Tegra124 exposes various knobs that can > be used to tune the behaviour of the clients attached to it. > > Currently this driver sets up the latency allowance registers to the HW > defaults. Eventually an API should be exported by this driver (via a > custom API or a generic subsystem) to allow clients to register latency > requirements. > > This driver also registers an IOMMU (SMMU) that's implemented by the > memory controller. > > Signed-off-by: Thierry Reding <tred...@nvidia.com> > --- > drivers/memory/Kconfig | 9 + > drivers/memory/Makefile | 1 + > drivers/memory/tegra124-mc.c | 1945 > ++++++++++++++++++++++++++++++ > include/dt-bindings/memory/tegra124-mc.h | 30 + > 4 files changed, 1985 insertions(+) > create mode 100644 drivers/memory/tegra124-mc.c > create mode 100644 include/dt-bindings/memory/tegra124-mc.h
I prefer reusing the existing SMMU and having MC and SMMU separated since most of SMMU code are not different from functionality POV, and new MC features are quite independent of SMMU. If it's really convenient to combine MC and SMMU into one driver, we could move "drivers/iomm/tegra-smmu.c" here first, and add MC features on the top of it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
