From: felipe.contreras@gmail.com (Felipe Contreras)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] omap: dsp: fix ioremap() usage
Date: Sun, 10 Oct 2010 23:39:33 +0300 [thread overview]
Message-ID: <AANLkTim8HHT3BQSVSZx_2yBo6SZFj+XR-XYrjNZg+ntW@mail.gmail.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59302342AE533@dbde02.ent.ti.com>
Hi,
Please remove the chunks you are not replying to.
On Sun, Oct 10, 2010 at 11:17 PM, Premi, Sanjeev <premi@ti.com> wrote:
>> -void __init omap_reserve(void)
>> +#if defined(CONFIG_TIDSPBRIDGE) || defined(CONFIG_TIDSPBRIDGE_MODULE)
>
> [sp] I do understand that dspbridge is the only driver accessing dsp in
> ? ? the linux-omap; but there are other known drivers - which would need
> ? ? this feature.
Are you talking about linux-omap the tree? If so, no, the tidspbridge
is part of staging, not linux-omap.
If you are trying to say there are other DSP drivers intended for
OMAP, then I guess you are referring to dsp-link, which uses it's own
tricks for contiguous memory allocation (CMEM).
So, who and how would benefit from this?
> ? ? Can we use a more generic config option viz. CONFIG_RESERVE_DSPMEM
> ? ? (or something similar) so that code is easily (re)usable.
How about CONFIG_OMAP_DSP, and CONFIG_OMAP_DSP_RESERVE_SIZE?
--
Felipe Contreras
next prev parent reply other threads:[~2010-10-10 20:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-10 17:40 [PATCH 0/3] staging: tidspbridge: fix ioremap() usage Felipe Contreras
2010-10-10 17:40 ` [PATCH 1/3] arm: mm: allow boards to fiddle with meminfo Felipe Contreras
2010-10-10 19:03 ` Russell King - ARM Linux
2010-10-10 19:37 ` Felipe Contreras
2010-10-10 17:40 ` [PATCH 2/3] omap: dsp: fix ioremap() usage Felipe Contreras
2010-10-10 20:17 ` Premi, Sanjeev
2010-10-10 20:39 ` Felipe Contreras [this message]
2010-10-11 15:15 ` Guzman Lugo, Fernando
2010-10-11 19:05 ` Felipe Contreras
2010-10-10 17:40 ` [PATCH 3/3] staging: tidspbridge: remove memory consistency from TODO list Felipe Contreras
2010-10-11 10:40 ` Arnd Bergmann
2010-10-11 11:16 ` Felipe Contreras
2010-10-11 14:02 ` Arnd Bergmann
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=AANLkTim8HHT3BQSVSZx_2yBo6SZFj+XR-XYrjNZg+ntW@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).