From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Nicolin Chen <b42378@freescale.com>,
lgirdwood@gmail.com
Subject: Re: [PATCH v4] ALSA: Add SoC on-chip internal memory support for DMA buffer allocation
Date: Wed, 16 Oct 2013 18:33:52 +0200 [thread overview]
Message-ID: <525EBFF0.1080303@metafoo.de> (raw)
In-Reply-To: <20131016115847.GK2443@sirena.org.uk>
On 10/16/2013 01:58 PM, Mark Brown wrote:
> On Wed, Oct 16, 2013 at 06:53:21PM +0800, Nicolin Chen wrote:
>
>> + if (!dev->of_node)
>> + return NULL;
>> +
>> + pool = of_get_named_gen_pool(dev->of_node, "iram", 0);
>> + if (!pool)
>> + return NULL;
>
> Can you refactor these ifdefs so they just protect this OF specific code
> and just have the allocation fail otherwise please? That way the OF
> dependency is minimised - we should be able to support this on other
> platforms in the future and the rest of the code will be the same.
>
> Also is iram the best name? It makes me think of the dedicated fast
> instruction RAM that some processors have. sram perhaps (for static
> RAM)?
Using IRAM (internal SRAM) for this seems to be quite popular (`grep IRAM
arch/arm -r`). Existing devicetree bindings also seem to use the 'iram'
property to refer to the on-chip SRAM
(Documentation/devicetree/bindings/media/coda.txt). It's probably a good
idea to stay consistent with the existing bindings.
- Lars
next prev parent reply other threads:[~2013-10-16 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 10:53 [PATCH v4] ALSA: Add SoC on-chip internal memory support for DMA buffer allocation Nicolin Chen
2013-10-16 11:58 ` Mark Brown
2013-10-16 12:13 ` Chen Guangyu-B42378
2013-10-16 16:33 ` Lars-Peter Clausen [this message]
2013-10-16 17:46 ` Mark Brown
2013-10-17 1:54 ` Nicolin Chen
2013-10-17 9:38 ` Mark Brown
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=525EBFF0.1080303@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.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 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.