public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 1/2] GPIO: Tegra2: add GPIO driver for Tegra2
Date: Tue, 3 May 2011 18:49:09 +0200 (CEST)	[thread overview]
Message-ID: <a9429252bd44c51eb61d27cb3ba6f1e8.squirrel@ssl.serverraum.org> (raw)

Am Di, 3.05.2011, 00:45, schrieb Tom Warren:
> Signed-off-by: Tom Warren <twarren@nvidia.com>
> ---
> Changes in V2:
> 	- use 'gpio_pin' enum in gpio.h (Simon Glass review request)
> 	- change 'GPIO_PORT8' to 'GPIO_FULLPORT' (Simon Glass request)
> 	- change 'offset' to 'pin' globally
>
>  arch/arm/include/asm/arch-tegra2/gpio.h |  244
++++++++++++++++++++++++-
>  drivers/gpio/Makefile                   |    1 +
>  drivers/gpio/tegra2_gpio.c              |  299

Does this (SoC) driver belong to drivers/gpio/ or
arch/arm/cpu/armv7/tegra2/? To me it seems that both are used for
architectures/SoCs specific drivers (eg. blackfin, omap in arch/ and at91
in drivers/gpio/). What is the preferred directory?

-- 
Michael

             reply	other threads:[~2011-05-03 16:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03 16:49 Michael Walle [this message]
2011-05-03 19:29 ` [U-Boot] [PATCH V2 1/2] GPIO: Tegra2: add GPIO driver for Tegra2 Mike Frysinger
2011-06-02 20:00   ` Tom Warren
2011-06-02 20:56     ` Wolfgang Denk
2011-06-02 21:30       ` Tom Warren
2011-06-02 21:34         ` Wolfgang Denk
2011-06-02 21:55           ` Tom Warren
2011-06-03  4:36             ` Wolfgang Denk
2011-06-03  4:55             ` Mike Frysinger
2011-06-03  4:53         ` Mike Frysinger
2011-06-03 16:01           ` Tom Warren
  -- strict thread matches above, loose matches on Subject: below --
2011-05-02 22:45 [U-Boot] [PATCH V2 0/2] " Tom Warren
2011-05-02 22:45 ` [U-Boot] [PATCH V2 1/2] " Tom Warren
2011-05-02 23:15   ` Mike Frysinger
2011-05-02 23:16     ` Tom Warren

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=a9429252bd44c51eb61d27cb3ba6f1e8.squirrel@ssl.serverraum.org \
    --to=michael@walle.cc \
    --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