public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ajay Bhargav <ajay.bhargav@einfochips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] gpio: Adds GPIO driver support for Armada100
Date: Wed, 20 Jul 2011 11:06:38 +0530 (IST)	[thread overview]
Message-ID: <1207509190.33599.1311140198703.JavaMail.root@ahm.einfochips.com> (raw)
In-Reply-To: <814164661.33093.1311137863843.JavaMail.root@ahm.einfochips.com>


----- "Prafulla Wadaskar" <prafulla@marvell.com> wrote:

> 
> That can be thought of while adding support for othe SoCs.
> Preferably define register struct in asm/arch/gpio.h
> 
> Regards..
> Prafulla . .
> 

..snip.. (quoting from another reply..)
> You have to follow all :-), more reviewers more better code output.
> BASE+OFFSET strictly not recommended.

> I think lei and me are suggesting similar things, macros should be used precisely, the code should be small and smarter.

Hi Prafulla,

I agree that macros make code look smaller and smarter. Now if you see the registers of GPIO they are not in order, I mean i cannot group together particular gpio set. can i do it this way, 

e.g. 
struct armdgpio_gplr_register {
    u32 gplr0;
    u32 gplr1;
    u32 gplr2;
    u8 pad[some_value]; //this padding is going to be big
    u32 gplr3;
}

then while using this particular set i can just use ARMD1_GPLR_BASE ( = ARMD1_GPIO_BASE + GPLR_OFFSET). moreover i am not using all the registers so i define only those register sets which are in use. what you say about this?

Regards,
Ajay Bhargav

       reply	other threads:[~2011-07-20  5:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <814164661.33093.1311137863843.JavaMail.root@ahm.einfochips.com>
2011-07-20  5:36 ` Ajay Bhargav [this message]
2011-07-20  6:02   ` [U-Boot] [PATCH 1/4] gpio: Adds GPIO driver support for Armada100 Wolfgang Denk
2011-07-20  6:36     ` Ajay Bhargav
2011-07-20 10:08       ` Lei Wen
2011-07-20 10:43         ` Ajay Bhargav
2011-07-20 12:18           ` Lei Wen
2011-07-20 12:20             ` Ajay Bhargav
2011-07-20 12:19           ` Wolfgang Denk
2011-07-20 12:09       ` Wolfgang Denk
     [not found] <1287709675.34262.1311146613076.JavaMail.root@ahm.einfochips.com>
2011-07-20  7:29 ` Ajay Bhargav
2011-07-20  7:48   ` Lei Wen
2011-07-20  7:54     ` Ajay Bhargav
     [not found] <952685375.34177.1311145646630.JavaMail.root@ahm.einfochips.com>
2011-07-20  7:14 ` Ajay Bhargav
2011-07-20  7:28   ` Lei Wen
     [not found] <550445252.29883.1311070783386.JavaMail.root@ahm.einfochips.com>
2011-07-19 10:29 ` Ajay Bhargav
2011-07-19 17:36   ` Prafulla Wadaskar
2011-07-20  7:13   ` Lei Wen
2011-07-18  9:41 Ajay Bhargav
2011-07-18 17:45 ` Mike Frysinger
2011-07-18 19:01 ` Prafulla Wadaskar
2011-07-19  4:04   ` Lei Wen
2011-07-19  4:01     ` Ajay Bhargav
2011-07-19  4:14       ` Lei Wen
2011-07-19  4:14         ` Ajay Bhargav
2011-07-20  3:49           ` Prafulla Wadaskar
2011-07-19  5:27     ` Wolfgang Denk
2011-07-19  5:55       ` Lei Wen
2011-07-19  4:23   ` Ajay Bhargav
2011-07-19 17:36     ` Prafulla Wadaskar
2011-07-20  7:11     ` Lei Wen

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=1207509190.33599.1311140198703.JavaMail.root@ahm.einfochips.com \
    --to=ajay.bhargav@einfochips.com \
    --cc=u-boot@lists.denx.de \
    /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