From: jgutierrez@ti.com (Juan Gutierrez)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/2] omap4: iommu: fix irq and clock name for dsp-iommu
Date: Thu, 10 May 2012 15:09:48 -0500 [thread overview]
Message-ID: <1336680588-8572-3-git-send-email-jgutierrez@ti.com> (raw)
In-Reply-To: <1336680588-8572-1-git-send-email-jgutierrez@ti.com>
Irq and clock names were wrong for dsp iommu configuration
for omap4.
- Renamed tesla_ick to dsp_fck:
This is required because the new naming convention introduced
by: commit 0e43327 "OMAP4 clock: Fix clock names and align
with hwmod names"
- Renamed INT_44XX_DSP_MMU to OMAP44XX_IRQ_TESLA_MMU.
Naming convention adopted since: commit e927f8d "omap4: Add
auto-generated irq and dma headers"
- dsp-iommu is enabled by default.
Signed-off-by: Juan Gutierrez <jgutierrez@ti.com>
Acked-by: Ohad Ben-Cohen <ohad@wizery.com>
---
arch/arm/mach-omap2/omap-iommu.c | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/omap-iommu.c b/arch/arm/mach-omap2/omap-iommu.c
index ac49384..1be8bcb 100644
--- a/arch/arm/mach-omap2/omap-iommu.c
+++ b/arch/arm/mach-omap2/omap-iommu.c
@@ -73,19 +73,17 @@ static struct iommu_device omap4_devices[] = {
.da_end = 0xFFFFF000,
},
},
-#if defined(CONFIG_MPU_TESLA_IOMMU)
{
.base = OMAP4_MMU2_BASE,
- .irq = INT_44XX_DSP_MMU,
+ .irq = OMAP44XX_IRQ_TESLA_MMU,
.pdata = {
.name = "tesla",
.nr_tlb_entries = 32,
- .clk_name = "tesla_ick",
+ .clk_name = "dsp_fck",
.da_start = 0x0,
.da_end = 0xFFFFF000,
},
},
-#endif
};
#define NR_OMAP4_IOMMU_DEVICES ARRAY_SIZE(omap4_devices)
static struct platform_device *omap4_iommu_pdev[NR_OMAP4_IOMMU_DEVICES];
--
1.7.1
prev parent reply other threads:[~2012-05-10 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 20:09 [PATCH v4 0/2] Fixes in preparation for enabling Dsp in omap4 Juan Gutierrez
2012-05-10 20:09 ` [PATCH v4 1/2] omap: mailbox: enable mailbox irq per instance Juan Gutierrez
2012-05-10 20:39 ` Ohad Ben-Cohen
2012-05-10 20:09 ` Juan Gutierrez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1336680588-8572-3-git-send-email-jgutierrez@ti.com \
--to=jgutierrez@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox