linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: GPIO support for HTC Dream
Date: Wed, 09 Dec 2009 08:18:15 -0800	[thread overview]
Message-ID: <1260375495.23633.175.camel@desktop> (raw)
In-Reply-To: <20091209113739.GC22752@elf.ucw.cz>

On Wed, 2009-12-09 at 12:37 +0100, Pavel Machek wrote:
> On Tue 2009-12-08 16:39:09, Arve Hj?nnev?g wrote:
> > On Tue, Dec 8, 2009 at 2:45 PM, Russell King - ARM Linux
> > <linux@arm.linux.org.uk> wrote:
> > > On Tue, Dec 08, 2009 at 11:28:43AM +0100, Pavel Machek wrote:
> > >> Add GPIO support for HTC Dream.
> > >>
> > >> Signed-off-by: Pavel Machek <pavel@ucw.cz>
> > >>
> > >> diff --git a/arch/arm/mach-msm/Kconfig b/arch/arm/mach-msm/Kconfig
> > >> index f780086..774c50e 100644
> > >> --- a/arch/arm/mach-msm/Kconfig
> > >> +++ b/arch/arm/mach-msm/Kconfig
> > >> @@ -40,4 +40,8 @@ config MACH_TROUT
> > >>       help
> > >>         Support for the HTC Dream, T-Mobile G1, Android ADP1 devices.
> > >>
> > >> +config GENERIC_GPIO
> > >> +     bool
> > >> +     default y
> > >
> > > Please arrange for this to be handled just like every other ARM
> > > platform via a 'select' statement - eg:
> > >
> > > config ARCH_AT91
> > >        bool "Atmel AT91"
> > >        select GENERIC_GPIO
> > >        select ARCH_REQUIRE_GPIOLIB
> > >        select HAVE_CLK
> > >
> > > It is not nice to have multiple definitions of the same symbol scattered
> > > throughout the Kconfig files.
> > >
> > 
> > Why did this code get pulled into the dream gpio code? The original
> > change that adds msm gpio support already selects GENERIC_GPIO
> > (http://android.git.kernel.org/?p=kernel/msm.git;a=commit;h=5ae9f4403530a5782478c35d29753081750c4188).
> > Since you copied half of the files from that change anyway, it would
> > be better to just include that change in you patch set.
> 
> I'm not sure how to do that with git without pulling all the changes
> before that one, too :-(.

I'm going to end up pulling a lot of these git commit into my git tree.
It would be pretty easy for me to just pull this GPIO change directly ..
I assume you haven't found a way to work with git that suites you? It
would be best if you used git, but I could try to do some sort of quilt
export if that works better for you.

Daniel

  parent reply	other threads:[~2009-12-09 16:18 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-08 10:28 GPIO support for HTC Dream Pavel Machek
2009-12-08 20:22 ` Ryan Mallon
2009-12-08 21:37   ` Pavel Machek
2009-12-08 21:53     ` Ryan Mallon
2009-12-10 16:26       ` Pavel Machek
2009-12-08 21:56     ` Arve Hjønnevåg
2009-12-09 11:32       ` Pavel Machek
2009-12-08 21:46   ` Pavel Machek
2009-12-08 22:03     ` Joe Perches
2009-12-09 11:46       ` Pavel Machek
2009-12-08 22:10     ` Ryan Mallon
2009-12-09 23:40       ` Ryan Mallon
2009-12-10 17:24         ` Pavel Machek
2009-12-10 17:41           ` Mark Brown
2009-12-10 19:49           ` Ryan Mallon
2009-12-10 23:14             ` H Hartley Sweeten
2009-12-11 19:58               ` Pavel Machek
2009-12-11 22:10               ` Pavel Machek
2009-12-11 22:40                 ` Arve Hjønnevåg
2009-12-11 23:12                   ` H Hartley Sweeten
2009-12-16 22:53                     ` Pavel Machek
2009-12-16 23:03                       ` Daniel Walker
2009-12-11 23:04                 ` H Hartley Sweeten
2009-12-14  6:45                   ` Pavel Machek
2009-12-14 17:54                     ` Daniel Walker
2009-12-14 18:12                       ` H Hartley Sweeten
2009-12-15  6:40                         ` Arve Hjønnevåg
2009-12-15 19:12                           ` Pavel Machek
2009-12-15 20:07                             ` Daniel Walker
2009-12-15 21:21                               ` Pavel Machek
2009-12-15 20:48                         ` Jamie Lokier
2009-12-15 21:07                           ` Brian Swetland
2009-12-14 19:00                     ` H Hartley Sweeten
2009-12-15 19:47                       ` Pavel Machek
2009-12-15 20:15                         ` H Hartley Sweeten
2009-12-15 20:47                           ` Pavel Machek
2009-12-15 21:16                           ` [patch] " Pavel Machek
2009-12-25 17:10                             ` Pavel Machek
2009-12-25 23:49                               ` Daniel Walker
2009-12-26  8:51                                 ` Pavel Machek
2009-12-15 20:24                         ` Ryan Mallon
2009-12-15 20:44                           ` Pavel Machek
2009-12-15  6:48                     ` Arve Hjønnevåg
2009-12-11 23:28                 ` Russell King - ARM Linux
2009-12-11 23:50                   ` H Hartley Sweeten
2009-12-14  6:24                   ` Pavel Machek
2009-12-10 16:57       ` Pavel Machek
2009-12-08 22:45 ` Russell King - ARM Linux
2009-12-09  0:39   ` Arve Hjønnevåg
2009-12-09 11:37     ` Pavel Machek
2009-12-09 11:42       ` Arve Hjønnevåg
2009-12-10 16:27         ` Pavel Machek
2009-12-09 16:18       ` Daniel Walker [this message]
2009-12-13 21:29         ` Pavel Machek
2009-12-13 21:38           ` Brian Swetland
2009-12-15 19:09             ` Pavel Machek
2009-12-14 17:40           ` Daniel Walker
2009-12-15 19:10             ` Pavel Machek
2009-12-09 11:41   ` Pavel Machek

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=1260375495.23633.175.camel@desktop \
    --to=dwalker@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).