From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Timur Tabi <timur@freescale.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH] asoc/multi-component: fsl: add support for variable SSI FIFO depth
Date: Thu, 5 Aug 2010 06:51:53 -0700 [thread overview]
Message-ID: <20100805135153.GB14470@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <AANLkTinYjH-r3Myv=YavQBS0ULu-T0U4LPscsMOUtujR@mail.gmail.com>
On Thu, Aug 05, 2010 at 08:14:43AM -0500, Timur Tabi wrote:
> On Thu, Aug 5, 2010 at 6:10 AM, Mark Brown
> > My first thought with this is that it's not something I'd expect to be
> > in the device tree at all - it looks like it's all properties of the
> > silicon which I'd expect the drivers to be able to figure out for
> > themselves without needing to be told by the device tree.
> There is no way for the software to know what the FIFO depth is, so
> this is the sort of thing that should be in the device tree.
Are you saying that every DT for a system doing audio on a PowerPC
system has to manually specify the depth of the FIFO on the silicon?
That doesn't sound particularly sensible, and I had been under the
impression that DT systems had a better way of coping with this.
next prev parent reply other threads:[~2010-08-05 13:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 20:04 [PATCH] asoc/multi-component: fsl: add support for variable SSI FIFO depth Timur Tabi
2010-08-05 11:10 ` Mark Brown
2010-08-05 13:14 ` Timur Tabi
2010-08-05 13:51 ` Mark Brown [this message]
2010-08-05 14:10 ` Tabi Timur-B04825
2010-08-05 14:54 ` Mark Brown
2010-08-05 15:14 ` Tabi Timur-B04825
2010-08-05 16:03 ` Mark Brown
2010-08-05 16:21 ` Tabi Timur-B04825
2010-08-05 18:18 ` Mark Brown
2010-08-05 19:43 ` Grant Likely
2010-08-05 21:13 ` Timur Tabi
2010-08-05 21:19 ` Grant Likely
2010-08-05 21:42 ` Mark Brown
2010-08-05 22:04 ` Grant Likely
2010-08-05 22:34 ` Mark Brown
2010-08-05 23:19 ` Grant Likely
2010-08-05 23:23 ` Mark Brown
2010-08-05 23:22 ` 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=20100805135153.GB14470@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=timur@freescale.com \
/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.