diff options
| author | Takashi Sakamoto <o-takashi@sakamocchi.jp> | 2014-06-01 20:50:16 +0400 |
|---|---|---|
| committer | Takashi Iwai <tiwai@suse.de> | 2014-06-02 10:46:48 +0400 |
| commit | a6975f2af8a5d72b822e51b79894c81151d4e963 (patch) | |
| tree | 5d5643794b6a26c787fdda7755f04f1440ae6500 /sound | |
| parent | 33a5f989de41622ae691b12f008390309b59ad74 (diff) | |
| download | linux-a6975f2af8a5d72b822e51b79894c81151d4e963.tar.xz | |
ALSA: firewire-lib: Use IEC 61883-6 compliant labels for Raw Audio data
According to AM824 in IEC 61883-6:2002, 2 bits in LSB of label for Raw Audio
data means Valid Length Code (VBL). Ths value is:
- b00 for 24 bits sample (label is 0x40)
- b01 for 20 bits sample (label is 0x41)
- b10 for 16 bits sample (label is 0x42)
But current firewire-lib apply 24 bits label for both of 16/24 bits samples.
As long as developers investigate BeBoB/Fireworks/OXFW/Dice, all of them
have a behaviour to ignore the label. They can generate correct sound even
if firewire-lib gives wrong label (i.e. 0xff). On BeBoB, this is not only
for Raw Audio data channel, but also for IEC 60958 Conformant data channel.
So there is little possibility of regression.
Acked-by: Clemens Ladisch <clemens@ladisch.de>
Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'sound')
| -rw-r--r-- | sound/firewire/amdtp.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sound/firewire/amdtp.c b/sound/firewire/amdtp.c index 31dd1cfc79b3..f96bf4c7c232 100644 --- a/sound/firewire/amdtp.c +++ b/sound/firewire/amdtp.c @@ -418,7 +418,7 @@ static void amdtp_write_s16(struct amdtp_stream *s, for (i = 0; i < frames; ++i) { for (c = 0; c < channels; ++c) { buffer[s->pcm_positions[c]] = - cpu_to_be32((*src << 8) | 0x40000000); + cpu_to_be32((*src << 8) | 0x42000000); src++; } buffer += s->data_block_quadlets; |