On 11/05/2013 03:34 AM, Michal Šmucr wrote: > But it looks better with that particular piece based on this reference > board. It turned out, that it were probably problem with incorrect > values at control descriptors reported by device about its current > draw and bmAttributes with and self-powered declaration. So it was > fixed by new firmware with adjusted values. Was there anything else connected to the same bus (or bus power domain, for that matter)? > Interesting was, that > sometimes it was properly detected, enumerated, all controls of > software mixer was created, but after opening of device, there were > probably uncompleted control transfers, because interface literally > died during it. That's not improbable. The device will draw more current when the streaming starts or the interface is selected or under other circumstances (depends on the hardware and firmware design). If the device then draws more power than the host is able to provide, a brownout condition occurs and the device resets. My general advise in such cases is to use powered USB hub in between, if only for tests. > I plan to try it again with few kernel versions with different > releases of snd-usb-audio module and do more thorough test of it, when > i will have chance. Alright. Thanks, Daniel ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
