linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Asier Llano Palacios" <a.llano@usyscom.com>
To: "Txema Lopez" <tlopez@aotek.es>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc5200 and spi bus
Date: Fri, 27 Apr 2007 12:36:33 +0200	[thread overview]
Message-ID: <1177670193.9950.9.camel@a.llano.llano> (raw)
In-Reply-To: <4630BBF9.7000305@aotek.es>

I'm working with the a linux 2.6.20.9 with patches from Sylvain's tree.
I've been looking the Den'x 2.5.xx SPI support and it seems that it is
done through GPIOs. I'd like a native SPI implementation, using the
hardware of the MPC5200, because of the performance issue of using a
GPIO, because I'd like to use it at full speed.

Is it done really with GPIOs? If so, is there any other implementation?
If it is possible I'd like it to be for 2.6.x.

Thank you,
Asier

El jue, 26-04-2007 a las 16:49 +0200, Txema Lopez escribi=F3:
> Asier Llano Palacios wrote:
>=20
> >I've seen some comments about drivers for SPI of the MPC5200. I'm not
> >sure about it, but is there anything functional about it?. I want to
> >know if there is anything already done, in order to use it or improve
> >it. I need a driver of the SPI bus, so if it is not implemented at =
all
> >we should contribute it.
> >
> > =20
> >
> The Denx's 2.4.xx top of tree kernel has MPC5200 SPI support. We are=20
> using the SPI dev interface from a user aplication and it works fine.
>=20
>=20
=20
----------------------------------------- PLEASE NOTE =
-------------------------------------------
This message, along with any attachments, may be confidential or legally =
privileged.=20
It is intended only for the named person(s), who is/are the only =
authorized recipients.
If this message has reached you in error, kindly destroy it without =
review and notify the sender immediately.
Thank you for your help.
=B5SysCom uses virus scanning software but excludes any liability for =
viruses contained in any attachment.
=20
------------------------------------ ROGAMOS LEA ESTE TEXTO =
-------------------------------
Este mensaje y sus anexos pueden contener informaci=F3n confidencial y/o =
con derecho legal.=20
Est=E1 dirigido =FAnicamente a la/s persona/s o entidad/es rese=F1adas =
como =FAnico destinatario autorizado.
Si este mensaje le hubiera llegado por error, por favor elim=EDnelo sin =
revisarlo ni reenviarlo y notif=EDquelo inmediatamente al remitente. =
Gracias por su colaboraci=F3n. =20
=B5SysCom utiliza software antivirus, pero no se hace responsable de los =
virus contenidos en los ficheros anexos.

  reply	other threads:[~2007-04-27 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 13:50 mpc5200 and spi bus Asier Llano Palacios
2007-04-26 14:49 ` Txema Lopez
2007-04-27 10:36   ` Asier Llano Palacios [this message]
2007-04-27 12:41     ` Txema Lopez
2007-05-02  8:02       ` Asier Llano Palacios
2007-05-02 17:36         ` Sascha Hauer
2007-05-02 20:19           ` John Rigby
2007-05-03 10:22             ` Asier Llano Palacios

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=1177670193.9950.9.camel@a.llano.llano \
    --to=a.llano@usyscom.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=tlopez@aotek.es \
    /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).