| #
b2f0caf1
|
| 26-Dec-2023 |
Emmanuel Vadot <manu@FreeBSD.org> |
regulator: Move regulator code in dev/regulator
We've removed kernel option EXT_RESOURCES almost two years ago. While it was ok to have some code under a common 'extres' subdirectory at first, we no
regulator: Move regulator code in dev/regulator
We've removed kernel option EXT_RESOURCES almost two years ago. While it was ok to have some code under a common 'extres' subdirectory at first, we now have a lot of consumer of it and we made it mandatory so no need to have it under a cryptic name.
Reviewed by: emaste, imp Sponsored by: Beckhoff Automation GmbH & Co. KG Differential Revision: https://reviews.freebsd.org/D43194
show more ...
|
| #
9c3a56d0
|
| 06-Nov-2019 |
Emmanuel Vadot <manu@FreeBSD.org> |
regulator: Add regulator_check_voltage function
This function will call the regnode_check_voltage method for a given regulator and check if the desired voltage in reachable by it. Also adds a defaul
regulator: Add regulator_check_voltage function
This function will call the regnode_check_voltage method for a given regulator and check if the desired voltage in reachable by it. Also adds a default method that check the std_param and which should be enough for most regulators and add it as the method for axp* rk805 and fixed regulators.
Reviewed by: mmel MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D22260
show more ...
|
| #
bcc0decd
|
| 16-Jun-2018 |
Michal Meloun <mmel@FreeBSD.org> |
Fix handling of enable counter for shared GPIO line in fixed regulator.
For most regulators, the regulator_stop() method can be transformed to regulator disable. But, in some cases, we needs to main
Fix handling of enable counter for shared GPIO line in fixed regulator.
For most regulators, the regulator_stop() method can be transformed to regulator disable. But, in some cases, we needs to maintain shared data across multiple regulators (e.g. single GPIO pin which works as enable for multiple regulates). In this case, the implementation of regulator should perform his own enable counting therefore it is necessary to distinguish between the regulator enable/disable method (which increments/decrements enable counter for shared resource) and regulator stop method (which don't affect it).
So: - add regnode_stop() method to regulator framework and default it to regnode_enable(..., false, ...) - implement it in regulator_fixed with proper enable counting.
While I'm in, also fix handling of always_on property. If any of regulators sharing same GPIO pin have it enabled, then none of them can disable regulator.
Tested by: kevans MFC after: 3 weeks
show more ...
|
| #
878ca242
|
| 15-Mar-2016 |
Michal Meloun <mmel@FreeBSD.org> |
Add regulator framework, a next part of new 'extended resources' family of support frameworks(i.e. clk/reset/phy/tsensors/fuses...).
The framework is still far from perfect and probably doesn't have
Add regulator framework, a next part of new 'extended resources' family of support frameworks(i.e. clk/reset/phy/tsensors/fuses...).
The framework is still far from perfect and probably doesn't have stable interface yet, but we want to start testing it on more real boards and different architectures.
show more ...
|