Hi, On Wed, May 30, 2018 at 9:20 AM, Mark Brown <broonie@xxxxxxxxxx> wrote: > On Wed, May 30, 2018 at 09:12:25AM -0700, Doug Anderson wrote: >> On Wed, May 30, 2018 at 8:50 AM, Mark Brown <broonie@xxxxxxxxxx> wrote: > >> > No, I'm saying that I don't know why that property exists at all. This >> > sounds like it's intended to be the amount of current the regulator can >> > deliver in each mode which is normally a design property of the silicon. > >> Ah, got it. So the whole point here is to be able to implement either >> the function "set_load" or the function "get_optimum_mode". We need >> some sort of table to convert from current to mode. That's what this >> table does. > > We do need that table, my expectation would be that this table would be > in the driver as it's not something I'd expect to vary between different > systems but rather be a property of the silicon design. No sense in > every single board having to copy it in. Ah, got it! I'd be OK with it being hardcoded in the driver. At one point I think David was making the argument that some boards have different noise needs for the rails and thus you might want to change modes at different currents. I don't know if this is realistic but I believe it was part of his original argument for why this needed to be specified. If we can hardcode this in the driver I'm fine with it... That would actually solve many of my objections too... -Doug -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
