Hi,

Takashi Iwai wrote:

>> Finally there is some misconception in the aureon & prodigy drivers: 
>>the codec chip does not have a Master control as it appears at the 
>>mixer. Instead the master control just updates the 8 volume controls of 
>>the individual DAC at the same time. Probably the best way is to add a 
>>virtual master control (ie that we update the volumes of the dac with  
>><master attenuation> + <specific channel attenuation> ).
>>    
>>
>
>well, such a thing should be done on user-space rather than on
>kernel.  let's postpone this until the new highlevel mixer functions
>become available.
>  
>
   That's fine if it can be done in user space but this creates a problem
with the mixer right now. Changing the master volume does not update all
the DAC volumes as it should and you can be in the situation where
Master is100% and all other volumes are 0, yet the playback is done in
maximum volume at all channels. Maybe the driver should update all
channel volumes on a master update.

>>As I wrote some days ago, the default buffer/period rates that 
>>alsarecord uses at 44.1KHz and lower sampling , locks hard the kernel. 
>>Have no idea what is it/how to fix it whatsoever.
>>    
>>
>
>hmm, could be the mismatch of cristal rate?
>i don't find out the critical path in the driver yet.
>  
>

No idea about that and how to debug it.. The driver still locks the
kernel using arecord and default parameters at 44.1Khz but not at higher
sample rates. I attached the PCM setup that locks the machine hard. It
seems that the driver manages to record a few periods and then locks.
Maybe the reason is the funny period buffer sizes (5513??) that appear
at the pcm setup. As I understand the situation it is a (minor) problem
with the ice1724 driver.

Apostolis