public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: Boot time errors/warnings on snowball
Date: Wed, 4 Dec 2013 17:26:26 +0000	[thread overview]
Message-ID: <20131204172626.GB26581@lee--X1> (raw)
In-Reply-To: <CACRpkda3V4bK3_QO76=++Gcm3pJp78G2L3pgAdaJb2NDcAJG6Q@mail.gmail.com>

> > I noticed these with last night's -next on the snowball:
> >
> > of_dma_request_slave_channel: dma-names property of node
> > '/soc/msp at 80124000' missing or empty
> > of_dma_request_slave_channel: dma-names property of node
> > '/soc/msp at 80124000' missing or empty
> > of_dma_request_slave_channel: dma-names property of node
> > '/soc/msp at 80125000' missing or empty
> > of_dma_request_slave_channel: dma-names property of node
> > '/soc/msp at 80125000' missing or empty
> > dma dma0chan22: [d40_config_memcpy] No memcpy`
> > dma dma0chan22: [d40_alloc_chan_resources] Failed to configure memcpy channel
> > ux500-msp-i2s ux500-msp-i2s.1: Missing dma channel for stream: 0
> > ux500-msp-i2s ux500-msp-i2s.1: ASoC: pcm constructor failed: -22
> 
> I don't see this when booting from the stuff I sent for v3.14,
> but I know Mark applied some fixes from Lee yesterday,
> Lee can you see if you recognize this?

It looks like whatever tree you're building from is missing this patch:
  
  ARM: ux500: Add DMA config bindings for MSP devices

Which is part of the initial reason I said this:

  "If this patch-set could go through ASoC as a whole, it would drive
  down the chance of a dependency mess. Vinod has already provided
  Acks for his parts, so it's just between you two Linus and Mark."

But in Mark's defence, I also tentatively said this:

  "I'm not aware of any dependencies on the ARM changes. I haven't
  tested the arch/arm and sound/soc adaptions orthogonally, but I
  _think_ the right decisions should be made depending on the
  information passed from platform/dt code."

But this error seems strange, as I thought we were still passing the
MSP stuff as AUXDATA for this very reason i.e. lack of DMA support. So
I assumed that the MSP driver(s) would take the platform data
route. At least until the AUXDATAs have been removed, which was my
next step.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2013-12-04 17:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 16:37 Boot time errors/warnings on snowball Olof Johansson
2013-12-04 16:47 ` Linus Walleij
2013-12-04 17:26   ` Lee Jones [this message]
2013-12-04 17:30     ` Olof Johansson
2013-12-04 17:38       ` Lee Jones
2013-12-04 17:39         ` Olof Johansson
2013-12-04 17:36     ` Olof Johansson
2013-12-04 17:51       ` Lee Jones
2013-12-04 17:58         ` Olof Johansson
2013-12-04 18:10           ` Lee Jones
2013-12-04 18:59           ` Mark Brown
2013-12-05  8:00             ` Lee Jones
2013-12-05  9:49             ` Lee Jones
2013-12-05 10:15               ` Mark Brown
2013-12-17 14:47               ` Lee Jones
2014-01-07 14:01                 ` Linus Walleij
2013-12-04 23:17         ` Russell King - ARM Linux
2013-12-05  8:04           ` Lee Jones

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=20131204172626.GB26581@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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