From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Mark A. Greer" <mgreer@animalcreek.com>,
"Porter, Matt" <mporter@ti.com>
Subject: Re: am3517: geting MMC working
Date: Thu, 19 Jul 2012 08:55:56 +0200 [thread overview]
Message-ID: <5007AF7C.1010902@visionsystems.de> (raw)
In-Reply-To: <CAMQu2gyGH2r1vqEx5DCiv8xr=Lp+p1_5nvrtQe9RdpnfecSoag@mail.gmail.com>
Am 19.07.2012 08:34, schrieb Shilimkar, Santosh:
> On Thu, Jul 19, 2012 at 11:54 AM, Yegor Yefremov
> <yegor_sub1@visionsystems.de> wrote:
>> What patches do I need to get MMC working with linux-omap master?
>>
>> omap_hsmmc omap_hsmmc.0: Failed to get debounce clk
>> omap-dma-engine omap-dma-engine: allocating channel for 62
>> omap-dma-engine omap-dma-engine: allocating channel for 61
>> omap_hsmmc omap_hsmmc.1: Failed to get debounce clk
>> omap-dma-engine omap-dma-engine: allocating channel for 48
>> omap-dma-engine omap-dma-engine: allocating channel for 47
>>
>> I searched for this issue and saw some patches for common clock framework
>> that were scheduled for 3.6, but I'm not sure it's enough or weather they
>> are already incorporated in linux-omap.
>>
> I guess you need [1] to get around the issue.
>
> [1] http://www.spinics.net/lists/linux-omap/msg73965.html
though I haven't applied this patch I have DMA activated (CONFIG_DMADEVICES and CONFIG_DMA_OMAP). Found in some other thread [1]. As far as I can tell, debounce clk is the problem.
[1] http://www.spinics.net/lists/linux-omap/msg73703.html
Yegor
next prev parent reply other threads:[~2012-07-19 6:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 6:24 am3517: geting MMC working Yegor Yefremov
2012-07-19 6:34 ` Shilimkar, Santosh
2012-07-19 6:55 ` Yegor Yefremov [this message]
2012-07-19 7:07 ` Shilimkar, Santosh
2012-07-19 7:28 ` Yegor Yefremov
2012-07-19 7:43 ` S, Venkatraman
2012-07-19 8:15 ` Yegor Yefremov
2012-07-19 8:57 ` S, Venkatraman
2012-07-19 10:08 ` T Krishnamoorthy, Balaji
2012-07-19 13:45 ` Yegor Yefremov
2012-07-19 21:38 ` Paul Walmsley
2012-07-20 7:28 ` T Krishnamoorthy, Balaji
2012-07-20 7:39 ` Yegor Yefremov
2012-07-20 8:01 ` Yegor Yefremov
2012-07-26 23:31 ` Mark A. Greer
2012-07-19 8:46 ` Javier Martinez Canillas
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=5007AF7C.1010902@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=linux-omap@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=mporter@ti.com \
--cc=santosh.shilimkar@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.