From: Shubhrajyoti <shubhrajyoti@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Omar Ramirez Luna <omar.luna@linaro.org>,
Joe Woodward <jw@terrafix.co.uk>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: PM/RTC 3.5-rc5: System suspends fails when not built with RTC?
Date: Thu, 12 Jul 2012 11:26:44 +0530 [thread overview]
Message-ID: <4FFE671C.30002@ti.com> (raw)
In-Reply-To: <87wr2ahtqg.fsf@ti.com>
On Thursday 12 July 2012 02:59 AM, Kevin Hilman wrote:
> Omar Ramirez Luna <omar.luna@linaro.org> writes:
>
>> On 11 July 2012 12:07, Kevin Hilman <khilman@ti.com> wrote:
>> ...
>>>> [ 2.311004] omap_hsmmc omap_hsmmc.0: Failed to get debounce clk
>>>> [ 2.317382] omap_hsmmc omap_hsmmc.0: unable to obtain RX DMA engine channel 62
>>>> [ 2.325256] omap_hsmmc omap_hsmmc.1: Failed to get debounce clk
>>>> [ 2.331512] omap_hsmmc omap_hsmmc.1: unable to obtain RX DMA engine channel 48
>>> These are normal because DMA engine is not compiled in with
>>> omap2plus_defconfig. MMC wont' work unless you build in DMA engine, but
>>> that doesn't matter for trying to figure out your problem.
>> Hijacking this thread a little bit...
>>
>> It looks like a dependency is missing in Kconfig then, as this also
>> fails to boot if the file system is in MMC. As you pointed out
>> CONFIG_DMADEVICES and CONFIG_DMA_OMAP is needed to boot in this case.
>> I'm using a Panda 4460.
> Yes, the drivers that have been converted to DMA engine should probably
> 'select DMADEVICES' and 'select DMA_OMAP' since they will now depend on
> DMA engine.
looks like some effort already
https://patchwork.kernel.org/patch/1157731/
>
> Kevin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-12 5:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 15:03 PM/RTC 3.5-rc5: System suspends fails when not built with RTC? Joe Woodward
2012-07-10 23:58 ` Kevin Hilman
2012-07-11 10:50 ` Joe Woodward
2012-07-11 15:31 ` T Krishnamoorthy, Balaji
2012-07-11 17:07 ` Kevin Hilman
2012-07-11 17:51 ` Mark A. Greer
2012-07-11 18:38 ` Kevin Hilman
2012-07-11 18:48 ` Kevin Hilman
2012-07-11 20:52 ` Omar Ramirez Luna
2012-07-11 21:29 ` Kevin Hilman
2012-07-12 5:56 ` Shubhrajyoti [this message]
2012-07-13 6:34 ` Tony Lindgren
2012-07-16 17:18 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2012-07-12 8:15 Joe Woodward
2012-07-12 10:59 ` Paul Walmsley
2012-07-12 14:43 ` Joe Woodward
2012-07-12 19:35 ` Paul Walmsley
2012-07-13 10:57 ` Joe Woodward
2012-07-13 18:26 ` Paul Walmsley
2012-07-13 21:28 ` Mark A. Greer
2012-07-17 0:40 ` Mark A. Greer
2012-07-17 0:43 ` Paul Walmsley
2012-07-17 10:08 ` Joe Woodward
2012-07-17 19:28 ` Paul Walmsley
2012-07-18 2:20 ` Mark A. Greer
2012-07-18 10:06 ` Joe Woodward
2012-07-18 17:26 ` Mark A. Greer
2012-07-26 21:09 ` Juha Kuikka
2012-07-26 23:06 ` Mark A. Greer
2012-07-26 23:08 ` Mark A. Greer
2012-07-12 18:25 ` Kevin Hilman
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=4FFE671C.30002@ti.com \
--to=shubhrajyoti@ti.com \
--cc=jw@terrafix.co.uk \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=omar.luna@linaro.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).