From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-media@vger.kernel.org
Subject: Re: iram pool not available for MX27
Date: Mon, 30 Sep 2013 17:14:11 +0800 [thread overview]
Message-ID: <524940E3.2070206@gtsys.com.hk> (raw)
In-Reply-To: <52493F77.2020602@gtsys.com.hk>
On Monday, September 30, 2013 05:08 PM, Chris Ruehl wrote:
> Hi Philipp,
>
> On Monday, September 30, 2013 04:30 PM, Philipp Zabel wrote:
>> Hi Chris,
>>
>> Am Montag, den 30.09.2013, 13:40 +0800 schrieb Chris Ruehl:
>>> Hi Phillipp,
>>>
>>> hope things doing OK.
>>>
>>> I recently update to the 3.12-rc kernel and hit this problem below.
>>>
>>> [ 3.377790] coda coda-imx27.0: iram pool not available
>>> [ 3.383363] coda: probe of coda-imx27.0 failed with error -12
>>>
>>> I read your comments of the patch-set using platform data rather then
>>> hard coded addresses to get
>>> the ocram from a SoC.
>>>
>>> I checked the imx27.dtsi for the iram (coda: coda@..) definition and
>>> compare with the former hard coded address and size it matches.
>>>
>>> My .config also has the CONFIG_OF set.
>>>
>>> Any Idea what's go wrong?
>> do you have the mmio-sram driver enabled (CONFIG_SRAM=y)?
>>
>> regards
>> Philipp
>>
>
> No, I didn't, and I found out that my device is not yet ported to use
> "Device Tree Support"
>
> for the moment I will quick add the CONFIG_SRAM and see what happen,
> but on the long term I move my code (clone of mach-mx27ads.c)
> to DTS which makes absolute sense when I see how nice that code works.
>
> Thanks for the reply!
> Chris
>
CONFIG_SRAM not solve my problem, I must port the code to Device Tree
Support and call the of_ functions to make the iram config available.
thank you.
Chris
next prev parent reply other threads:[~2013-09-30 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 5:40 iram pool not available for MX27 Chris Ruehl
2013-09-30 8:30 ` Philipp Zabel
2013-09-30 9:08 ` Chris Ruehl
2013-09-30 9:14 ` Chris Ruehl [this message]
2013-10-29 7:42 ` Chris Ruehl
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=524940E3.2070206@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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).