From: Felipe Balbi <felipe.balbi@nokia.com>
To: "ext Kanigeri, Hari" <h-kanigeri2@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gupta, Ramesh" <grgupta@ti.com>,
"rmk@arm.linux.org.uk" <rmk@arm.linux.org.uk>,
"Pasam, Vijay" <vpasam@ti.com>
Subject: Re: [RFC][PATCH 2/3] ARM:OMAP4 iommu:add omap4 support in iommu
Date: Fri, 24 Jul 2009 21:27:02 +0300 [thread overview]
Message-ID: <20090724182702.GA10206@nokia.com> (raw)
In-Reply-To: <8F7AF80515AF0D4D93307E594F3CB40E3A8CAD44@dlee03.ent.ti.com>
On Fri, Jul 24, 2009 at 07:22:32PM +0200, ext Kanigeri, Hari wrote:
> This patch adds omap4 support in iommu
> module. This creates OMAP4 platform specific file
> for iommu and defines the Ducati MMU fault interrupt.
>
> Signed-off-by: Hari Kanigeri <h-kanigeri2@ti.com>
> ---
> arch/arm/mach-omap2/omap4-iommu.c | 112 ++++++++++++++++++++++++++++++++
> arch/arm/plat-omap/include/mach/irqs.h | 2 +-
> 2 files changed, 113 insertions(+), 1 deletions(-)
> create mode 100644 arch/arm/mach-omap2/omap4-iommu.c
>
> diff --git a/arch/arm/mach-omap2/omap4-iommu.c b/arch/arm/mach-omap2/omap4-iommu.c
> new file mode 100644
> index 0000000..5a782df
> --- /dev/null
> +++ b/arch/arm/mach-omap2/omap4-iommu.c
> @@ -0,0 +1,112 @@
> +/*
> + * omap iommu: omap4 device registration
> + *
> + * Copyright (C) 2009-2010 Nokia Corporation
> + *
> + * Written by Hari Kanigeri <h-kanigeri2@ti.com>
> + *
> + * Added support for OMAP4. This is based on original file
> + * omap3-iommu.c
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + */
> +
> +#include <linux/platform_device.h>
> +
> +#include <mach/iommu.h>
> +#include <mach/irqs.h>
> +
> +#define OMAP4_MMU1_BASE 0x55082000
> +#define OMAP4_MMU2_BASE 0x4A066000
> +
> +#define OMAP4_MMU1_IRQ INT_44XX_DUCATI_MMU_IRQ
> +#define OMAP4_MMU2_IRQ INT_44XX_DSP_MMU
> +
> +
> +
> +static unsigned long iommu_base[] __initdata = {
> + OMAP4_MMU1_BASE,
> + OMAP4_MMU2_BASE,
> +};
> +
> +static int iommu_irq[] __initdata = {
> + OMAP4_MMU1_IRQ,
> + OMAP4_MMU2_IRQ,
> +};
these two looks really odd :-s
> +
> +static const struct iommu_platform_data omap4_iommu_pdata[] __initconst = {
> + {
> + .name = "ducati",
> + .nr_tlb_entries = 32,
> + .clk_name = "ducati_ick",
passing clk names should be avoided. use clkdev.
> + },
> +#if defined(CONFIG_MPU_TESLA_IOMMU)
this ifdef looks odd.
--
balbi
next prev parent reply other threads:[~2009-07-24 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 17:22 [RFC][PATCH 2/3] ARM:OMAP4 iommu:add omap4 support in iommu Kanigeri, Hari
2009-07-24 18:21 ` Hiroshi DOYU
2009-07-27 0:18 ` Kanigeri, Hari
2009-07-27 6:47 ` Hiroshi DOYU
2009-07-28 15:42 ` Kanigeri, Hari
2009-07-29 6:36 ` Hiroshi DOYU
2009-07-24 18:27 ` Felipe Balbi [this message]
2009-07-24 18:47 ` Hiroshi DOYU
2009-07-24 20:08 ` Felipe Balbi
2009-07-26 18:16 ` Kanigeri, Hari
2009-07-25 9:02 ` Shilimkar, Santosh
2009-07-25 23:17 ` Kanigeri, Hari
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=20090724182702.GA10206@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=grgupta@ti.com \
--cc=h-kanigeri2@ti.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=tony@atomide.com \
--cc=vpasam@ti.com \
/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