From: Ajay Bhargav <ajay.bhargav@einfochips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] gpio: Add GPIO driver for Marvell SoC Armada100
Date: Mon, 25 Jul 2011 10:45:38 +0530 (IST) [thread overview]
Message-ID: <1939544051.460.1311570938194.JavaMail.root@ahm.einfochips.com> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D19FB089D26@SC-VEXCH4.marvell.com>
----- "Prafulla Wadaskar" <prafulla@marvell.com> wrote:
> The main objective of having mvgpio.c is to share/reuse a driver code
> across several SoCs.
>
> If most of the SoCs (what we know) have similar register definition,
> it makes sense to keep them in mvgpio.c
>
> What may differ for each SOC is that- base addresses, number of GPIOs,
> number of GPIO Banks, that should go in asm/arch/gpio.h
>
> If any future SoC follows totally different GPIO architecture, we can
> always have _gpio.c.
>
> Regards..
> Prafulla . .
>
So what about v2 patches i sent? I did things accordingly you said.
can you please review them and let me know if any changes are required.
Regards,
Ajay Bhargav
next prev parent reply other threads:[~2011-07-25 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1727751274.46180.1311328869198.JavaMail.root@ahm.einfochips.com>
2011-07-22 10:03 ` [U-Boot] [PATCH v2 2/2] gpio: Add GPIO driver for Marvell SoC Armada100 Ajay Bhargav
2011-07-22 17:17 ` Prafulla Wadaskar
2011-07-25 5:15 ` Ajay Bhargav [this message]
2011-07-29 4:24 ` Ajay Bhargav
[not found] <416881811.45805.1311324803475.JavaMail.root@ahm.einfochips.com>
2011-07-22 8:57 ` Ajay Bhargav
2011-07-22 9:47 ` Lei Wen
2011-07-22 7:16 Ajay Bhargav
2011-07-22 7:30 ` Lei Wen
2011-07-22 7:27 ` Ajay Bhargav
2011-07-22 7:52 ` 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=1939544051.460.1311570938194.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.