On Tue, Dec 17, 2013 at 09:16:15PM +0800, Shawn Guo wrote:
On Tue, Dec 17, 2013 at 12:46:57PM +0000, Mark Brown wrote:
It tells the core that it now knows about all regulator mappings so it knows if it's not got a mapping none will ever appear.
Okay, it sounds like what we need. But I searched all the occurrences of have_full_constraints() in core.c, and haven't found how it influences the regulator_map_list searching. I'm looking at function regulator_dev_lookup(). Can you point me the correct place of the code?
For platform data it can't influence the map searching since we rely on the driver registering outbound supplies, all it does is change if we defer or error. Though the erroring code seems to have gone AWOL at some point and it'd never have been robust for modular drivers anyway.