linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: <hs@denx.de>
Cc: Andreas Larsson <andreas@gaisler.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-spi@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Anton Vorontsov <avorontsov@ru.mvista.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: spi, spi_fsl-spi.c not working?
Date: Mon, 4 Aug 2014 16:52:56 -0500	[thread overview]
Message-ID: <1407189176.10311.12.camel@snotra.buserror.net> (raw)
In-Reply-To: <53C79351.2080406@denx.de>

On Thu, 2014-07-17 at 11:11 +0200, Heiko Schocher wrote:
> Hello all,
> 
> I just tried a mpc83xx based board (similiar to the mpc8313erdb)
> with linux v3.16-rc4 using the drivers/spi/spi-fsl-spi.c driver.
> DT nodes for spi are the same as in arch/powerpc/boot/dts/mpc8313erdb.dts:
> 
>                  spi@7000 {
>                          cell-index = <0>;
>                          compatible = "fsl,spi";
>                          reg = <0x7000 0x1000>;
>                          interrupts = <16 0x8>;
>                          interrupt-parent = <&ipic>;
>                          mode = "cpu";
>                  };
> 
> Bootlog shows:
> 
> [    1.341411] fsl_spi f0007000.spi: master is unqueued, this is deprecated
> [    1.554405] ------------[ cut here ]------------
> [    1.559080] WARNING: at c023a958 [verbose debug info unavailable]

If you haven't already resolved this, could you enable verbose debug
info (or use gdb) to get the line number?

I don't see the WARNING when booting mpc8379rdb with SPI enabled (though
I do see the "master is unqueued" message).  I don't have easy access to
an mpc8313erdb to test on.

-Scott

      parent reply	other threads:[~2014-08-04 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  9:11 spi, spi_fsl-spi.c not working? Heiko Schocher
2014-07-17 11:31 ` Mark Brown
2014-07-17 11:44   ` Heiko Schocher
2014-08-04 21:52 ` Scott Wood [this message]

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=1407189176.10311.12.camel@snotra.buserror.net \
    --to=scottwood@freescale.com \
    --cc=andreas@gaisler.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=broonie@kernel.org \
    --cc=hs@denx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linuxppc-dev@lists.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).