> If the board doesn't use regulators you can just disable the regulator > API at which point it compiles out into stubs which report success - > this has been the case from day one. There's only an issue if the board > has a regulator configuration which is partially visible to software. Which is quite likely on anything complex and means that hardcoding regulator assumptions is bad. I actually see two ways of attacking that, one is that the dummy regulator *and* the compiled in regulator system have a standard regulator value that can be passed which means "report success, move along nothing to see" that could be passed into drivers, the other is to not stick the stuff in drivers. I suspect the former may be cleaner ? Alan -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
