Hi Omar,
On 3/7/2011 8:01 PM, Ramirez Luna, Omar wrote:
Hi Benoit,
On Mon, Mar 7, 2011 at 6:55 AM, Cousson, Benoitb-cous...@ti.com wrote:
Hi Omar,
I have some concern about the introduction of a hwmod that does not match
the actual HW capability. MMU does exist, but there is no SW control
Hi Benoit,
On Tue, Mar 8, 2011 at 3:29 PM, Cousson, Benoit b-cous...@ti.com wrote:
What I meant is that the mmu does not have any explicit PRCM module enable
control. The PRCM does control only the DSP as a whole. Since hwmods are
generated with a PRCM granularity, any sub module will not be
Add mmu hwmod data for ipu and dsp.
Signed-off-by: Omar Ramirez Luna omar.rami...@ti.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 156 +--
1 files changed, 144 insertions(+), 12 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
Hi Omar,
I have some concern about the introduction of a hwmod that does not
match the actual HW capability. MMU does exist, but there is no SW
control for it. In fact the only control available is for mmu + cache +
logic, and that's why the MMU is handle today under the main DSP/IPU hwmod.
Hi Benoit,
On Mon, Mar 7, 2011 at 6:55 AM, Cousson, Benoit b-cous...@ti.com wrote:
Hi Omar,
I have some concern about the introduction of a hwmod that does not match
the actual HW capability. MMU does exist, but there is no SW control for it.
Maybe I'm missing something, but iommu (driver)
