linux-kernel - Re: [alsa-devel] [PATCH v3] ARM: kirkwood: extend the kirkwood i2s driver for DT usage

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 23 Jul 2013 14:50:00 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Cc:	Mark Brown <broonie@...nel.org>,
	Jean-Francois Moine <moinejf@...e.fr>,
	alsa-devel@...a-project.org, Takashi Iwai <tiwai@...e.de>,
	linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
	Rob Herring <rob.herring@...xeda.com>,
	devicetree-discuss@...r.kernel.org
Subject: Re: [alsa-devel] [PATCH v3] ARM: kirkwood: extend the kirkwood i2s
	driver for DT usage

On Tue, Jul 23, 2013 at 03:30:57PM +0200, Sebastian Hesselbarth wrote:
> On 07/23/13 15:20, Mark Brown wrote:
>>> again, we mentioned to merge kirkwood-i2s.c and kirkwood-dma.c into
>>> a single file, didn't we?
>>
>> That's been discussed several times but nobody's actually done it.
>
> Correct, that is why I repeated that request to Jean-Francois.

On that, I have some initial patches which start doing that, but I've
not had time to really complete the effort - the problem is working
with one tree (mainline) while testing on Rabeeh's kernel tree to get
a fully working Cubox platform is quite a hinderance.

Not only that, but the lack of assistance from ASoC people on the
multiple substream stuff really doesn't help one iota when it comes to
making forward progress with SPDIF support.  I've explained to them the
problem (SPDIF and I2S if used together must be enabled simultaneously
or only one is permitted at any one time); they've suggested using the
multiple PCM substream support, and then it's a case that "oh it's
undocumented" "oh there's no examples yet".

And then there's the problem of understanding the ASoC DAPM stuff
"oh it's just a graph walk, you don't need to know the internals"
is what I get from ASoC people.  Well, yes I do need to know the
internals, so I can find out whether it's going to startup a second
substream while a first one is active, and end up with SPDIF enabled
non-concurrently with I2S.
--
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/