From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tabi Timur-B04825 <B04825@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 15:54:31 +0100 [thread overview]
Message-ID: <20100805145430.GB26801@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <69A042BE-A5B7-4BD5-91FF-B3F635AF7839@freescale.com>
On Thu, Aug 05, 2010 at 09:10:08AM -0500, Tabi Timur-B04825 wrote:
> On Aug 5, 2010, at 8:52 AM, "Mark Brown" <broonie@opensource.wolfsonmicro.com> wrote:
> > 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?
> Only for SSI devices.
Right, but that's the audio controller on the overwhelming majority of
PowerPC devices.
> > That doesn't sound particularly sensible, and I had been under the
> > impression that DT systems had a better way of coping with this.
> The whole point behind having a device tree is to specify device
> information that cannot be probed. So every piece of information in the
> DT is something that the driver needs to be told because there is no way
> to query the hardware.
This seems crazy, it means that we're not able to use new support for
hardware features to the driver which require any kind of flag or data
without also going through and updating the device trees for all
existing boards. That doesn't seem terribly helpful.
I'm fairly sure that some of the previous discussion with other device
tree people suggested that this was something that there was
infrastructure to cope with.
next prev parent reply other threads:[~2010-08-05 14:54 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
2010-08-05 14:10 ` Tabi Timur-B04825
2010-08-05 14:54 ` Mark Brown [this message]
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=20100805145430.GB26801@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=B04825@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
/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).