17 Dec
2013
17 Dec
'13
1:46 p.m.
On Tue, Dec 17, 2013 at 08:39:48PM +0800, Shawn Guo wrote:
Hmm, I do not quite follow. The regulator core needs to know whether a regulator device is present or absent, before the regulator is registered, so that regulator core can decide to return -EDEFER_PROBE or -ENODEV when consumer calls regulator_get_optional() to get the regulator. Are you saying platform can call regulator_has_full_constraints() to help regulator core to make this decision? I do not understand how it works.
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.