On Tue, Apr 28, 2009 at 02:32:56AM -0700, David Brownell wrote: > On Tuesday 28 April 2009, Mark Brown wrote: > > It's not VAUX3 that it's saying has incomplete constraints, it's the > > board as a whole - if the constraints for the board were fully specified > No; driver support != constraint. Only one of the > issues is packaged as a "constraint". Driver support isn't particularly relevant here. If there are devices that don't have drivers or don't have drivers with regulator support but need a regulator enabling then the board should mark the regulator as always_on when setting full constraints; the always_on flag can be removed when the required consumers are added. > > > Mark and/or Liam ... you might want to fix that diagnostic, to > > > avoid leading more developers astray! > > Probably shove a "board has" in there or something I guess. > How about: "VAUX3 board support is incomplete". > That's accurate. No. The constraints being complete is a property of the board as a whole and not the particular regulator. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
