linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Nizette <bn@niasdigital.com>
To: 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 17:52:50 +1000	[thread overview]
Message-ID: <1216713170.4004.243.camel@moss.renham> (raw)
In-Reply-To: <200807220948.51053.super.firetwister@gmail.com>


On Tue, 2008-07-22 at 09:48 +0200, super.firetwister@googlemail.com
wrote:
> On Tuesday 22 July 2008, Ben Nizette wrote:
> 
> > As an aside, you sure you want to do this anyway?  
> 
> No ;)
> 
> 
> > 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.
> 
> This was just an example to make it others easier to reproduce my problem. My 
> goal is to have a soft spi driver in userspace, which would probably be 
> slower if it uses gpiolib. This driver is integrated in the application I 
> want to port to Linux. 

Ah right, cool.  I donno what the speed would be like, but both David
Brownell and Michael Buesch both have spi-over-gpio patches floating
around (eg [1]).  That, plus the spidev interface, might at least be
worth a try..?

But I'll let you get back to solving the UIO problem at hand :-D

	--Ben.

[1] http://lwn.net/Articles/290066/


  reply	other threads:[~2008-07-22  7:52 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
2008-07-22  7:48     ` super.firetwister
2008-07-22  7:52       ` Ben Nizette [this message]
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=1216713170.4004.243.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).