forked from Minki/linux
regulator: Suggest use of datasheet supply or pin names for consumers
Update the documentation to suggest the use of datasheet names for the supplies requested by regulator consumers. Doing this makes it easier to tie the design for a given platform up with the requirements of the driver for a consumer. Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk>
This commit is contained in:
parent
1dd68f0188
commit
fe203ddfa5
@ -925,9 +925,12 @@ overflow_err:
|
||||
* @id: Supply name or regulator ID.
|
||||
*
|
||||
* Returns a struct regulator corresponding to the regulator producer,
|
||||
* or IS_ERR() condition containing errno. Use of supply names
|
||||
* configured via regulator_set_device_supply() is strongly
|
||||
* encouraged.
|
||||
* or IS_ERR() condition containing errno.
|
||||
*
|
||||
* Use of supply names configured via regulator_set_device_supply() is
|
||||
* strongly encouraged. It is recommended that the supply name used
|
||||
* should match the name used for the supply and/or the relevant
|
||||
* device pins in the datasheet.
|
||||
*/
|
||||
struct regulator *regulator_get(struct device *dev, const char *id)
|
||||
{
|
||||
|
Loading…
Reference in New Issue
Block a user