From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
linux-omap@vger.kernel.org, h-kanigeri2@ti.com,
omar.ramirez@ti.com, sakari.ailus@maxwell.research.nokia.com,
tony@atomide.com
Subject: Re: [PATCH 3/6] omap iommu: omap3 iommu device registration
Date: Sat, 16 May 2009 10:20:36 +0100 [thread overview]
Message-ID: <20090516092036.GD15328@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090505124700.4583.69988.stgit@oreo.research.nokia.com>
On Tue, May 05, 2009 at 03:47:00PM +0300, Hiroshi DOYU wrote:
> +static struct resource omap3_iommu_res[] = {
> + { /* Camera ISP MMU */
> + .start = OMAP3_MMU1_BASE,
> + .end = OMAP3_MMU1_BASE + MMU_REG_SIZE - 1,
> + .flags = IORESOURCE_MEM,
> + },
> + {
> + .start = OMAP3_MMU1_IRQ,
> + .flags = IORESOURCE_IRQ,
> + },
> + { /* IVA2.2 MMU */
> + .start = OMAP3_MMU2_BASE,
> + .end = OMAP3_MMU2_BASE + MMU_REG_SIZE - 1,
> + .flags = IORESOURCE_MEM,
> + },
> + {
> + .start = OMAP3_MMU2_IRQ,
> + .flags = IORESOURCE_IRQ,
> + },
> +};
> +#define NR_IOMMU_RES (ARRAY_SIZE(omap3_iommu_res) / 2)
This looks all very convoluted. Why not do something like:
static unsigned long iommu_base[] = {
OMAP3_MMU1_BASE,
OMAP3_MMU2_BASE,
};
static int iommu_irq[] = {
OMAP3_MMU1_IRQ,
OMAP3_MMU2_IRQ,
};
> +static struct platform_device *omap3_iommu_pdev[NR_IOMMU_DEVICES];
> +
> +static int __init omap3_iommu_init(void)
> +{
> + int i, err;
> +
> + for (i = 0; i < NR_IOMMU_DEVICES; i++) {
> + struct platform_device *pdev;
> +
> + pdev = platform_device_alloc("omap-iommu", i + 1);
Why number them 1 and up when zero is perfectly fine?
> + if (!pdev) {
> + err = -ENOMEM;
> + goto err_out;
> + }
> + err = platform_device_add_resources(pdev,
> + &omap3_iommu_res[2 * i], NR_IOMMU_RES);
struct resource res[2];
res[0].start = iommu_base[i];
res[0].end = iommu_base[i] + MMU_REG_SIZE - 1;
res[0].flags = IORESOURCE_MEM;
res[1].start = res[1].end = iommu_irq[i];
res[1].flags = IORESOURCE_IRQ;
err = platform_device_add_resources(pdev, &res, ARRAY_SIZE(res));
There's no need to keep 'res' around since it's copied by add_resources.
> + if (err)
> + goto err_out;
> + err = platform_device_add_data(pdev, &omap3_iommu_pdata[i],
> + sizeof(omap3_iommu_pdata[0]));
> + if (err)
> + goto err_out;
> + err = platform_device_add(pdev);
> + if (err)
> + goto err_out;
> + omap3_iommu_pdev[i] = pdev;
> + }
> + return 0;
> +
> +err_out:
> + while (i--)
> + platform_device_put(omap3_iommu_pdev[i]);
> + return err;
> +}
> +module_init(omap3_iommu_init);
> +
> +static void __exit omap3_iommu_exit(void)
> +{
> + int i;
> +
> + for (i = 0; i < NR_IOMMU_DEVICES; i++)
> + platform_device_unregister(omap3_iommu_pdev[i]);
> +}
> +module_exit(omap3_iommu_exit);
> +
> +MODULE_AUTHOR("Hiroshi DOYU");
> +MODULE_DESCRIPTION("omap iommu: omap3 device registration");
> +MODULE_LICENSE("GPL v2");
>
>
> -------------------------------------------------------------------
> List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
> FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php
> Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
next prev parent reply other threads:[~2009-05-16 9:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 12:46 [PATCH 0/6] Initial support for omap iommu driver Hiroshi DOYU
2009-05-05 12:46 ` [PATCH 1/6] omap iommu: tlb and pagetable primitives Hiroshi DOYU
2009-05-05 20:19 ` Kanigeri, Hari
2009-05-06 5:56 ` Hiroshi DOYU
2009-05-05 12:46 ` [PATCH 2/6] omap iommu: omap2 architecture specific functions Hiroshi DOYU
2009-05-06 14:31 ` Kanigeri, Hari
2009-05-07 5:12 ` Hiroshi DOYU
2009-05-07 14:40 ` Kanigeri, Hari
2009-05-05 12:47 ` [PATCH 3/6] omap iommu: omap3 iommu device registration Hiroshi DOYU
2009-05-05 19:32 ` Felipe Contreras
2009-05-06 6:00 ` Hiroshi DOYU
2009-05-07 20:02 ` Felipe Contreras
2009-05-07 20:11 ` [RFC/PATCH 0/3] omap3-iommu: cleanups and remote registration Felipe Contreras
2009-05-07 20:11 ` [RFC/PATCH 1/3] omap3-iommu: reorganize Felipe Contreras
2009-05-07 20:11 ` [RFC/PATCH 2/3] omap3-iommu: split init function into omap_iommu_add Felipe Contreras
2009-05-07 20:11 ` [RFC/PATCH 3/3] omap3-iommu: remote registration Felipe Contreras
2009-05-07 21:14 ` [RFC/PATCH 1/3] omap3-iommu: reorganize Felipe Balbi
2009-05-07 22:16 ` Felipe Contreras
2009-05-08 4:15 ` Hiroshi DOYU
2009-05-07 20:28 ` [RFC/PATCH 0/3] omap3-iommu: cleanups and remote registration Kanigeri, Hari
2009-05-07 20:39 ` Felipe Contreras
2009-05-07 20:54 ` Kanigeri, Hari
2009-05-08 4:14 ` Hiroshi DOYU
2009-05-08 8:04 ` Felipe Contreras
2009-05-07 20:05 ` [PATCH 3/6] omap iommu: omap3 iommu device registration Felipe Contreras
2009-05-08 4:10 ` Hiroshi DOYU
2009-05-08 7:32 ` Felipe Contreras
2009-05-08 17:21 ` Aguirre Rodriguez, Sergio Alberto
2009-05-08 22:27 ` Felipe Contreras
2009-05-16 9:20 ` Russell King - ARM Linux [this message]
2009-05-16 9:38 ` Felipe Contreras
2009-05-16 9:54 ` Russell King - ARM Linux
2009-05-16 9:56 ` Felipe Contreras
2009-05-16 9:55 ` Russell King - ARM Linux
2009-05-18 5:36 ` Hiroshi DOYU
2009-05-18 9:39 ` Hiroshi DOYU
2009-05-18 14:26 ` Hiroshi DOYU
2009-05-18 16:43 ` [PATCH] omap3-iommu: reorganize Felipe Contreras
2009-05-19 6:03 ` Hiroshi DOYU
2009-05-19 9:43 ` Felipe Contreras
2009-05-18 5:22 ` [PATCH 3/6] omap iommu: omap3 iommu device registration Hiroshi DOYU
2009-05-05 12:47 ` [PATCH 4/6] omap iommu: simple virtual address space management Hiroshi DOYU
2009-05-16 9:22 ` Russell King - ARM Linux
2009-05-18 6:31 ` Hiroshi DOYU
2009-05-18 13:10 ` Russell King - ARM Linux
2009-05-05 12:47 ` [PATCH 5/6] omap iommu: entries for Kconfig and Makefile Hiroshi DOYU
2009-05-18 13:36 ` Russell King - ARM Linux
2009-05-05 12:47 ` [PATCH 6/6] omap2 " Hiroshi DOYU
-- strict thread matches above, loose matches on Subject: below --
2009-01-16 8:37 [PATCH 0/6] arm: omap iommu: add initial support Hiroshi DOYU
2009-01-16 8:37 ` [PATCH 3/6] omap iommu: omap3 iommu device registration Hiroshi DOYU
2009-01-17 16:21 ` Russell King - ARM Linux
2009-01-27 21:29 ` Hiroshi DOYU
2009-01-28 10:41 ` Russell King - ARM Linux
2009-01-28 11:37 ` Hiroshi DOYU
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=20090516092036.GD15328@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Hiroshi.DOYU@nokia.com \
--cc=h-kanigeri2@ti.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--cc=sakari.ailus@maxwell.research.nokia.com \
--cc=tony@atomide.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