On Tue, Jul 20, 2010 at 08:25:00AM +0200, Clemens Ladisch wrote:
Takashi Iwai wrote:
Well, what I don't feel right is that this breaks the simpleness of DB_RANGE handling. It's just damn simple, and works as long as the target point is covered by defined ranges. If something is wrong, it's the definition, not the parser. That's why I wondered first whether it can't be fixed in the driver side.
As a driver writer, I would intuitively assume that the ranges must not be overlapping. If we require all drivers to get this right, there will likely be new ones that don't.
This is exactly what happened with all the ASoC drivers - it never even occurred to me that it might be sensible to overlap the ranges. It's not at all obvious, like I've said the drivers are basically providing a data table.