From: Andres Salomon <dilinger@collabora.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
cjb@laptop.org, deepak@laptop.org,
linux-geode@lists.infradead.org,
Jordan Crouse <jordan@cosmicpenguin.net>,
Tobias_Mueller@twam.info
Subject: Re: [PATCH 1/3] cs5535-gpio: add AMD CS5535/CS5536 GPIO driver support
Date: Thu, 20 Aug 2009 12:40:02 -0400 [thread overview]
Message-ID: <20090820124002.58d3d25b@mycelium.queued.net> (raw)
In-Reply-To: <s5hd46qo6j3.wl%tiwai@suse.de>
On Thu, 20 Aug 2009 17:21:20 +0200
Takashi Iwai <tiwai@suse.de> wrote:
> At Tue, 18 Aug 2009 17:53:14 -0400,
> Andres Salomon wrote:
> >
> >
> > This creates a CS5535/CS5536 GPIO driver which uses a gpio_chip
> > backend (allowing GPIO users to use the generic GPIO API if
> > desired) while also allowing architecture-specific users directly
> > (via the cs5535_gpio_* functions).
>
> Will be any user of cs5535_gpio_*() expected? If not, it'd be better
> not to export stuff, IMO.
>
The olpc-dcon driver, for one. If desired, I can remove the exports
for now.
> > Tested on an OLPC machine. Some Leemotes also use CS5536 (with a
> > mips cpu), which is why this is in drivers/gpio rather than
> > arch/x86. Currently, it conflicts with older geode GPIO support;
> > once MFGPT support is reworked to also be more generic, the older
> > geode code will be removed.
>
> .... or you can rewrite the old driver to use the functions above?
> Then the ugly Kconfig check can be dropped, too. (yeah that's an
> answer to my own question above.)
I guess in theory I could..
>
> BTW CONFIG_GPIO_CS5536 and CONFIG_CS5536_GPIO are so confusing... :)
>
Agreed. I'd really like CONFIG_CS5535_GPIO to go away, but first there
needs to be a replacement. CONFIG_CS5535_GPIO will probably also need
to be marked DEPRECATED for a while, too, since it's a
userspace-visible change. I can follow up w/ a patch for that once
people are happy w/ this current set of patches.
> > Signed-off-by: Andres Salomon <dilinger@collabora.co.uk>
>
> I can happily merge this patch series to sound GIT tree if no one
> objects, since it's basically for OLPC sound stuff.
>
>
> thanks,
>
> Takashi
next prev parent reply other threads:[~2009-08-20 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 21:53 [PATCH 1/3] cs5535-gpio: add AMD CS5535/CS5536 GPIO driver support Andres Salomon
2009-08-19 19:13 ` Andres Salomon
2009-08-20 15:21 ` Takashi Iwai
2009-08-20 16:40 ` Andres Salomon [this message]
2009-08-20 17:03 ` Martin-Éric Racine
2009-08-20 17:27 ` Andres Salomon
2009-08-20 19:35 ` Takashi Iwai
2009-08-20 19:37 ` Takashi Iwai
2009-08-23 9:22 ` Alessandro Zummo
2009-08-28 19:51 ` Andres Salomon
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=20090820124002.58d3d25b@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=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