kernel/linux.git/include/linux/regulator/coupler.h, branch v6.19.11Linux kernel stable tree (mirror)https://git.radix-linux.su/kernel/linux.git/atom?h=v6.19.112025-06-26T23:29:07+00:00regulator: core: Don't use "proxy" headers2025-06-26T23:29:07+00:00Andy Shevchenkoandriy.shevchenko@linux.intel.com2025-06-26T15:23:07+00:00urn:sha1:ce57bc9771411d6d27f2ca7b40396cbd7d684ba9
Update header inclusions to follow IWYU (Include What You Use)
principle.
Note that kernel.h is discouraged to be included as it's written
at the top of that file.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Link: https://patch.msgid.link/20250626152307.322627-1-andriy.shevchenko@linux.intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>
regulator: move rdev_print helpers to internal.h2021-06-21T12:08:39+00:00Matti Vaittinenmatti.vaittinen@fi.rohmeurope.com2021-06-03T05:41:37+00:00urn:sha1:157d2230193ae683fcffcc1cd0a2c3aa4479955f
The rdev print helpers are a nice way to print messages related to a
specific regulator device. Move them from core.c to internal.h
As the rdev print helpers use rdev_get_name() export it from core.c. Also
move the declaration from coupler.h to driver.h because the rdev name is
not just a coupled regulator property. I guess the main audience for
rdev_get_name() will be the regulator core and drivers.
Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Link: https://lore.kernel.org/r/dc7fd70dc31de4d0e820b7646bb78eeb04f80735.1622628333.git.matti.vaittinen@fi.rohmeurope.com
Signed-off-by: Mark Brown <broonie@kernel.org>
regulator: extract voltage balancing code to the separate function2020-05-29T13:36:00+00:00Marek Szyprowskim.szyprowski@samsung.com2020-05-29T12:49:39+00:00urn:sha1:752db83a5dfd4fd3a0624b9ab440ed947fa003ca
Move the coupled regulators voltage balancing code to the separate
function and allow to call it from the custom regulator couplers.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Link: https://lore.kernel.org/r/20200529124940.10675-2-m.szyprowski@samsung.com
Signed-off-by: Mark Brown <broonie@kernel.org>
regulator: core: Expose some of core functions needed by couplers2019-06-25T11:15:35+00:00Dmitry Osipenkodigetx@gmail.com2019-06-23T21:08:32+00:00urn:sha1:d22b85a1b97d12a4940ef9d778f6122546736f78
Expose some of internal functions that are required for implementation of
customized regulator couplers.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
regulator: core: Introduce API for regulators coupling customization2019-06-25T11:15:32+00:00Dmitry Osipenkodigetx@gmail.com2019-06-23T21:08:31+00:00urn:sha1:d8ca7d184b33af7913c244900df77c6cad6a5590
Right now regulator core supports only one type of regulators coupling,
the "voltage max-spread" which keeps voltages of coupled regulators in a
given range from each other. A more sophisticated coupling may be required
in practice, one example is the NVIDIA Tegra SoCs which besides the
max-spreading have other restrictions that must be adhered. Introduce API
that allow platforms to provide their own customized coupling algorithms.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>