From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Koro Chen <koro.chen@mediatek.com>,
alsa-devel@alsa-project.org, srv_heupstream@mediatek.com,
tiwai@suse.de, s.hauer@pengutronix.de,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
linux-mediatek@lists.infradead.org, p.zabel@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [alsa-devel] [RFC PATCH] ASoC: Modify check condition of multiple bindings of components
Date: Thu, 15 Oct 2015 13:10:35 +0100 [thread overview]
Message-ID: <20151015121035.GE14956@sirena.org.uk> (raw)
In-Reply-To: <561E1991.1050705@metafoo.de>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Wed, Oct 14, 2015 at 11:00:01AM +0200, Lars-Peter Clausen wrote:
> It was never intended that it is possible to bind a component to multiple
> cards. That it was possible was a bug that was overlooked and some people
> tried to do it which caused apparently random crashes later on, caused by
> the data structure corruption. This is why we added the check to catch this
> kind of mistake early and to avoid the crashes.
This is true, but I do think it's something that we should have some
story on supporting for some of this hardware that has a bunch of
channels in one IP block that can't really interact with each other.
It's going to make it a lot easier for people to think about the
hardware and how to describe it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-15 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:37 [RFC PATCH] ASoC: Modify check condition of multiple bindings of components Koro Chen
2015-10-13 13:44 ` Lars-Peter Clausen
2015-10-13 14:18 ` [alsa-devel] " Koro Chen
2015-10-13 14:42 ` Lars-Peter Clausen
2015-10-14 1:19 ` Koro Chen
2015-10-14 9:00 ` Lars-Peter Clausen
2015-10-15 12:10 ` Mark Brown [this message]
2015-10-15 12:49 ` Koro Chen
2015-10-15 13:26 ` Lars-Peter Clausen
2015-10-16 2:31 ` Koro Chen
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=20151015121035.GE14956@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=koro.chen@mediatek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
--cc=tiwai@suse.de \
/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).