From: Nishanth Menon <menon.nishanth@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Guzman Lugo, Fernando" <x0095840@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
Ameya Palande <ameya.palande@nokia.com>,
"felipe.contreras@nokia.com" <felipe.contreras@nokia.com>
Subject: Re: [PATCH 3/3] DSPBRIDGE: remove hw_prcm module and related functions
Date: Sat, 01 May 2010 10:34:08 -0500 [thread overview]
Message-ID: <4BDC49F0.6050505@gmail.com> (raw)
In-Reply-To: <g2p94a0d4531005010827x1fc649c0h4bcbf2f1afbccb07@mail.gmail.com>
On 05/01/2010 10:27 AM, Felipe Contreras wrote:
> On Tue, Apr 6, 2010 at 8:54 PM, Guzman Lugo, Fernando<x0095840@ti.com> wrote:
>> From 4fb9fc015cea65dcd47172a8b180f380fe86be46 Mon Sep 17 00:00:00 2001
>> From: Fernando Guzman Lugo<x0095840@ti.com>
>> Date: Tue, 30 Mar 2010 21:37:21 -0600
>> Subject: [PATCH] DSPBRIDGE: remove hw_prcm module and related functions
>>
>> This patches removes TI hw_prcm module and related functions
>> and replace them with kernel functions. As kernel functions
>> are exported, pointer function are used to build without
>> problem in case of building dspbridge as a module.
>>
>> Signed-off-by: Fernando Guzman Lugo<x0095840@ti.com>
>
> This is screwing things for me on a beagleboard:
>
> mem_ext_phys_pool_init: external physical memory map failed
this is interesting -> we ran out of IOremap memory??
> ------------[ cut here ]------------
> WARNING: at mm/page_alloc.c:1813 __alloc_pages_nodemask+0x144/0x514()
> Modules linked in: bridgedriver(+) mailbox_mach mailbox
> [<c002c3a0>] (unwind_backtrace+0x0/0xd4) from [<c004ce38>]
> (warn_slowpath_common+0x48/0x60)
> [<c004ce38>] (warn_slowpath_common+0x48/0x60) from [<c007cef0>]
> (__alloc_pages_nodemask+0x144/0x514)
> [<c007cef0>] (__alloc_pages_nodemask+0x144/0x514) from [<c002cafc>]
> (__dma_alloc+0xc0/0x27c)
> [<c002cafc>] (__dma_alloc+0xc0/0x27c) from [<c002cd30>]
> (dma_alloc_coherent+0x54/0x60)
> [<c002cd30>] (dma_alloc_coherent+0x54/0x60) from [<bf00d7f8>]
> (mem_alloc_phys_mem+0xb0/0xcc [bridgedriver])
> [<bf00d7f8>] (mem_alloc_phys_mem+0xb0/0xcc [bridgedriver]) from
> [<bf01d530>] (drv_request_resources+0x1bc/0x260 [bridgedriver])
> [<bf01d530>] (drv_request_resources+0x1bc/0x260 [bridgedriver]) from
> [<bf023370>] (dsp_init+0x64/0xe8 [bridgedriver])
> [<bf023370>] (dsp_init+0x64/0xe8 [bridgedriver]) from [<bf028da8>]
> (omap34_xx_bridge_probe+0x208/0x2d0 [bridgedriver])
> [<bf028da8>] (omap34_xx_bridge_probe+0x208/0x2d0 [bridgedriver]) from
> [<c01b3550>] (platform_drv_probe+0x18/0x1c)
> [<c01b3550>] (platform_drv_probe+0x18/0x1c) from [<c01b2748>]
> (driver_probe_device+0xa0/0x14c)
> [<c01b2748>] (driver_probe_device+0xa0/0x14c) from [<c01b2854>]
> (__driver_attach+0x60/0x84)
> [<c01b2854>] (__driver_attach+0x60/0x84) from [<c01b201c>]
> (bus_for_each_dev+0x44/0x74)
> [<c01b201c>] (bus_for_each_dev+0x44/0x74) from [<c01b1988>]
> (bus_add_driver+0x9c/0x218)
> [<c01b1988>] (bus_add_driver+0x9c/0x218) from [<c01b2b24>]
> (driver_register+0xa8/0x134)
> [<c01b2b24>] (driver_register+0xa8/0x134) from [<c0026330>]
> (do_one_initcall+0x58/0x1a8)
> [<c0026330>] (do_one_initcall+0x58/0x1a8) from [<c00713c8>]
> (sys_init_module+0xb0/0x1dc)
> [<c00713c8>] (sys_init_module+0xb0/0x1dc) from [<c0026dc0>]
> (ret_fast_syscall+0x0/0x2c)
> ---[ end trace ec6c9b46b6f26ea2 ]---
> shm reservation Failed
> cfg_get_dev_object: Failed, status 0xffffffff
> DSP Bridge driver initialization failed
>
next prev parent reply other threads:[~2010-05-01 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AcrVsjYetIHyTxGhSQuU4kCXDj8zwQ==>
2010-04-06 17:54 ` [PATCH 3/3] DSPBRIDGE: remove hw_prcm module and related functions Guzman Lugo, Fernando
2010-05-01 15:27 ` Felipe Contreras
2010-05-01 15:34 ` Nishanth Menon [this message]
2010-05-01 16:06 ` Felipe Contreras
2010-05-19 0:34 ` Deepak Chitriki
2010-05-19 1:08 ` Guzman Lugo, Fernando
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=4BDC49F0.6050505@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=felipe.contreras@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=x0095840@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox