From: Charulatha V <charu@ti.com>
To: linux-omap@vger.kernel.org
Cc: khilman@deeprootsystems.com, paul@pwsan.com, tony@atomide.com,
rnayak@ti.com, p-basak2@ti.com, b-cousson@ti.com,
Charulatha V <charu@ti.com>
Subject: [PATCH:v4 04/13] OMAP: GPIO: Introduce support for OMAP15xx chip GPIO init
Date: Tue, 22 Jun 2010 20:31:47 +0530 [thread overview]
Message-ID: <1277218916-15213-5-git-send-email-charu@ti.com> (raw)
In-Reply-To: <1277218916-15213-4-git-send-email-charu@ti.com>
This patch adds support for handling OMAP15xx specific gpio_init
by providing platform device data and doing device registration.
Signed-off-by: Charulatha V <charu@ti.com>
Signed-off-by: Basak, Partha <p-basak2@ti.com>
---
arch/arm/mach-omap1/gpio15xx.c | 105 ++++++++++++++++++++++++++++++++++++++++
1 files changed, 105 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/mach-omap1/gpio15xx.c
diff --git a/arch/arm/mach-omap1/gpio15xx.c b/arch/arm/mach-omap1/gpio15xx.c
new file mode 100644
index 0000000..f3d2bd4
--- /dev/null
+++ b/arch/arm/mach-omap1/gpio15xx.c
@@ -0,0 +1,102 @@
+/*
+ * OMAP15XX-specific gpio code
+ *
+ * Copyright (C) 2010 Texas Instruments, Inc.
+ *
+ * Author:
+ * Charulatha V <charu@ti.com>
+ *
+ * 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/gpio.h>
+
+#define OMAP1_MPUIO_VBASE OMAP1_MPUIO_BASE
+#define OMAP1510_GPIO_BASE 0xfffce000
+
+static struct omap_gpio_dev_attr omap15xx_gpio_attr = {
+ .gpio_bank_width = 16,
+ .omap1_ick_flag = true,
+};
+
+/*
+ * OMAP15XX GPIO1 interface data
+ */
+static struct __initdata resource omap15xx_mpu_gpio_resources[] = {
+ {
+ .start = OMAP1_MPUIO_VBASE,
+ .end = OMAP1_MPUIO_VBASE + SZ_2K - 1,
+ .flags = IORESOURCE_MEM,
+ },
+ {
+ .start = INT_MPUIO,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
+static struct __initdata omap_gpio_platform_data omap15xx_mpu_gpio_config = {
+ .virtual_irq_start = IH_MPUIO_BASE,
+ .bank_type = METHOD_MPUIO,
+ .gpio_attr = &omap15xx_gpio_attr,
+};
+
+static struct __initdata platform_device omap15xx_mpu_gpio = {
+ .name = "omap-gpio",
+ .id = 0,
+ .dev = {
+ .platform_data = &omap15xx_mpu_gpio_config,
+ },
+ .num_resources = ARRAY_SIZE(omap15xx_mpu_gpio_resources),
+ .resource = omap15xx_mpu_gpio_resources,
+};
+
+/*
+ * OMAP15XX GPIO2 interface data
+ */
+static struct __initdata resource omap15xx_gpio_resources[] = {
+ {
+ .start = OMAP1510_GPIO_BASE,
+ .end = OMAP1510_GPIO_BASE + SZ_2K - 1,
+ .flags = IORESOURCE_MEM,
+ },
+ {
+ .start = INT_GPIO_BANK1,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
+static struct __initdata omap_gpio_platform_data omap15xx_gpio_config = {
+ .virtual_irq_start = IH_GPIO_BASE,
+ .bank_type = METHOD_GPIO_1510,
+ .gpio_attr = &omap15xx_gpio_attr,
+};
+
+static struct __initdata platform_device omap15xx_gpio = {
+ .name = "omap-gpio",
+ .id = 1,
+ .dev = {
+ .platform_data = &omap15xx_gpio_config,
+ },
+ .num_resources = ARRAY_SIZE(omap15xx_gpio_resources),
+ .resource = omap15xx_gpio_resources,
+};
+
+/*
+ * omap15xx_gpio_init needs to be done before
+ * machine_init functions access gpio APIs.
+ * Hence omap15xx_gpio_init is a postcore_initcall.
+ */
+static int __init omap15xx_gpio_init(void)
+{
+ if (!cpu_is_omap15xx())
+ return -EINVAL;
+
+ platform_device_register(&omap15xx_mpu_gpio);
+ platform_device_register(&omap15xx_gpio);
+
+ gpio_bank_count = 2,
+ return 0;
+}
+postcore_initcall(omap15xx_gpio_init);
--
1.6.3.3
next prev parent reply other threads:[~2010-06-22 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 15:01 [PATCH:v4 00/13] OMAP: GPIO: Implement GPIO in HWMOD way Charulatha V
2010-06-22 15:01 ` [PATCH:v4 01/13] OMAP: GPIO: Modify init() in preparation for platform device implementation Charulatha V
2010-06-22 15:01 ` [PATCH:v4 02/13] OMAP: GPIO: Populate GPIO base address in omapxxxx.h Charulatha V
2010-06-22 15:01 ` [PATCH:v4 03/13] OMAP: GPIO: Include platform_data structure for GPIO Charulatha V
2010-06-22 15:01 ` Charulatha V [this message]
2010-06-22 15:01 ` [PATCH:v4 05/13] OMAP: GPIO: Introduce support for OMAP16xx chip GPIO init Charulatha V
2010-06-22 15:01 ` [PATCH:v4 06/13] OMAP: GPIO: Introduce support for OMAP7xx " Charulatha V
2010-06-22 15:01 ` [PATCH:v4 07/13] OMAP: GPIO: add GPIO hwmods structures for OMAP3 Charulatha V
2010-06-22 15:01 ` [PATCH:v4 08/13] OMAP: GPIO: add GPIO hwmods structures for OMAP242X Charulatha V
2010-06-22 15:01 ` [PATCH:v4 09/13] OMAP: GPIO: add GPIO hwmods structures for OMAP243X Charulatha V
2010-06-22 15:01 ` [PATCH:v4 10/13] OMAP: GPIO: Add gpio dev_attr and correct clks in OMAP4 hwmod struct Charulatha V
2010-06-22 15:01 ` [PATCH:v4 11/13] OMAP: GPIO: Introduce support for OMAP2PLUS chip GPIO init Charulatha V
2010-06-22 15:01 ` [PATCH:v4 12/13] OMAP: GPIO: Implement GPIO as a platform device Charulatha V
2010-06-22 15:01 ` [PATCH:v4 13/13] OMAP: GPIO: Remove omap_gpio_init() Charulatha V
2010-06-25 23:36 ` [PATCH:v4 12/13] OMAP: GPIO: Implement GPIO as a platform device Kevin Hilman
2010-06-24 7:03 ` [PATCH:v4 03/13] OMAP: GPIO: Include platform_data structure for GPIO DebBarma, Tarun Kanti
2010-07-06 13:17 ` [PATCH:v4 00/13] OMAP: GPIO: Implement GPIO in HWMOD way Tony Lindgren
2010-07-27 11:47 ` Cousson, Benoit
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=1277218916-15213-5-git-send-email-charu@ti.com \
--to=charu@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.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;
as well as URLs for NNTP newsgroup(s).