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 17:03:11 +0100 [thread overview]
Message-ID: <20100805160310.GA17454@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5610599F537DD74A8D1F5CC946A750730347914E@az33exm25.fsl.freescale.net>
On Thu, Aug 05, 2010 at 08:14:55AM -0700, Tabi Timur-B04825 wrote:
> Mark Brown wrote:
> > 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.
> Hey, what do you want me to do? That's just the way the hardware is
> designed. It is not possible for software to know the FIFO depth of the SSI
> on its own, because there is no register that can be queried. The device
> tree was designed specifically for this purpose -- the provide a data
> structure (e.g. not kernel code) that describes all of the unprobe-able
> features of the various devices on the SOC.
This doesn't seem like a hardware issue, it seems like an issue with the
way we've deployed the device tree. I'd have strongly expected that the
device tree was able to incoporate all the properties that are standard
to the CPU by reference somehow (with that data being distributed
separately to the per system device tree).
next prev parent reply other threads:[~2010-08-05 16:02 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
2010-08-05 15:14 ` Tabi Timur-B04825
2010-08-05 16:03 ` Mark Brown [this message]
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=20100805160310.GA17454@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).