linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "S. Fricke" <silvio.fricke@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: psc and spi
Date: Tue, 15 Jan 2008 07:51:47 -0700	[thread overview]
Message-ID: <fa686aa40801150651s213a745dwa4d595de5a9d191b@mail.gmail.com> (raw)
In-Reply-To: <20080115135306.GE14333@sfrouter>

On 1/15/08, S. Fricke <silvio.fricke@googlemail.com> wrote:
> Hello friends,
>
> I have on the psc3 the spi-interface of a fpga connected.
>
>    psc3-0 - MOSI
>    psc3-1 - MISO
>    psc3-2 - CLK
>    psc3-3 - SlaveSelect
>    psc3-4 - CS-FPGA
>    psc3-5 - CS Another device
>    psc3-6 - SPI-SEL0
>    psc3-7 - SPI-SEL1
>    psc3-8/9 - Not connected
>
> Can I use the mpc52xx_psc_spi-driver? And if yes, how I have to use this
> driver?  Or must I write a own spi-master/slave thing? Can anyone point me
> to a good start-position?

Yes, you should be able to use the mpc52xx_psc_spi driver.  You'' need
to add the activate_cs and deactivate_cs hooks in your platform code
to activate your SPI CS lines.  You'll also need to set port_config to
have the PSC3 pins in "CODEC3" mode.

Cheers,
g.

>
> Best regards,
> Silvio Fricke
>
> --
> -- S. Fricke ----------------------------- MAILTO:silvio.fricke@gmail.com --
>    Diplom-Informatiker (FH)
>    Linux-Entwicklung
> ----------------------------------------------------------------------------
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
>


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-01-15 14:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 13:53 psc and spi S. Fricke
2008-01-15 14:51 ` Grant Likely [this message]
2008-01-17  7:36   ` S. Fricke
2008-04-02 13:06   ` S. Fricke

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=fa686aa40801150651s213a745dwa4d595de5a9d191b@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=silvio.fricke@gmail.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).