diff options
| author | Subramaniam C.A <subramaniam.ca@ti.com> | 2012-04-13 11:38:41 -0500 |
|---|---|---|
| committer | Ziyann <jaraidaniel@gmail.com> | 2014-10-01 12:58:03 +0200 |
| commit | 268ebf01d357d4b99de2f8e2476004eb5ec24ebb (patch) | |
| tree | bb5a7fd12885029789a2507a62ba30a3d8495640 /arch/arm/mach-shmobile | |
| parent | 27404fd8b2c1e23ac21203a5c2546bccf9b94cd0 (diff) | |
| download | kernel_samsung_tuna-268ebf01d357d4b99de2f8e2476004eb5ec24ebb.zip kernel_samsung_tuna-268ebf01d357d4b99de2f8e2476004eb5ec24ebb.tar.gz kernel_samsung_tuna-268ebf01d357d4b99de2f8e2476004eb5ec24ebb.tar.bz2 | |
omap: iommu: program constraints based on platform data
IOMMU driver requests and releases constraints in iommu_get
and iommu_put respectively. These constraints are actually
needed only on OMAP4 and beyond for sub-systems that have
an AMMU. The current driver code has these values hard-coded
for all the chips.
A new platform data field has been added now for the constraints
values, and this allows the values to be programmed based on
the OMAP chip and also allow a unique value if needed for each
iommu instance.
The logic in IOMMU driver code is adjusted to request the
constraints only if the relevant platform data field is set.
Change-Id: Iab18cbdde1d7fa7507dbff0b9512c8577b42fefd
Signed-off-by: Subramaniam C.A <subramaniam.ca@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
Diffstat (limited to 'arch/arm/mach-shmobile')
0 files changed, 0 insertions, 0 deletions