linux-kernel - Re: [PATCH 1/2 v2] ASoC: Fix codec device id format used by some dai

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: <1295956512.3322.74.camel@odin>
Date:	Tue, 25 Jan 2011 11:55:12 +0000
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Lars-Peter Clausen <lars@...afoo.de>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2 v2] ASoC: Fix codec device id format used by some
 dai_links

On Mon, 2011-01-24 at 22:09 +0100, Lars-Peter Clausen wrote:
> The id part of an I2C device name is created with the "%d-%04x" format string.
> 
> So for example for an I2C device which is connected to the adapter with the id 0
> and has its address set to 0x1a the id part of the devices name would be
> "0-001a".
> 
> Currently some sound board drivers have the id part the codec_name field of
> their dai_link structures set as if it had been created by a "%d-0x%x" format
> string. For example "0-0x1a" instead of "0-001a".
> 
> As a result there is no match between the codec device and the dai_link and no
> sound card is instantiated.
> 
> This patch fixes it.
> 
> Signed-off-by: Lars-Peter Clausen <lars@...afoo.de>
> 

Both

Acked-by: Liam Girdwood <lrg@...mlogic.co.uk>
-- 
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk

--
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/