| commit | 81d7da5404aad930a4e4f6111e4f16b752183018 | |
| author | Lars-Peter Clausen <lars@metafoo.de> | |
| Mon, 24 Jan 2011 21:09:22 +0000 (24 22:09 +0100) | ||
| committer | Mark Brown <broonie@opensource.wolfsonmicro.com> | |
| Tue, 25 Jan 2011 15:12:36 +0000 (25 15:12 +0000) | ||
| tree | b9a3d9d1bf3532d728e917b519cce68ea8a6bf03 | treesnapshot (tar.gz zip) |
| parent | 20a4e7fc7e213365ea3771d7bf1e10a6bab853be | commitdiff |
ASoC: Fix codec device id format used by some dai_links
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@metafoo.de>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: stable@kernel.org
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@metafoo.de>
Acked-by: Liam Girdwood <lrg@slimlogic.co.uk>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: stable@kernel.org