[alsa-devel] wrong print debugging message code

Jin-Young Park mcjin02 at gmail.com
Mon Jun 23 20:18:49 CEST 2008


Hello.

I tested the code that "#define XXXX_DEBUG 0" on our company EVB with
WM8960.
I defined "#define XXXX_DEBUG 0" and dbg() put into mute
function(wm8960_digital_mute()).
After linux boot, played audio file.
My test dbg() message was not print terminal, but I find dbg() code was
working exactly.
Excuted dmesg command, then it was print that logged dbg() messages.
I think, it maybe potential that reduce performance before one knows.

Thanks.
Jinyoung Park.


More information about the Alsa-devel mailing list