From: Marc Pignat <marc.pignat@hevs.ch>
To: Florian Fainelli <florian.fainelli@telecomint.eu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC, PATCH, take 2] watchdog on generic gpio
Date: Mon, 14 Jan 2008 15:59:38 +0100 [thread overview]
Message-ID: <200801141559.38781.marc.pignat@hevs.ch> (raw)
In-Reply-To: <200801141503.15359.florian.fainelli@telecomint.eu>
On Monday 14 January 2008, Florian Fainelli wrote:
> Le lundi 14 janvier 2008, Marc Pignat a écrit :
> > Hi Florian!
> > I understand your wish, but...
> > You told me that your plaform doesn't implement the generic gpio interface
> > (yet?), so this driver can't work for you.
>
> You understood me wrong, I told you that not all platforms, actually only
> AVR32 and ARM seem to make use of David Brownell's gpiolib, but the MIPS
> board I am working with supports the "old" generic GPIO API which required
> you to define your own wrappers for gpio_set/get_value and such. For both
> implementations the config symbol is GENERIC_GPIO, which can somehow be
> confusing.
The gpiolib isn't merged yet and it's purpose it to let use any gpio in the
system independently of how they are connected (directly, or through spi, ...).
So I don't use it!
...
> I use only one gpio bit as well, only the keepalive function should be
> changed. And even if we need the other ones to be changed, let's assume we
> can pass the necessary callback to the platform driver, and checking wether
> they are defined and call them or not is just trivial. This will not bloat
> the driver.
Okay, so what do you do with this single pin?
...
> Yes, I understand, but having a max823-centric driver does not make it as
> general as it could be.
Sure. Another solution is to make add a .type in the gpio_wdt struct to choose
which function to use for keepalive -> support for more chips in the driver
itself.
>
> >
> > Let me know if you want some help implementing your driver!
>
> It already exists and his merged as mtx1_wdt, I just want to get rid of it if
> any generic gpio wathchdog driver can fit my needs and others.
I just had a look at it. It has additionnal restrictions like 'It should not
be triggered more often than 1.6 seconds', ..., and works with a timer, it
is really very differrent of what I'm doing...
Can you please tell me what is connected to this gpio?
>
> As a general comments, Wim did not answer yet, I would like to hear from him.
Me too :)
Regards
Marc
next prev parent reply other threads:[~2008-01-14 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 10:03 Marc Pignat
2008-01-14 11:06 ` Florian Fainelli
2008-01-14 13:01 ` Marc Pignat
2008-01-14 14:03 ` Florian Fainelli
2008-01-14 14:59 ` Marc Pignat [this message]
2008-01-14 15:57 ` Haavard Skinnemoen
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=200801141559.38781.marc.pignat@hevs.ch \
--to=marc.pignat@hevs.ch \
--cc=florian.fainelli@telecomint.eu \
--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
Powered by JetHome