linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Dushara Jayasinghe <DusharaJ@optiscan.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Can't load module spi_mpc83xx : No such device
Date: Fri, 27 Feb 2009 15:54:56 +0300	[thread overview]
Message-ID: <20090227125456.GA21435@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <DE0CCFFBFF707949BEABD4537A14ACBA0C04B40564@mailsvr>

On Fri, Feb 27, 2009 at 03:56:41PM +1100, Dushara Jayasinghe wrote:
> Hi all,
> 
> I'm using linux version 2.6.29-rc5.

Linus' tree is still lacking few patches for spi_mpc83xx driver, the
patches makes spi_mpc83xx work with the device tree directly.

You should use -mm kernels.

[...]
> Part of my device tree is as follows:
> 
> 	soc8349@e0000000 {
> 		...
> 		spi@7000 {
> 			#address-cells = <1>;
> 			#size-cells = <0>;
> 			compatible = "fsl,spi";
> 			reg = <0x7000 0x1000>;
> 			interrupts = <0x10 0x8>;
> 			interrupt-parent = < &ipic >;

You don't seem to have any chip-selects (i.e. gpios = <>) specified.

If the chip-select is always asserted (i.e. there is only one
device on the SPI bus), then..

> 
> 			m25p40@2 {
> 				compatible = "m25p80";
> 				spi-max-frequency = <25000000>;
> 				reg = <2>;

..there is no point in specifying reg = <> for the device.


Thanks,

-- 
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2

  reply	other threads:[~2009-02-27 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-27  4:56 Can't load module spi_mpc83xx : No such device Dushara Jayasinghe
2009-02-27 12:54 ` Anton Vorontsov [this message]
2009-02-28 16:07   ` mpc8349e-mitx 2.6.25 serial IRQ assigned wrong Steve DeLaney
2009-03-03  4:11   ` Can't load module spi_mpc83xx : No such device Dushara Jayasinghe
2009-03-03 12:41     ` Anton Vorontsov

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=20090227125456.GA21435@oksana.dev.rtsoft.ru \
    --to=avorontsov@ru.mvista.com \
    --cc=DusharaJ@optiscan.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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).