From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: 32337ea "ASoC: warn if we will overwrite the DAI stream widgets"
Date: Thu, 29 Aug 2013 01:01:26 +0100 [thread overview]
Message-ID: <20130829000126.GQ6617@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <521E8798.10206@wwwdotorg.org>
On Wed, Aug 28, 2013 at 05:28:24PM -0600, Stephen Warren wrote:
> Russell, if the warning in commit 32337ea "ASoC: warn if we will
> overwrite the DAI stream widgets" fires, what do I need to do to the
> ASoC driver to fix it? (I'm deliberately ignoring any other issues with
> this patch, and looking only to discover what is apparently wrong with
> my driver that's triggering this...).
>
> Steev Klimaszewski reported this warning to me, and I've repro'd it
> running next-20130827 on a couple of Tegra systems (TrimSlice and
> Seaboard at least), using sound/soc/tegra/tegra_{trimslice,wm8903}.c,
> and associated ASoC components.
I chucked this into linux-next in order to prove that the issue I had
been reporting was not specific to my systems here (because I was making
absolutely no useful progress with Mark.) Mark finally admitted for the
first time that there's a bug here yesterday, so I've now dropped the
patch out of linux-next (either that's coincidental or cause and effect).
In any case, it's served its purpose.
As for how to solve the underlying problem, I have no idea - I've been
asking the same question of Mark for the last three weeks and just been
getting a load of drivel about "it's because you're using DPCM" and
other *totally useless* suggestions about the code I'm trying to get
working.
Liam says he's working on "a patch" last week, so I assume that this
issue will eventually be resolved.
prev parent reply other threads:[~2013-08-29 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 23:28 32337ea "ASoC: warn if we will overwrite the DAI stream widgets" Stephen Warren
2013-08-29 0:01 ` Russell King - ARM Linux [this message]
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=20130829000126.GQ6617@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