From: Ben Nizette <bn@niasdigital.com>
To: Markus Brunner <super.firetwister@googlemail.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: UIO not working on ppc405 onchip registers
Date: Tue, 22 Jul 2008 16:42:47 +1000 [thread overview]
Message-ID: <1216708967.4004.238.camel@moss.renham> (raw)
In-Reply-To: <20080722061730.GB12576@digi.com>
Hey Markus,
> >
> > +config UIO_GPIO
> > + tristate "Driver for PPC_4xx GPIO"
As an aside, you sure you want to do this anyway? I'd suggest that you
just do a gpio chip driver for this, tie it in to gpiolib and use the
gpiolib user interface (which IIRC has only made it as far as -mm but is
on the way up). This gives kernel internals nice access to the pins as
well through the standard gpio framework.
Thanks :-)
--Ben.
next prev parent reply other threads:[~2008-07-22 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 19:52 UIO not working on ppc405 onchip registers Markus Brunner
2008-07-22 6:17 ` Uwe Kleine-König
2008-07-22 6:42 ` Ben Nizette [this message]
2008-07-22 7:48 ` super.firetwister
2008-07-22 7:52 ` Ben Nizette
2008-09-05 6:18 ` Markus Brunner
2008-07-22 7:47 ` super.firetwister
2008-07-22 16:20 ` super.firetwister
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=1216708967.4004.238.camel@moss.renham \
--to=bn@niasdigital.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=super.firetwister@googlemail.com \
/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).