From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 08/10] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation
Date: Tue, 19 Nov 2013 19:33:41 +0000 [thread overview]
Message-ID: <20131119193341.GC19953@lee--X1> (raw)
In-Reply-To: <20131119184829.GF2674@sirena.org.uk>
On Tue, 19 Nov 2013, Mark Brown wrote:
> On Tue, Nov 19, 2013 at 11:07:47AM +0000, Lee Jones wrote:
>
> > require slightly different flags to inform the core that we 'are'
> > booting with DT.
>
> Is there some situation when we would want to say we're booting from DT
> when we aren't? Just wondering about the quotes.
The quotes do 'not' mean anything special. :)
> > +static const struct snd_dmaengine_pcm_config ux500_dmaengine_of_pcm_config = {
> > + .pcm_hardware = &ux500_pcm_hw,
> > + .prealloc_buffer_size = 128 * 1024,
>
> You shouldn't need to set this explicitly, the generic code should be
> able to pick a number for you - if you do need this number please
> explain why the number was chosen in the comments (or fix the core to
> guess better). At the minute the core just makes up a number too but at
> least then it's a consistent random number between platforms.
>
> Can you also get away without the pcm_hardware - the core should also
> have support for discovering this by querying the DMA controller?
Despite the '+'s, I'm not actually adding these parameters, I'm
duplicating the pdata version and removing the stuff I 'know' that's
not required. I don't know what happens when/if these two parameters
are removed. I can add this to my TODO when I rip out platform data
support, which will happen when this stuff lands.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-11-19 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1384859269-19801-1-git-send-email-lee.jones@linaro.org>
2013-11-19 11:07 ` [PATCH 05/10] ASoC: Ux500: Match platform by device node when booting Device Tree Lee Jones
2013-11-19 18:49 ` Mark Brown
2013-11-19 11:07 ` [PATCH 06/10] ASoC: ux500_pcm: Extend Device Tree support to deal with DMA data Lee Jones
2013-11-19 18:50 ` Mark Brown
2013-11-19 11:07 ` [PATCH 07/10] ASoC: ux500: Store DMA data in the DAI differently in the pdata and DT case Lee Jones
2013-11-19 18:51 ` Mark Brown
2013-12-02 7:35 ` [alsa-devel] " Olof Johansson
2013-12-02 10:12 ` Lee Jones
2013-12-02 13:54 ` [alsa-devel] " Mark Brown
2013-12-02 14:03 ` Lee Jones
2013-12-02 14:04 ` [alsa-devel] " Mark Brown
2013-12-04 17:45 ` Kevin Hilman
2013-12-04 18:03 ` Lee Jones
2013-11-19 11:07 ` [PATCH 08/10] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-11-19 18:48 ` Mark Brown
2013-11-19 19:33 ` Lee Jones [this message]
2013-11-19 19:40 ` Lars-Peter Clausen
2013-11-19 20:09 ` Mark Brown
2013-11-19 11:07 ` [PATCH 09/10] ASoC: ux500_pcm: Take out pointless dev_dbg() call Lee Jones
2013-11-19 18:51 ` 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=20131119193341.GC19953@lee--X1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).