From: Nicolin Chen <b42378@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Lars-Peter Clausen <lars@metafoo.de>,
lgirdwood@gmail.com
Subject: Re: [PATCH v4] ALSA: Add SoC on-chip internal memory support for DMA buffer allocation
Date: Thu, 17 Oct 2013 09:54:32 +0800 [thread overview]
Message-ID: <20131017015431.GD24805@MrMyself> (raw)
In-Reply-To: <20131016174658.GO2443@sirena.org.uk>
On Wed, Oct 16, 2013 at 06:46:58PM +0100, Mark Brown wrote:
> On Wed, Oct 16, 2013 at 06:33:52PM +0200, Lars-Peter Clausen wrote:
> > On 10/16/2013 01:58 PM, Mark Brown wrote:
>
> > > 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.
>
> Oh, I wonder when that changed - it always used to get called SRAM (or
> TCM when that was what was used).
Do I still need to change the name to SRAM? I think both name make sense to me.
I use IRAM just because using different name for phandle and macro/functions
might confuse people when reviewing the patch. But it looks like IRAM is still
not the perfect choice.
Looking forward to your reply,
Nicolin Chen
next prev parent reply other threads:[~2013-10-17 2:19 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
2013-10-16 17:46 ` Mark Brown
2013-10-17 1:54 ` Nicolin Chen [this message]
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=20131017015431.GD24805@MrMyself \
--to=b42378@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--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.