public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jens Gehrlein <sew_s@tqs.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPI on PPC MPC85xx
Date: Thu, 28 Oct 2010 08:44:49 +0200	[thread overview]
Message-ID: <4CC91BE1.4040707@tqs.de> (raw)
In-Reply-To: <201010271002.31707.sr@denx.de>

Hi Matthias,

Stefan Roese schrieb:
> Hi Matthias,
> 
> On Wednesday 27 October 2010 08:55:42 Matthias Dunda wrote:
>> unfortunately I have to push this message, as I received no comment on it,
>> yet.
>>
>> Is there a reason why the immap_t is not implemented for mpc85xx?
>>
>> I tried to copy it from mpc8360 but there are so many dependent mpc83xx
>> datatypes in that struct that I postponed the work on that, because I
>> think it'll lead to no success...
>>
>> Even trying to use the soft SPI fails, because first thing the code does is
>> using that immap_t datatype... :-(
>>
>> Does anyone have a comment on this?
> 
> I took a quick glance at this. There are different versions of SPI controllers 
> in the MPC8xxx SoC's. As it seems mpc8xxx_spi.c does "only" support the "CPU-
> mode" (meaning non-CPM/QE-mode) Freescale SPI controllers. This controller is 
> implemented for example in the MPC8349. For your SoC (MPC8568) you need to 
> implement the QE-mode which is currently not supported.

I didn't compare the MPC85xx QE SPI controller with the MPC8xx CPM SPI
controller, but maybe a look at arch/powerpc/cpu/mpc8xx/spi.c could
help you as a base for porting/creating a driver?

-- 
Kind regards,
Jens

  reply	other threads:[~2010-10-28  6:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 11:05 [U-Boot] SPI on PPC MPC85xx Matthias
2010-10-27  6:55 ` Matthias Dunda
2010-10-27  7:21   ` Wolfgang Denk
2010-10-27  8:02   ` Stefan Roese
2010-10-28  6:44     ` Jens Gehrlein [this message]
2010-10-27 19:13   ` Scott Wood

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=4CC91BE1.4040707@tqs.de \
    --to=sew_s@tqs.de \
    --cc=u-boot@lists.denx.de \
    /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