From: andrew may <acmay@acmay.homeip.net>
To: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
Cc: andrew may <acmay@acmay.homeip.net>,
linuxppc-embedded@lists.linuxppc.org,
Armin Kuster <akuster@mvista.com>
Subject: Re: [PATCH] ibm ocp gpio
Date: Tue, 21 May 2002 09:08:19 -0700 [thread overview]
Message-ID: <20020521090819.G9190@ecam.san.rr.com> (raw)
In-Reply-To: <3CEA0F45.BDBBA25@etx.ericsson.se>
On Tue, May 21, 2002 at 11:11:33AM +0200, Kenneth Johansson wrote:
> andrew may wrote:
> >
> > The most common thing I want to use the GPIO pins for is
> > simple lighting of some LED's. I decided to roll in some timers
> > into the generic GPIO driver rather than haveing each user of the
> > GPIO driver be forced to do some form of timers to get a usable
> > LED visual as well.
> >
> > I think I got the timer stuff correct but I am not sure.
> > I didn't bother cleaning it up until I get some feedback on it.
>
> I don't think we should add this It's not really something that needs to be
> done in the driver. Also you have not exported this functionality to
> userspace.
Well no it doesn't need to be in the driver, but you then are forced with
having every other driver doing there own timer to turn off the bit rather
than having one timer take care of them all. And do you really want to
have you UserSpace app wake up and do an ioctl just to turn off an LED
a quarter second after you turn it on?
As I said I didn't clean it up. That would include not having it exported
as an ioctl or having the symbol export to modules. Or making it a config
option to compile it out if you are worried about the size of the code.
Or removing the extra printk's.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-21 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 1:26 [PATCH] ibm ocp gpio andrew may
2002-05-21 9:11 ` Kenneth Johansson
2002-05-21 16:08 ` andrew may [this message]
2002-05-21 16:28 ` Kenneth Johansson
2002-05-21 18:26 ` andrew may
2002-05-22 10:58 ` Kenneth Johansson
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=20020521090819.G9190@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=akuster@mvista.com \
--cc=kenneth.johansson@etx.ericsson.se \
--cc=linuxppc-embedded@lists.linuxppc.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).