On Thu, Mar 17, 2011 at 09:27:02AM -0500, pl bossart wrote: > Wow. Run-time changes and discoverability? This sounds wild. what type > of solutions are we talking about here? > All the DSP implementations I've seen are pretty dumb, the firmware is > downloaded at the request of the host when a specific service is > requested; discoverability isn't an issue since the driver and > possibly user-space know what's been downloaded and how the downloaded > parts interact with the rest of the firmware. Having the driver figure out what's going on isn't usually much of an issue, it's letting the application know about the configuration that's available. In situations where the DSP can support flexible routing (eg, if it's got multiple audio interfaces and can route or mix between them and also to and from the CPU) with per-flow algorithm selection it gets unmanagable if you try to show everything possible via the current ALSA APIs. Things get worse the more algorithms and so on the DSP can support. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
