blob: 5318ab3aceced510d89fc28be24ac00005103f07 [file] [log] [blame]
Tom Rini10e47792018-05-06 17:58:06 -04001/* SPDX-License-Identifier: GPL-2.0+ */
Przemyslaw Marczak08edd002015-04-20 20:07:42 +02002/*
3 * Copyright (C) 2014-2015 Samsung Electronics
4 * Przemyslaw Marczak <p.marczak@samsung.com>
Przemyslaw Marczak08edd002015-04-20 20:07:42 +02005 */
6
7#ifndef _INCLUDE_REGULATOR_H_
8#define _INCLUDE_REGULATOR_H_
9
10/**
11 * U-Boot Voltage/Current Regulator
12 * ================================
13 *
14 * The regulator API is based on a driver model, with the device tree support.
15 * And this header describes the functions and data types for the uclass id:
16 * 'UCLASS_REGULATOR' and the regulator driver API.
17 *
18 * The regulator uclass - is based on uclass platform data which is allocated,
19 * automatically for each regulator device on bind and 'dev->uclass_platdata'
20 * points to it. The data type is: 'struct dm_regulator_uclass_platdata'.
21 * The uclass file: 'drivers/power/regulator/regulator-uclass.c'
22 *
23 * The regulator device - is based on driver's model 'struct udevice'.
24 * The API can use regulator name in two meanings:
25 * - devname - the regulator device's name: 'dev->name'
26 * - platname - the device's platdata's name. So in the code it looks like:
27 * 'uc_pdata = dev->uclass_platdata'; 'name = uc_pdata->name'.
28 *
29 * The regulator device driver - provide an implementation of uclass operations
30 * pointed by 'dev->driver->ops' as a struct of type 'struct dm_regulator_ops'.
31 *
32 * To proper bind the regulator device, the device tree node should provide
33 * regulator constraints, like in the example below:
34 *
35 * ldo1 {
Przemyslaw Marczak75692a32015-05-13 13:38:27 +020036 * regulator-name = "VDD_MMC_1.8V"; (must be unique for proper bind)
Przemyslaw Marczak08edd002015-04-20 20:07:42 +020037 * regulator-min-microvolt = <1000000>; (optional)
38 * regulator-max-microvolt = <1000000>; (optional)
39 * regulator-min-microamp = <1000>; (optional)
40 * regulator-max-microamp = <1000>; (optional)
41 * regulator-always-on; (optional)
42 * regulator-boot-on; (optional)
43 * };
44 *
Przemyslaw Marczak75692a32015-05-13 13:38:27 +020045 * Note: For the proper operation, at least name constraint is needed, since
46 * it can be used when calling regulator_get_by_platname(). And the mandatory
47 * rule for this name is, that it must be globally unique for the single dts.
Peng Fanb4cb9ce2015-08-07 16:43:43 +080048 * If regulator-name property is not provided, node name will be chosen.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +020049 *
50 * Regulator bind:
51 * For each regulator device, the device_bind() should be called with passed
52 * device tree offset. This is required for this uclass's '.post_bind' method,
Przemyslaw Marczak75692a32015-05-13 13:38:27 +020053 * which does the scan on the device node, for the 'regulator-name' constraint.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +020054 * If the parent is not a PMIC device, and the child is not bind by function:
55 * 'pmic_bind_childs()', then it's recommended to bind the device by call to
Simon Glass09128c52016-07-05 17:10:09 -060056 * dm_scan_fdt_dev() - this is usually done automatically for bus devices,
Przemyslaw Marczak08edd002015-04-20 20:07:42 +020057 * as a post bind method.
Przemyslaw Marczak75692a32015-05-13 13:38:27 +020058 *
59 * Regulator get:
Przemyslaw Marczak08edd002015-04-20 20:07:42 +020060 * Having the device's name constraint, we can call regulator_by_platname(),
Przemyslaw Marczak75692a32015-05-13 13:38:27 +020061 * to find the required regulator. Before return, the regulator is probed,
Przemyslaw Marczak08edd002015-04-20 20:07:42 +020062 * and the rest of its constraints are put into the device's uclass platform
63 * data, by the uclass regulator '.pre_probe' method.
64 *
65 * For more info about PMIC bind, please refer to file: 'include/power/pmic.h'
66 *
67 * Note:
68 * Please do not use the device_bind_by_name() function, since it pass '-1' as
69 * device node offset - and the bind will fail on uclass .post_bind method,
70 * because of missing 'regulator-name' constraint.
71 *
72 *
73 * Fixed Voltage/Current Regulator
74 * ===============================
75 *
76 * When fixed voltage regulator is needed, then enable the config:
77 * - CONFIG_DM_REGULATOR_FIXED
78 *
79 * The driver file: 'drivers/power/regulator/fixed.c', provides basic support
80 * for control the GPIO, and return the device tree constraint values.
81 *
82 * To bind the fixed voltage regulator device, we usually use a 'simple-bus'
83 * node as a parent. And 'regulator-fixed' for the driver compatible. This is
84 * the same as in the kernel. The example node of fixed regulator:
85 *
86 * simple-bus {
87 * compatible = "simple-bus";
88 * #address-cells = <1>;
89 * #size-cells = <0>;
90 *
91 * blue_led {
92 * compatible = "regulator-fixed";
93 * regulator-name = "VDD_LED_3.3V";
94 * regulator-min-microvolt = <3300000>;
95 * regulator-max-microvolt = <3300000>;
96 * gpio = <&gpc1 0 GPIO_ACTIVE_LOW>;
97 * };
98 * };
99 *
100 * The fixed regulator devices also provide regulator uclass platform data. And
101 * devices bound from such node, can use the regulator drivers API.
102*/
103
104/* enum regulator_type - used for regulator_*() variant calls */
105enum regulator_type {
106 REGULATOR_TYPE_LDO = 0,
107 REGULATOR_TYPE_BUCK,
108 REGULATOR_TYPE_DVS,
109 REGULATOR_TYPE_FIXED,
Keerthy17b3fe72016-09-15 17:04:06 +0530110 REGULATOR_TYPE_GPIO,
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200111 REGULATOR_TYPE_OTHER,
112};
113
114/**
115 * struct dm_regulator_mode - this structure holds an information about
116 * each regulator operation mode. Probably in most cases - an array.
117 * This will be probably a driver-static data, since it is device-specific.
118 *
119 * @id - a driver-specific mode id
120 * @register_value - a driver-specific value for its mode id
121 * @name - the name of mode - used for regulator command
122 * Note:
123 * The field 'id', should be always a positive number, since the negative values
124 * are reserved for the errno numbers when returns the mode id.
125 */
126struct dm_regulator_mode {
127 int id; /* Set only as >= 0 (negative value is reserved for errno) */
128 int register_value;
129 const char *name;
130};
131
Simon Glass991f9bc2015-06-23 15:38:57 -0600132enum regulator_flag {
133 REGULATOR_FLAG_AUTOSET_UV = 1 << 0,
134 REGULATOR_FLAG_AUTOSET_UA = 1 << 1,
135};
136
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200137/**
138 * struct dm_regulator_uclass_platdata - pointed by dev->uclass_platdata, and
139 * allocated on each regulator bind. This structure holds an information
140 * about each regulator's constraints and supported operation modes.
141 * There is no "step" voltage value - so driver should take care of this.
142 *
143 * @type - one of 'enum regulator_type'
144 * @mode - pointer to the regulator mode (array if more than one)
145 * @mode_count - number of '.mode' entries
146 * @min_uV* - minimum voltage (micro Volts)
147 * @max_uV* - maximum voltage (micro Volts)
148 * @min_uA* - minimum amperage (micro Amps)
149 * @max_uA* - maximum amperage (micro Amps)
150 * @always_on* - bool type, true or false
151 * @boot_on* - bool type, true or false
Simon Glass991f9bc2015-06-23 15:38:57 -0600152 * TODO(sjg@chromium.org): Consider putting the above two into @flags
153 * @flags: - flags value (see REGULATOR_FLAG_...)
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200154 * @name** - fdt regulator name - should be taken from the device tree
Keerthy4d96cd02016-09-30 09:20:42 +0530155 * ctrl_reg: - Control register offset used to enable/disable regulator
156 * volt_reg: - register offset for writing voltage vsel values
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200157 *
158 * Note:
159 * * - set automatically on device probe by the uclass's '.pre_probe' method.
160 * ** - set automatically on device bind by the uclass's '.post_bind' method.
161 * The constraints: type, mode, mode_count, can be set by device driver, e.g.
162 * by the driver '.probe' method.
163 */
164struct dm_regulator_uclass_platdata {
165 enum regulator_type type;
166 struct dm_regulator_mode *mode;
167 int mode_count;
168 int min_uV;
169 int max_uV;
170 int min_uA;
171 int max_uA;
172 bool always_on;
173 bool boot_on;
174 const char *name;
Simon Glass991f9bc2015-06-23 15:38:57 -0600175 int flags;
Keerthy4d96cd02016-09-30 09:20:42 +0530176 u8 ctrl_reg;
177 u8 volt_reg;
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200178};
179
180/* Regulator device operations */
181struct dm_regulator_ops {
182 /**
183 * The regulator output value function calls operates on a micro Volts.
184 *
185 * get/set_value - get/set output value of the given output number
186 * @dev - regulator device
187 * Sets:
188 * @uV - set the output value [micro Volts]
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200189 * @return output value [uV] on success or negative errno if fail.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200190 */
191 int (*get_value)(struct udevice *dev);
192 int (*set_value)(struct udevice *dev, int uV);
193
194 /**
195 * The regulator output current function calls operates on a micro Amps.
196 *
197 * get/set_current - get/set output current of the given output number
198 * @dev - regulator device
199 * Sets:
200 * @uA - set the output current [micro Amps]
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200201 * @return output value [uA] on success or negative errno if fail.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200202 */
203 int (*get_current)(struct udevice *dev);
204 int (*set_current)(struct udevice *dev, int uA);
205
206 /**
207 * The most basic feature of the regulator output is its enable state.
208 *
209 * get/set_enable - get/set enable state of the given output number
210 * @dev - regulator device
211 * Sets:
212 * @enable - set true - enable or false - disable
Keerthy23be7fb2017-06-13 09:53:45 +0530213 * @return true/false for get or -errno if fail; 0 / -errno for set.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200214 */
Keerthy23be7fb2017-06-13 09:53:45 +0530215 int (*get_enable)(struct udevice *dev);
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200216 int (*set_enable)(struct udevice *dev, bool enable);
217
218 /**
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200219 * The 'get/set_mode()' function calls should operate on a driver-
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200220 * specific mode id definitions, which should be found in:
221 * field 'id' of struct dm_regulator_mode.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200222 *
223 * get/set_mode - get/set operation mode of the given output number
224 * @dev - regulator device
225 * Sets
226 * @mode_id - set output mode id (struct dm_regulator_mode->id)
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200227 * @return id/0 for get/set on success or negative errno if fail.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200228 * Note:
229 * The field 'id' of struct type 'dm_regulator_mode', should be always
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200230 * a positive number, since the negative is reserved for the error.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200231 */
232 int (*get_mode)(struct udevice *dev);
233 int (*set_mode)(struct udevice *dev, int mode_id);
234};
235
236/**
237 * regulator_mode: returns a pointer to the array of regulator mode info
238 *
239 * @dev - pointer to the regulator device
240 * @modep - pointer to the returned mode info array
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200241 * @return - count of modep entries on success or negative errno if fail.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200242 */
243int regulator_mode(struct udevice *dev, struct dm_regulator_mode **modep);
244
245/**
246 * regulator_get_value: get microvoltage voltage value of a given regulator
247 *
248 * @dev - pointer to the regulator device
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200249 * @return - positive output value [uV] on success or negative errno if fail.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200250 */
251int regulator_get_value(struct udevice *dev);
252
253/**
254 * regulator_set_value: set the microvoltage value of a given regulator.
255 *
256 * @dev - pointer to the regulator device
257 * @uV - the output value to set [micro Volts]
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200258 * @return - 0 on success or -errno val if fails
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200259 */
260int regulator_set_value(struct udevice *dev, int uV);
261
262/**
Keerthy162c02e2016-10-26 13:42:30 +0530263 * regulator_set_value_force: set the microvoltage value of a given regulator
264 * without any min-,max condition check
265 *
266 * @dev - pointer to the regulator device
267 * @uV - the output value to set [micro Volts]
268 * @return - 0 on success or -errno val if fails
269 */
270int regulator_set_value_force(struct udevice *dev, int uV);
271
272/**
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200273 * regulator_get_current: get microampere value of a given regulator
274 *
275 * @dev - pointer to the regulator device
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200276 * @return - positive output current [uA] on success or negative errno if fail.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200277 */
278int regulator_get_current(struct udevice *dev);
279
280/**
281 * regulator_set_current: set the microampere value of a given regulator.
282 *
283 * @dev - pointer to the regulator device
284 * @uA - set the output current [micro Amps]
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200285 * @return - 0 on success or -errno val if fails
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200286 */
287int regulator_set_current(struct udevice *dev, int uA);
288
289/**
290 * regulator_get_enable: get regulator device enable state.
291 *
292 * @dev - pointer to the regulator device
Keerthy23be7fb2017-06-13 09:53:45 +0530293 * @return - true/false of enable state or -errno val if fails
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200294 */
Keerthy23be7fb2017-06-13 09:53:45 +0530295int regulator_get_enable(struct udevice *dev);
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200296
297/**
298 * regulator_set_enable: set regulator enable state
299 *
300 * @dev - pointer to the regulator device
301 * @enable - set true or false
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200302 * @return - 0 on success or -errno val if fails
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200303 */
304int regulator_set_enable(struct udevice *dev, bool enable);
305
306/**
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200307 * regulator_get_mode: get active operation mode id of a given regulator
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200308 *
309 * @dev - pointer to the regulator device
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200310 * @return - positive mode 'id' number on success or -errno val if fails
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200311 * Note:
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200312 * The device can provide an array of operating modes, which is type of struct
313 * dm_regulator_mode. Each mode has it's own 'id', which should be unique inside
314 * that array. By calling this function, the driver should return an active mode
315 * id of the given regulator device.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200316 */
317int regulator_get_mode(struct udevice *dev);
318
319/**
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200320 * regulator_set_mode: set the given regulator's, active mode id
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200321 *
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200322 * @dev - pointer to the regulator device
323 * @mode_id - mode id to set ('id' field of struct type dm_regulator_mode)
324 * @return - 0 on success or -errno value if fails
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200325 * Note:
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200326 * The device can provide an array of operating modes, which is type of struct
327 * dm_regulator_mode. Each mode has it's own 'id', which should be unique inside
328 * that array. By calling this function, the driver should set the active mode
329 * of a given regulator to given by "mode_id" argument.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200330 */
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200331int regulator_set_mode(struct udevice *dev, int mode_id);
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200332
333/**
Simon Glassefeeb2c2015-06-23 15:38:59 -0600334 * regulators_enable_boot_on() - enable regulators needed for boot
335 *
336 * This enables all regulators which are marked to be on at boot time. This
337 * only works for regulators which don't have a range for voltage/current,
338 * since in that case it is not possible to know which value to use.
339 *
340 * This effectively calls regulator_autoset() for every regulator.
341 */
342int regulators_enable_boot_on(bool verbose);
343
344/**
Simon Glass46cb8242015-06-23 15:38:58 -0600345 * regulator_autoset: setup the voltage/current on a regulator
346 *
347 * The setup depends on constraints found in device's uclass's platform data
348 * (struct dm_regulator_uclass_platdata):
349 *
350 * - Enable - will set - if any of: 'always_on' or 'boot_on' is set to true,
351 * or if both are unset, then the function returns
352 * - Voltage value - will set - if '.min_uV' and '.max_uV' values are equal
353 * - Current limit - will set - if '.min_uA' and '.max_uA' values are equal
354 *
355 * The function returns on the first-encountered error.
356 *
357 * @platname - expected string for dm_regulator_uclass_platdata .name field
358 * @devp - returned pointer to the regulator device - if non-NULL passed
359 * @return: 0 on success or negative value of errno.
360 */
361int regulator_autoset(struct udevice *dev);
362
363/**
364 * regulator_autoset_by_name: setup the regulator given by its uclass's
365 * platform data name field. The setup depends on constraints found in device's
366 * uclass's platform data (struct dm_regulator_uclass_platdata):
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200367 * - Enable - will set - if any of: 'always_on' or 'boot_on' is set to true,
368 * or if both are unset, then the function returns
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200369 * - Voltage value - will set - if '.min_uV' and '.max_uV' values are equal
370 * - Current limit - will set - if '.min_uA' and '.max_uA' values are equal
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200371 *
372 * The function returns on first encountered error.
373 *
374 * @platname - expected string for dm_regulator_uclass_platdata .name field
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200375 * @devp - returned pointer to the regulator device - if non-NULL passed
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200376 * @return: 0 on success or negative value of errno.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200377 *
378 * The returned 'regulator' device can be used with:
379 * - regulator_get/set_*
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200380 */
Simon Glass46cb8242015-06-23 15:38:58 -0600381int regulator_autoset_by_name(const char *platname, struct udevice **devp);
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200382
383/**
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200384 * regulator_list_autoset: setup the regulators given by list of their uclass's
385 * platform data name field. The setup depends on constraints found in device's
386 * uclass's platform data. The function loops with calls to:
Simon Glass46cb8242015-06-23 15:38:58 -0600387 * regulator_autoset_by_name() for each name from the list.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200388 *
389 * @list_platname - an array of expected strings for .name field of each
390 * regulator's uclass platdata
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200391 * @list_devp - an array of returned pointers to the successfully setup
392 * regulator devices if non-NULL passed
393 * @verbose - (true/false) print each regulator setup info, or be quiet
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200394 * @return 0 on successfully setup of all list entries, otherwise first error.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200395 *
396 * The returned 'regulator' devices can be used with:
397 * - regulator_get/set_*
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200398 *
399 * Note: The list must ends with NULL entry, like in the "platname" list below:
400 * char *my_regulators[] = {
401 * "VCC_3.3V",
402 * "VCC_1.8V",
403 * NULL,
404 * };
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200405 */
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200406int regulator_list_autoset(const char *list_platname[],
407 struct udevice *list_devp[],
408 bool verbose);
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200409
410/**
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200411 * regulator_get_by_devname: returns the pointer to the pmic regulator device.
412 * Search by name, found in regulator device's name.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200413 *
414 * @devname - expected string for 'dev->name' of regulator device
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200415 * @devp - returned pointer to the regulator device
416 * @return 0 on success or negative value of errno.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200417 *
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200418 * The returned 'regulator' device is probed and can be used with:
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200419 * - regulator_get/set_*
420 */
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200421int regulator_get_by_devname(const char *devname, struct udevice **devp);
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200422
423/**
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200424 * regulator_get_by_platname: returns the pointer to the pmic regulator device.
425 * Search by name, found in regulator uclass platdata.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200426 *
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200427 * @platname - expected string for uc_pdata->name of regulator uclass platdata
Simon Glass46cb8242015-06-23 15:38:58 -0600428 * @devp - returns pointer to the regulator device or NULL on error
Przemyslaw Marczakafee81e2015-04-20 20:07:47 +0200429 * @return 0 on success or negative value of errno.
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200430 *
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200431 * The returned 'regulator' device is probed and can be used with:
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200432 * - regulator_get/set_*
433 */
Przemyslaw Marczak75692a32015-05-13 13:38:27 +0200434int regulator_get_by_platname(const char *platname, struct udevice **devp);
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200435
Przemyslaw Marczakc9001032015-10-27 13:07:59 +0100436/**
437 * device_get_supply_regulator: returns the pointer to the supply regulator.
438 * Search by phandle, found in device's node.
439 *
440 * Note: Please pay attention to proper order of device bind sequence.
441 * The regulator device searched by the phandle, must be binded before
442 * this function call.
443 *
444 * @dev - device with supply phandle
445 * @supply_name - phandle name of regulator
446 * @devp - returned pointer to the supply device
447 * @return 0 on success or negative value of errno.
448 */
449int device_get_supply_regulator(struct udevice *dev, const char *supply_name,
450 struct udevice **devp);
451
Przemyslaw Marczak08edd002015-04-20 20:07:42 +0200452#endif /* _INCLUDE_REGULATOR_H_ */