From: Ajay Bhargav <ajay.bhargav@einfochips.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] gpio: Add GPIO driver framework for Marvell SoCs
Date: Wed, 3 Aug 2011 10:10:00 +0530 (IST) [thread overview]
Message-ID: <160480648.39359.1312346400264.JavaMail.root@ahm.einfochips.com> (raw)
In-Reply-To: <1990439524.39318.1312346163802.JavaMail.root@ahm.einfochips.com>
----- "Simon Guinot" <simon@sequanux.org> wrote:
> AFAIK, Orion and Kirkwood SoCs don't provide bitwise set/clear for
> GPIO output/direction registers. Instead, a register must be read
> first to leave other bits unchanged (see __set_direction in
> kw_gpio.c).
>
> Is it possible to handle Armada SoCs GPIOs in a same way ? maybe
> using
> the pin registers (gpxx in the Armada struct gpio_reg array) ?
>
> If not, this code is not Marvell generic but rather specific for
> Armada
> SoCs and then maybe armada_gpio is a better name...
>
> Regards,
>
> Simon
Hi Simon,
Yes its possible to implement code that way, Armada SoC does have GPIO
registers for set/clear. what about register naming?? I think they are
different for Kirkwood and Orion.
One more thing which can be done to make this code generic is to have
some macros which can be defined by individual arch for specific registers
which are going to be in use e.g.
#define GPIO_PIN_LEVEL_REG
#define GPIO_DIR_REG
#define GPIO_PIN_SET_REG
#define GPIO_PIN_CLR_REG
so anyone can have their own version of these registers in gpio.h of their
arch. The only thing which can complicate this is banking of registers, no.
of banks etc.
Please provide comments on this, so we can have a better code.
Thanks & Regards,
Ajay Bhargav
next parent reply other threads:[~2011-08-03 4:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1990439524.39318.1312346163802.JavaMail.root@ahm.einfochips.com>
2011-08-03 4:40 ` Ajay Bhargav [this message]
2011-08-04 0:04 ` [U-Boot] [PATCH v2 1/2] gpio: Add GPIO driver framework for Marvell SoCs Simon Guinot
2011-08-04 8:51 ` Albert ARIBAUD
2011-08-04 9:18 ` Lei Wen
[not found] <2088605993.55298.1312607122087.JavaMail.root@ahm.einfochips.com>
2011-08-06 5:10 ` Ajay Bhargav
2011-08-07 2:16 ` Prafulla Wadaskar
[not found] <1874826476.47235.1312454749903.JavaMail.root@ahm.einfochips.com>
2011-08-04 10:51 ` Ajay Bhargav
2011-08-04 11:25 ` Prafulla Wadaskar
2011-08-04 12:51 ` Lei Wen
2011-07-22 7:16 Ajay Bhargav
2011-08-02 14:10 ` Simon Guinot
2011-08-03 10:18 ` Prafulla Wadaskar
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=160480648.39359.1312346400264.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