linux-kernel - Re: [alsa-devel] [RFC PATCH] ASoC: Modify check condition of multiple bindings of components

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1444913380.26493.38.camel@mtksdaap41>
Date:	Thu, 15 Oct 2015 20:49:40 +0800
From:	Koro Chen <koro.chen@...iatek.com>
To:	Mark Brown <broonie@...nel.org>
CC:	Lars-Peter Clausen <lars@...afoo.de>,
	<alsa-devel@...a-project.org>, <srv_heupstream@...iatek.com>,
	<tiwai@...e.de>, <s.hauer@...gutronix.de>,
	<linux-kernel@...r.kernel.org>, <lgirdwood@...il.com>,
	<linux-mediatek@...ts.infradead.org>, <p.zabel@...gutronix.de>,
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [alsa-devel] [RFC PATCH] ASoC: Modify check condition of
 multiple bindings of components

On Thu, 2015-10-15 at 13:10 +0100, Mark Brown wrote:
> 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.
Yes, and if in some cases we must use multiple cards, it seems the only
option left is to separate an ASoC platform driver into multiple
drivers. It does not make sense to me since there is only one HW block.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/