Hi Omar,
On Thursday 05 January 2012 20:24:25 Ramirez Luna, Omar wrote:
On Sun, Dec 25, 2011 at 3:08 PM, Laurent Pinchart wrote:
I'm not sure how this clock stuff works, but I'm guessing the device
is supposed to go to sleep at some points in time, and with your patch
OMAP3/4: iommu:
Hi Laurent
On Sun, Dec 25, 2011 at 3:08 PM, Laurent Pinchart
laurent.pinch...@ideasonboard.com wrote:
I'm not sure how this clock stuff works, but I'm guessing the device
is supposed to go to sleep at some points in time, and with your patch
OMAP3/4: iommu: adapt to runtime pm it won't, as
Hi Omar,
On Friday 23 December 2011 16:53:58 Ramirez Luna, Omar wrote:
On Mon, Dec 19, 2011 at 10:11 AM, Felipe Contreras wrote:
On Fri, Dec 16, 2011 at 4:01 AM, Ramirez Luna, Omar wrote:
On Thu, Dec 15, 2011 at 6:39 PM, Felipe Contreras wrote:
Are you sure you are not missing something
On Mon, Dec 19, 2011 at 10:11 AM, Felipe Contreras
felipe.contre...@gmail.com wrote:
On Fri, Dec 16, 2011 at 4:01 AM, Ramirez Luna, Omar omar.rami...@ti.com
wrote:
On Thu, Dec 15, 2011 at 6:39 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Are you sure you are not missing something
On Fri, Dec 16, 2011 at 4:01 AM, Ramirez Luna, Omar omar.rami...@ti.com wrote:
On Thu, Dec 15, 2011 at 6:39 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Are you sure you are not missing something like:
.clk = cam_ick,
I believe in this case cam_ick is used as the main clock as it
On Thu, Dec 15, 2011 at 6:18 AM, Omar Ramirez Luna omar.rami...@ti.com wrote:
+/* l4_core - isp mmu */
+static struct omap_hwmod_ocp_if omap3xxx_l4_core__isp_mmu = {
+ .master = omap3xxx_l4_core_hwmod,
+ .slave = omap3xxx_isp_mmu_hwmod,
+ .addr =
On Thu, Dec 15, 2011 at 6:39 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
On Thu, Dec 15, 2011 at 6:18 AM, Omar Ramirez Luna omar.rami...@ti.com
wrote:
+/* l4_core - isp mmu */
+static struct omap_hwmod_ocp_if omap3xxx_l4_core__isp_mmu = {
+ .master =
Add mmu hwmod data for iva and isp.
Due to compatibility an ifdef CONFIG_OMAP_IOMMU_IVA2 needs to be
propagated (previously on iommu resource info) to hwmod data in OMAP3,
so users of iommu and tidspbridge can avoid issues of two modules
managing mmu data/irqs/resets; this until tidspbridge can
