From: Mark Jackson <mpfj-list@newflow.co.uk>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: Matt Porter <mporter@ti.com>, Tony Lindgren <tony@atomide.com>,
Joel Fernandes <joelf@ti.com>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Chris Ball <cjb@laptop.org>, Balaji TK <balajitk@ti.com>
Subject: Re: ARM: AM335x: Kernel oops when using EDMA and MMC
Date: Wed, 17 Jul 2013 17:28:37 +0100 [thread overview]
Message-ID: <51E6C635.5020506@newflow.co.uk> (raw)
In-Reply-To: <51E6BE84.6080905@newflow.co.uk>
On 17/07/13 16:55, Mark Jackson wrote:
> I'm trying to get the MMC port working on our custom AM3352 CPU board.
>
> I have added MMC entries to out dts file (similar to [1]), and I've
> enabled CONFIG_TI_EDMA.
>
> Our board boots fine without an SD card inserted ...
>
> [ 0.000000] Booting Linux on physical CPU 0x0
> [ 0.000000] Linux version 3.11.0-rc1-00025-g95b9b72 (mpfj@mpfj-nanobone) (gcc version 4.6.3 (Buildroot 2013.02-dirty) ) #309 Wed Jul 17 16:37:28 BST 2013
> ...
> [ 2.789028] VFS: Mounted root (ubifs filesystem) on device 0:12.
> [ 2.797268] devtmpfs: mounted
> [ 2.801032] Freeing unused kernel memory: 200K (c0551000 - c0583000)
> ...
> Welcome to Buildroot
> nanobone login:
I have just noticed the following in the boot log:-
...
[ 1.225698] omap_hsmmc 48060000.mmc: unable to obtain RX DMA engine channel 3227000204
...
next prev parent reply other threads:[~2013-07-17 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 15:55 ARM: AM335x: Kernel oops when using EDMA and MMC Mark Jackson
2013-07-17 16:28 ` Mark Jackson [this message]
2013-07-17 16:38 ` Joel Fernandes
2013-07-18 8:55 ` Mark Jackson
2013-07-18 16:40 ` Balaji T K
2013-07-18 16:47 ` Daniel Mack
2013-07-18 17:02 ` Joel Fernandes
2013-07-18 17:00 ` Joel Fernandes
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=51E6C635.5020506@newflow.co.uk \
--to=mpfj-list@newflow.co.uk \
--cc=balajitk@ti.com \
--cc=cjb@laptop.org \
--cc=joelf@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.com \
--cc=tony@atomide.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