From: Andres Salomon <dilinger@collabora.co.uk>
To: Tobias_Mueller@twam.info
Cc: akpm@linux-foundation.org, Randy Dunlap <randy.dunlap@oracle.com>,
deepak@laptop.org, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org, linux-geode@lists.infradead.org,
jordan@cosmicpenguin.net, cjb@laptop.org
Subject: Re: [PATCH 1/2] cs5535-gpio: add AMD CS5535/CS5536 GPIO driver support
Date: Thu, 11 Jun 2009 11:16:10 -0400 [thread overview]
Message-ID: <20090611111610.0667898a@mycelium.queued.net> (raw)
In-Reply-To: <17be05570906110746l214f88cdh8570488e1be51b30@mail.gmail.com>
On Thu, 11 Jun 2009 16:46:35 +0200
Tobias Müller <Tobias_Mueller@twam.info> wrote:
> 2009/6/10 Andres Salomon <dilinger@collabora.co.uk>:
> > +config GPIO_CS5535
> > + tristate "AMD CS5535/CS5536 GPIO support"
> > + depends on PCI && !CS5535_GPIO && !MGEODE_LX
> > + help
> > + The AMD CS5535 and CS5536 southbridges support 28 GPIO
> > pins that
> > + can be used for quite a number of things. The CS5535/6
> > is found on
> > + AMD Geode and Lemote Yeeloong devices.
>
> Why do you depend on !MGEODE_LX? Are there any problems?
Because arch/x86/kernel/{mfgpt,geode}_32.c are built if
CONFIG_MGEODE_LX is set, and they will happily clobber each other. We
need to get a broken-out mfgpt driver completed, and then we can rework
or remove the arch/x86/kernel/{mfgpt,geode}_32.c stuff.
It's probably possible to add a separate config for that
(CONFIG_GEODE_LEGACY or something?) rather than having it depend upon
CONFIG_MGEODE_LX, but I haven't looked into it. I'd rather spend the
time fixing it correctly than fretting about with the various config
permutations. :)
next prev parent reply other threads:[~2009-06-11 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 4:10 [PATCH 1/2] cs5535-gpio: add AMD CS5535/CS5536 GPIO driver support Andres Salomon
2009-06-11 14:46 ` Tobias Müller
2009-06-11 15:16 ` Andres Salomon [this message]
2009-06-11 18:52 ` Tobias Müller
2009-06-11 20:00 ` Andres Salomon
2009-06-11 20:11 ` Tobias Müller
2009-06-11 21:28 ` Andres Salomon
2009-06-11 21:35 ` Tobias Müller
2009-06-13 0:23 ` Andres Salomon
2009-06-20 10:20 ` Tobias Müller
2009-07-01 22:32 ` David Brownell
2009-08-15 10:59 ` Tobias Müller
2009-08-18 4:43 ` Andres Salomon
2009-08-18 8:32 ` Tobias Müller
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=20090611111610.0667898a@mycelium.queued.net \
--to=dilinger@collabora.co.uk \
--cc=Tobias_Mueller@twam.info \
--cc=akpm@linux-foundation.org \
--cc=cjb@laptop.org \
--cc=deepak@laptop.org \
--cc=jordan@cosmicpenguin.net \
--cc=linux-geode@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=tiwai@suse.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