From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: alsa-devel@alsa-project.org,
sakari.ailus@maxwell.research.nokia.com,
Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, lennart@poettering.net,
linux-omap@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [RFC/PATCH v6 03/12] media: Entities, pads and links
Date: Thu, 25 Nov 2010 15:35:46 +0000 [thread overview]
Message-ID: <20101125153546.GI22298@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <201011251629.54575.laurent.pinchart@ideasonboard.com>
On Thu, Nov 25, 2010 at 04:29:53PM +0100, Laurent Pinchart wrote:
> It depends on how you define nodes. I can certainly imagine a graph with 100
> controls, but maybe several controls can be part of the same node ? On the
> video side we've decided to split entities depending on the possible data
> paths configurations. As I'm not a fluent ascii-art speaker, please have a
> look at pages 4 and 5 of http://www.ideasonboard.org/media/20101103-lpc-
> media.pdf
Please take a look at:
http://www.wolfsonmicro.com/products/WM8994
for an example of a modern smartphone CODEC. This has in the ballpark
of 75-100 nodes (I've not counted exactly) represented in the routing
graph in the driver today. This does not include any audio routing
available in other components such as the CPU.
next prev parent reply other threads:[~2010-11-25 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290652099-15102-1-git-send-email-laurent.pinchart@ideasonboard.com>
[not found] ` <1290652099-15102-4-git-send-email-laurent.pinchart@ideasonboard.com>
2010-11-25 9:38 ` [RFC/PATCH v6 03/12] media: Entities, pads and links Clemens Ladisch
2010-11-25 13:41 ` Mark Brown
2010-11-25 15:29 ` [RFC/PATCH v6 03/12] [alsa-devel] " Laurent Pinchart
2010-11-25 15:35 ` Mark Brown [this message]
2010-11-25 15:21 ` Laurent Pinchart
2010-11-25 15:28 ` [RFC/PATCH v6 03/12] " Mark Brown
2010-11-26 9:10 ` Clemens Ladisch
2010-12-13 16:10 ` Clemens Ladisch
2010-12-14 12:00 ` [alsa-devel] " Laurent Pinchart
2010-12-14 12:40 ` Hans Verkuil
2010-12-14 12:53 ` Laurent Pinchart
2010-12-14 13:49 ` Clemens Ladisch
2010-12-14 23:50 ` Laurent Pinchart
2010-12-21 16:49 ` [alsa-devel] " Hans Verkuil
2010-12-14 13:31 ` Clemens Ladisch
2010-12-14 13:54 ` Takashi Iwai
2010-12-14 14:25 ` Laurent Pinchart
2010-12-14 15:30 ` Clemens Ladisch
2010-12-14 23:30 ` Raymond Yau
2010-12-14 14:51 ` [alsa-devel] " Hans Verkuil
2010-12-14 14:57 ` Laurent Pinchart
2010-12-14 14:49 ` [alsa-devel] " Sakari Ailus
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=20101125153546.GI22298@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox