public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Charulatha V <charu@ti.com>
Cc: linux-omap@vger.kernel.org, rnayak@ti.com, paul@pwsan.com
Subject: Re: [PATCH 2/8] OMAP3:GPIO:Add support for early platform gpio device
Date: Thu, 1 Apr 2010 02:13:57 -0700	[thread overview]
Message-ID: <20100401091357.GE31200@atomide.com> (raw)
In-Reply-To: <1270038239-1090-3-git-send-email-charu@ti.com>

* Charulatha V <charu@ti.com> [100331 05:15]:
> This patch adds support for implementing OMAP3 GPIO as an
> early platform device and adds gpio_init specific to OMAP3
> 
> This patch adds device structures for each GPIO device in
> OMAP3 architecture. These strutures are not created in a
> separate *_data.c file because these structures would be
> removed once the driver gets adapted to HWMOD way.
> 
> Signed-off-by: Charulatha V <charu@ti.com>
> ---
>  arch/arm/mach-omap2/gpio3xxx.c          |  351 +++++++++++++++++++++++++++++++
>  arch/arm/mach-omap2/include/mach/gpio.h |   13 +-
>  2 files changed, 363 insertions(+), 1 deletions(-)
>  create mode 100644 arch/arm/mach-omap2/gpio3xxx.c
> 
> diff --git a/arch/arm/mach-omap2/gpio3xxx.c b/arch/arm/mach-omap2/gpio3xxx.c
> new file mode 100644
> index 0000000..8f404e7
> --- /dev/null
> +++ b/arch/arm/mach-omap2/gpio3xxx.c
> @@ -0,0 +1,351 @@
> +/*
> + * gpio3xxx.c - OMAP3-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 <plat/gpio.h>
> +
> +/*
> + * OMAP3 GPIO reg offsets
> + */
> +static struct gpio_reg_offset omap3_gpio_reg = {
> +	.data_in	= OMAP24XX_GPIO_DATAIN,
> +	.data_out	= OMAP24XX_GPIO_DATAOUT,
> +	.data_out_set	= OMAP24XX_GPIO_SETDATAOUT,
> +	.data_out_clear	= OMAP24XX_GPIO_CLEARDATAOUT,
> +	.dir_ctrl	= OMAP24XX_GPIO_OE,
> +	.irq_status0	= OMAP24XX_GPIO_IRQSTATUS1,
> +	.irq_status1	= OMAP24XX_GPIO_IRQSTATUS2,
> +	.irq_mask	= OMAP24XX_GPIO_IRQENABLE1,
> +	.irq_set	= OMAP24XX_GPIO_SETIRQENABLE1,
> +	.irq_clear	= OMAP24XX_GPIO_CLEARIRQENABLE1,
> +	.irq_mask_bits	= 0xffffffff,
> +	.irq_inv	= 0,
> +	.wkup_enable	= OMAP24XX_GPIO_WAKE_EN,
> +	.wkup_clear	= OMAP24XX_GPIO_CLEARWKUENA,
> +	.wkup_set	= OMAP24XX_GPIO_SETWKUENA,
> +	.debounce_ena	= OMAP24XX_GPIO_DEBOUNCE_EN,
> +	.debounce_val	= OMAP24XX_GPIO_DEBOUNCE_VAL,
> +	.ctrl		= OMAP24XX_GPIO_CTRL,
> +	.syscfg		= OMAP24XX_GPIO_SYSCONFIG,
> +	.leveldetect0	= OMAP24XX_GPIO_LEVELDETECT0,
> +	.leveldetect1	= OMAP24XX_GPIO_LEVELDETECT1,
> +	.rise_detect	= OMAP24XX_GPIO_RISINGDETECT,
> +	.fall_detect	= OMAP24XX_GPIO_FALLINGDETECT,
> +	.rev_reg	= OMAP24XX_GPIO_REVISION,
> +};

Can we use just a omap specific shift here? Or is the register
ordering different too?

Tony

  parent reply	other threads:[~2010-04-01  9:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 12:23 [PATCH 0/8 RFC] OMAP: GPIO: Split OMAP1 and OMAP2PLUS Charulatha V
2010-03-31 12:23 ` [PATCH 1/8] OMAP:GPIO:Move architecture specific macros to specific header Charulatha V
2010-03-31 12:23   ` [PATCH 2/8] OMAP3:GPIO:Add support for early platform gpio device Charulatha V
2010-03-31 12:23     ` [PATCH 3/8] OMAP2:GPIO:Add " Charulatha V
2010-03-31 12:23       ` [PATCH 4/8] OMAP4:GPIO:Add " Charulatha V
2010-03-31 12:23         ` [PATCH 5/8] OMAP2PLUS:GPIO:Add OMAP2PLUS specific gpio support Charulatha V
2010-03-31 12:23           ` [PATCH 6/8] OMAP1:GPIO:Support for OMAP1 specific gpio Charulatha V
2010-03-31 12:23             ` [PATCH 7/8] OMAP2PLUS:GPIO:Move gpio_init from board files to init_common_hw Charulatha V
2010-03-31 12:23               ` [PATCH 8/8] OMAP:GPIO:Common platform code for all OMAPs Charulatha V
2010-04-01  9:34                 ` Tony Lindgren
2010-04-01  9:32               ` [PATCH 7/8] OMAP2PLUS:GPIO:Move gpio_init from board files to init_common_hw Tony Lindgren
2010-04-01 10:50                 ` Varadarajan, Charulatha
2010-04-06 22:13               ` Kevin Hilman
2010-04-01  9:30           ` [PATCH 5/8] OMAP2PLUS:GPIO:Add OMAP2PLUS specific gpio support Tony Lindgren
2010-04-06 22:08             ` Kevin Hilman
2010-04-01  7:26       ` [PATCH 3/8] OMAP2:GPIO:Add support for early platform gpio device Felipe Balbi
2010-04-01  8:53         ` Varadarajan, Charulatha
2010-04-01  8:58           ` Felipe Balbi
2010-04-01  9:16             ` Varadarajan, Charulatha
2010-04-01  7:23     ` [PATCH 2/8] OMAP3:GPIO:Add " Felipe Balbi
2010-04-01  8:58       ` Varadarajan, Charulatha
2010-04-01  9:12         ` Tony Lindgren
2010-04-01  9:19           ` Varadarajan, Charulatha
2010-04-01  9:13     ` Tony Lindgren [this message]
2010-04-01 10:49       ` Varadarajan, Charulatha
2010-04-01  9:31     ` Tony Lindgren
2010-04-01 10:50       ` Varadarajan, Charulatha
2010-04-01  7:17   ` [PATCH 1/8] OMAP:GPIO:Move architecture specific macros to specific header Felipe Balbi
2010-04-01  8:52     ` Varadarajan, Charulatha
2010-04-01  9:00       ` Felipe Balbi
2010-04-01  9:41       ` Tony Lindgren
2010-04-01 10:50         ` Varadarajan, Charulatha
2010-04-06 22:31 ` [PATCH 0/8 RFC] OMAP: GPIO: Split OMAP1 and OMAP2PLUS Kevin Hilman
2010-04-12 12:16   ` Varadarajan, Charulatha
2010-04-19 14:31     ` Kevin Hilman

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=20100401091357.GE31200@atomide.com \
    --to=tony@atomide.com \
    --cc=charu@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=rnayak@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