From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC 10/13] ASoC: kirkwood-t5325: add DAPM links between codec and cpu DAI
Date: Mon, 5 Aug 2013 15:56:44 +0100 [thread overview]
Message-ID: <20130805145644.GV23006@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130805144054.GE9858@sirena.org.uk>
On Mon, Aug 05, 2013 at 03:40:54PM +0100, Mark Brown wrote:
> On Mon, Aug 05, 2013 at 12:33:10PM +0100, Russell King - ARM Linux wrote:
> > On Mon, Aug 05, 2013 at 12:27:33PM +0100, Mark Brown wrote:
>
> > > This doesn't look good - this is adding DAPM routes which should
> > > correspond to the DAI link that's already been configured.
>
> > No, you're wrong there:
>
> > CPU DAI: Codec DAI
> > dma-playback ---> i2sdo ---> Playback
> > `--> spdifdo -> not connected
> > dma-capture <--- i2sdi <--- Capture
>
> > And the intermediate level is needed to determine which outputs from
> > the chip are wired up.
>
> Right, and that's exactly what the dai_links are doing - they're showing
> what's hanging off each of the DAIs.
>
> > And don't even say "use dpcm" - if you say that, I want _you_ to write
> > it because dpcm is totally and utterly unusable as it currently stands -
> > as you can see from all the emails I've sent over the weekend.
>
> I'm going to tell you to work with the framework rather than around it;
Work with the fscking undocumented framework. If you want that, then
sodding well document this pile of crap. If not, stop telling people
to "work around it".
> adding routes that link the CODEC and CPU together in parallel with the
> links set up for the DAIs is not something that seems like it's going to
> continue to work sensibly going forwards.
So you're *TOTALLY* missing why I've had to do that. Tell me, how can
the CPU DAI detect which of its frigging outputs are connected to the
codec without doing the above? Show me how your crappy subsystem is
supposed to work. Document the sodding thing.
If you don't do this, don't expect people to understand it. Don't
expect people not to find "other solutions" around the utter shite that
I've had to deal with ALL FRIGGING WEEKEND.
These patches stay as they are until you get a clue about what's required
to drive this hardware and start providing some sensible assistance with
your undocumented code.
next prev parent reply other threads:[~2013-08-05 14:56 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 19:21 [PATCH RFC 00/13] Adding SPDIF support to kirkwood-i2s Russell King - ARM Linux
2013-08-04 19:22 ` [PATCH RFC 01/13] ASoC: kirkwood: merge struct kirkwood_dma_priv with struct kirkwood_dma_data Russell King
2013-08-05 14:49 ` Mark Brown
2013-08-04 19:23 ` [PATCH RFC 02/13] ASoC: kirkwood: use devm_clk_get() for the external clock Russell King
2013-08-05 16:16 ` Mark Brown
2013-08-04 19:24 ` [PATCH RFC 03/13] ASoC: avoid duplicated DAI routes Russell King
2013-08-05 16:18 ` Mark Brown
2013-08-04 19:25 ` [PATCH RFC 04/13] ASoC: HACK: avoid creating duplicated widgets Russell King
2013-08-04 19:26 ` [PATCH RFC 05/13] ASoC: kirkwood: provide KIRKWOOD_PLAYCTL_ENABLE_MASK Russell King
2013-08-05 17:03 ` Mark Brown
2013-08-04 19:27 ` [PATCH RFC 06/13] ASoC: kirkwood: combine kirkwood-i2s and kirkwood-dma drivers Russell King
2013-08-05 10:13 ` Jean-Francois Moine
2013-08-05 10:20 ` Russell King - ARM Linux
2013-08-05 17:04 ` Mark Brown
2013-08-04 19:28 ` [PATCH RFC 07/13] ASoC: kirkwood: move calculation of max buffer size to kirkwood.h Russell King
2013-08-05 17:07 ` Mark Brown
2013-08-04 19:29 ` [PATCH RFC 08/13] ASoC: kirkwood: add DAPM widgets for input and output routing Russell King
2013-08-04 19:30 ` [PATCH RFC 09/13] ASoC: kirkwood-openrd: add DAPM links between codec and cpu DAI Russell King
2013-08-04 19:31 ` [PATCH RFC 10/13] ASoC: kirkwood-t5325: " Russell King
2013-08-05 11:27 ` Mark Brown
2013-08-05 11:33 ` Russell King - ARM Linux
2013-08-05 14:40 ` Mark Brown
2013-08-05 14:56 ` Russell King - ARM Linux [this message]
2013-08-05 20:32 ` Russell King - ARM Linux
2013-08-05 22:06 ` Mark Brown
2013-08-05 23:30 ` Russell King - ARM Linux
2013-08-06 13:32 ` Mark Brown
2013-08-10 16:11 ` Russell King - ARM Linux
2013-08-10 21:13 ` Russell King - ARM Linux
2013-08-12 7:40 ` [alsa-devel] " Liam Girdwood
2013-08-12 8:28 ` Russell King - ARM Linux
2013-08-13 14:59 ` Liam Girdwood
2013-08-20 10:25 ` Russell King - ARM Linux
2013-08-20 11:44 ` Mark Brown
2013-08-20 11:49 ` Russell King - ARM Linux
2013-08-20 13:31 ` Russell King - ARM Linux
2013-08-20 18:50 ` Mark Brown
2013-08-20 20:18 ` Russell King - ARM Linux
2013-08-22 19:22 ` Liam Girdwood
2013-08-22 20:16 ` Russell King - ARM Linux
2013-08-23 12:13 ` Liam Girdwood
2013-08-23 12:58 ` Russell King - ARM Linux
2013-08-23 16:58 ` Mark Brown
2013-08-23 17:45 ` Russell King - ARM Linux
2013-08-28 1:22 ` Mark Brown
[not found] ` <CAOyKLY_mQzPxHAg2RFSMY89uxp-0-OAf6fC=gVY0i+pQhv4iHQ@mail.gmail.com>
2013-08-30 11:27 ` Russell King - ARM Linux
2013-08-30 16:10 ` Russell King - ARM Linux
2013-08-11 12:36 ` Mark Brown
2013-08-04 19:32 ` [PATCH RFC 11/13] ASoC: spdif_transceiver: add output pin widget Russell King
2013-08-05 11:33 ` Mark Brown
2013-08-04 19:33 ` [PATCH RFC 12/13] ASoC: kirkwood: add SPDIF output support Russell King
2013-08-04 19:34 ` [PATCH RFC 13/13] ASoC: kirkwood: add IEC958 channel status support Russell King
2013-08-04 21:45 ` [PATCH RFC 00/13] Adding SPDIF support to kirkwood-i2s Sebastian Hesselbarth
2013-08-05 8:43 ` Thomas Petazzoni
2013-08-05 8:53 ` Russell King - ARM Linux
2013-08-05 9:06 ` Thomas Petazzoni
2013-08-05 11:59 ` Mark Brown
2013-08-05 13:06 ` Sebastian Hesselbarth
2013-08-05 14:07 ` Mark Brown
2013-08-05 15:04 ` Sebastian Hesselbarth
2013-08-05 16:59 ` Mark Brown
2013-08-05 18:14 ` Sebastian Hesselbarth
2013-08-05 18:59 ` Mark Brown
2013-08-05 22:47 ` [alsa-devel] " Stephen Warren
2013-08-05 14:10 ` Lars-Peter Clausen
2013-08-05 15:03 ` Mark Brown
2013-08-06 0:02 ` Kuninori Morimoto
2013-08-30 7:20 ` Kuninori Morimoto
2013-08-30 8:26 ` Lars-Peter Clausen
2013-08-30 9:56 ` Mark Brown
2013-08-05 14:59 ` Russell King - ARM Linux
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=20130805145644.GV23006@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).