From: Benoit Cousson <b-cousson@ti.com>
To: "Varadarajan, Charulatha" <charu@ti.com>
Cc: "david-b@pacbell.net" <david-b@pacbell.net>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"paul@pwsan.com" <paul@pwsan.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH 10/13 v3] OMAP: GPIO: Add gpio dev_attr and correct clks in OMAP4 hwmod struct
Date: Tue, 15 Jun 2010 18:40:08 +0200 [thread overview]
Message-ID: <4C17ACE8.6000805@ti.com> (raw)
In-Reply-To: <1276614348-5201-11-git-send-email-charu@ti.com>
Hi Charu,
On 6/15/2010 5:05 PM, Varadarajan, Charulatha wrote:
> From: Charulatha V<charu@ti.com>
>
> This patch adds gpio_dev_attr to OMAP4 gpio hwmod structure. This patch
> also corrects the gpio .main_clk and .clk fields in gpio hwmod structures.
>
> Signed-off-by: Charulatha V<charu@ti.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 37 +++++++++++++++++++---------
> 1 files changed, 25 insertions(+), 12 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 20f5f8c..b4c0878 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -22,6 +22,7 @@
>
> #include<plat/omap_hwmod.h>
> #include<plat/cpu.h>
> +#include<plat/gpio.h>
>
> #include "omap_hwmod_common_data.h"
>
> @@ -1272,6 +1273,12 @@ static struct omap_hwmod omap44xx_fdif_hwmod = {
> * general purpose io module
> */
>
> +static struct omap_gpio_dev_attr gpio_dev_attr = {
> + .gpio_bank_count = 6,
Why do you need that information?
The point is that this struct is in theory a per instance data not a
global one. If needed, you should be able to get that from the number of
iteration done during the init of hwmods.
> + .gpio_bank_bits = 32,
> + .dbck_flag = true,
> +};
Since this structure is the same than OMAP3, you should maybe consider
sharing it.
> +
> static struct omap_hwmod_class_sysconfig omap44xx_gpio_sysc = {
> .rev_offs = 0x0000,
> .sysc_offs = 0x0010,
> @@ -1305,7 +1312,7 @@ static struct omap_hwmod_addr_space omap44xx_gpio1_addrs[] = {
> static struct omap_hwmod_ocp_if omap44xx_l4_wkup__gpio1 = {
> .master =&omap44xx_l4_wkup_hwmod,
> .slave =&omap44xx_gpio1_hwmod,
> - .clk = "l4_wkup_clk_mux_ck",
> + .clk = "gpio1_ick",
> .addr = omap44xx_gpio1_addrs,
> .addr_cnt = ARRAY_SIZE(omap44xx_gpio1_addrs),
> .user = OCP_USER_MPU | OCP_USER_SDMA,
> @@ -1325,7 +1332,7 @@ static struct omap_hwmod omap44xx_gpio1_hwmod = {
> .class =&omap44xx_gpio_hwmod_class,
> .mpu_irqs = omap44xx_gpio1_irqs,
> .mpu_irqs_cnt = ARRAY_SIZE(omap44xx_gpio1_irqs),
> - .main_clk = "gpio1_ick",
> + .main_clk = NULL,
Removing the line is enough. It will be null by default.
I'm still not 100% sure that this is the good way to control the GPIO
module mode, but at least this is cleaner than the previous clock mapping.
Benoit
next prev parent reply other threads:[~2010-06-15 16:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 15:05 [PATCH 00/13 v3] OMAP: GPIO: Implement GPIO in HWMOD way Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 01/13 v3] OMAP: GPIO: Modify init() in preparation for platform device implementation Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 02/13 v3] OMAP: GPIO: Populate GPIO base address in omapxxxx.h Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 03/13 v3] OMAP: GPIO: Include platform_data structure for GPIO Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 04/13 v3] OMAP: GPIO: Introduce support for OMAP15xx chip GPIO init Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 05/13 v3] OMAP: GPIO: Introduce support for OMAP16xx " Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 06/13 v3] OMAP: GPIO: Introduce support for OMAP7xx " Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 07/13 v3] OMAP: GPIO: add GPIO hwmods structures for OMAP3 Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 08/13 v3] OMAP: GPIO: add GPIO hwmods structures for OMAP242X Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 09/13 v3] OMAP: GPIO: add GPIO hwmods structures for OMAP243X Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 10/13 v3] OMAP: GPIO: Add gpio dev_attr and correct clks in OMAP4 hwmod struct Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 11/13 v3] OMAP: GPIO: Introduce support for OMAP2PLUS chip GPIO init Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 12/13 v3] OMAP: GPIO: Implement GPIO as a platform device Varadarajan, Charulatha
2010-06-15 15:05 ` [PATCH 13/13 v3] OMAP: GPIO: Remove omap_gpio_init() Varadarajan, Charulatha
2010-06-16 20:34 ` [PATCH 12/13 v3] OMAP: GPIO: Implement GPIO as a platform device Benoit Cousson
2010-06-21 16:02 ` Varadarajan, Charulatha
2010-06-15 17:22 ` [PATCH 11/13 v3] OMAP: GPIO: Introduce support for OMAP2PLUS chip GPIO init Benoit Cousson
2010-06-16 6:55 ` Varadarajan, Charulatha
2010-06-16 7:21 ` Shilimkar, Santosh
2010-06-16 8:46 ` Varadarajan, Charulatha
2010-06-16 9:35 ` Cousson, Benoit
2010-06-16 9:06 ` Cousson, Benoit
2010-06-16 15:43 ` Varadarajan, Charulatha
2010-06-17 16:34 ` Kevin Hilman
2010-06-21 15:53 ` Varadarajan, Charulatha
2010-06-15 16:40 ` Benoit Cousson [this message]
2010-06-16 6:54 ` [PATCH 10/13 v3] OMAP: GPIO: Add gpio dev_attr and correct clks in OMAP4 hwmod struct Varadarajan, Charulatha
2010-06-16 8:57 ` Cousson, Benoit
2010-06-16 15:41 ` Varadarajan, Charulatha
2010-06-16 20:25 ` Benoit Cousson
2010-06-17 16:42 ` Kevin Hilman
2010-06-22 13:30 ` Varadarajan, Charulatha
2010-06-22 14:35 ` Kevin Hilman
2010-06-24 8:44 ` [PATCH 07/13 v3] OMAP: GPIO: add GPIO hwmods structures for OMAP3 DebBarma, Tarun Kanti
2010-06-17 20:23 ` [PATCH 04/13 v3] OMAP: GPIO: Introduce support for OMAP15xx chip GPIO init Kevin Hilman
2010-06-21 10:52 ` Varadarajan, Charulatha
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=4C17ACE8.6000805@ti.com \
--to=b-cousson@ti.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=charu@ti.com \
--cc=david-b@pacbell.net \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--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).