public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Tobias_Mueller@twam.info
Cc: jordan@cosmicpenguin.net, dilinger@collabora.co.uk,
	david-b@pacbell.net, gardner.ben@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 001/001] gpio: AMD CS5535/CS5536 GPIO driver
Date: Tue, 2 Jun 2009 13:33:12 -0700	[thread overview]
Message-ID: <20090602133312.68158cd5.akpm@linux-foundation.org> (raw)
In-Reply-To: <17be05570906020114k7f2a3096h48335d509951cf90@mail.gmail.com>

On Tue, 2 Jun 2009 10:14:45 +0200
Tobias M__ller <Tobias_Mueller@twam.info> wrote:

> 2009/6/2 Jordan Crouse <jordan@cosmicpenguin.net>:
> > Andres Salomon wrote:
> >> As far as Tobias's driver, one major difference between our drivers is
> >> that mine doesn't grab the entire PCI device.  This is because other
> >> drivers (ie, the MFGPT driver) will want to share the PCI device.
> >
> > Also SMBUS. In fact, they *must* share the PCI device if they all want to
> > play well together, so that alone would probably push us toward Andre's
> > patch, once it gets clean.
> 
> I had SMBUS and my driver tested in parallel and there I didn't found any
> problems. But I would be fine if we would use Andre's patch. I haven't know
> about, so that's why I tried my own. :)
> 
> I see some other problem's on Andre's patch:
> - He allows the use of PIN 23 which is reserved
> - No special handling is done for 28, which is a GPIO, but
>   serves as Power Button as well
> - OUT_AUX1/OUT_AUX2 should be disabled by default
>   if pin is configured as in output
> - IN_AUX should be disabled by default is pin is
>   configured as in input
> 
> And, if I request a GPIO by userspace via sysfs, on my system it's an
> input pin by default. So my driver initializes a GPIO as an input by default.
> But I don't know if this is default or system specific. I didn't found anything
> about this in the gpio docs.
> 
> So maybe we should decide whether we take Andre's or my approach
> and then adjust it.
> 

I think I'll drop gpio-amd-cs5535-cs5536-gpio-driver.patch while you
guys sort all this out, please.


  reply	other threads:[~2009-06-02 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23 11:53 [PATCH 001/001] gpio: AMD CS5535/CS5536 GPIO driver Tobias Müller
2009-05-26 22:16 ` Andrew Morton
2009-05-30 18:05   ` [PATCH v2 " Tobias Müller
2009-06-01 23:54     ` Andrew Morton
2009-06-02  0:08       ` Andres Salomon
2009-06-02  3:02         ` Jordan Crouse
2009-06-02  8:14           ` Tobias Müller
2009-06-02 20:33             ` Andrew Morton [this message]
2009-06-09 12:27               ` Tobias Müller
2009-06-10  4:00                 ` Andres Salomon
2009-06-02  0:02     ` Andrew Morton

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=20090602133312.68158cd5.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Tobias_Mueller@twam.info \
    --cc=david-b@pacbell.net \
    --cc=dilinger@collabora.co.uk \
    --cc=gardner.ben@gmail.com \
    --cc=jordan@cosmicpenguin.net \
    --cc=linux-kernel@vger.kernel.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