Applied "regulator: core: Parse coupled regulators properties" to the regulator tree
Mark Brown
maintainerThe patch
regulator: core: Parse coupled regulators properties
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark
Quoted 1 line
From
0c551039dddd5bac73ec15107850afff3cf2dbdcMon Sep 17 00:00:00 2001
From: Maciej Purski <[email protected]>
Date: Fri, 2 Mar 2018 09:42:46 +0100
Subject: [PATCH] regulator: core: Parse coupled regulators properties
On Odroid XU3/4 and other Exynos5422 based boards there is a case, that different devices on the board are supplied by different regulators with non-fixed voltages. If one of these devices temporarily requires higher voltage, there might occur a situation that the spread between devices' voltages is so high, that there is a risk of changing 'high' and 'low' states on the interconnection between devices powered by those regulators.
Add new structure "coupling_desc" to regulator_dev, which contains pointers to all coupled regulators including the owner of the structure, number of coupled regulators and counter of currently resolved regulators.
Add of_functions to parse all data needed in regulator coupling. Provide method to check DTS data consistency. Check if each coupled regulator's max_spread is equal and if their lists of regulators match.
--- drivers/regulator/internal.h | 6 ++ drivers/regulator/of_regulator.c | 149 ++++++++++++++++++++++++++++++++++++++ include/linux/regulator/driver.h | 18 +++++ include/linux/regulator/machine.h | 4 + 4 files changed, 177 insertions(+)
drivers/regulator/internal.h +6 -0
@@ -84,4 +84,10 @@ enum regulator_get_type {struct regulator *_regulator_get (struct device *dev,const char *id,enum regulator_get_type get_type); +struct regulator_dev *of_parse_coupled_regulator (struct regulator_dev *rdev, +int index); + +int of_get_n_coupled (struct regulator_dev *rdev); + +bool of_check_coupling_data (struct regulator_dev *rdev);#endif
drivers/regulator/of_regulator.c +149 -0
158 lines not on this page · raw message
include/linux/regulator/driver.h +18 -0
@@ -15,6 +15,8 @@#ifndef __LINUX_REGULATOR_DRIVER_H_#define __LINUX_REGULATOR_DRIVER_H_ +#define MAX_COUPLED 10 +#include <linux/device.h> #include <linux/notifier.h> #include <linux/regulator/consumer.h>
@@ -403,6 +405,20 @@ struct regulator_config {unsigned int ena_gpio_flags; }; +/* +* struct coupling_desc +* +* Describes coupling of regulators. Each regulator should have +* at least a pointer to itself in coupled_rdevs array. +* When a new coupled regulator is resolved, n_resolved is +* incremented. +*/ +struct coupling_desc { +struct regulator_dev *coupled_rdevs[MAX_COUPLED ]; +int n_resolved; +int n_coupled; +}; +/* * struct regulator_dev *
@@ -426,6 +442,8 @@ struct regulator_dev {/* lists we own */ struct list_head consumer_list;/* consumers we supply */ +struct coupling_desc coupling_desc; +struct blocking_notifier_head notifier;struct mutex mutex;/* consumer lock */ struct module *owner;
include/linux/regulator/machine.h +4 -0
@@ -103,6 +103,7 @@ struct regulator_state {* @ilim_uA: Maximum input current. * @system_load: Load that isn't captured by any consumer requests. * +* @max_spread: Max possible spread between coupled regulators * @valid_modes_mask: Mask of modes which may be configured by consumers. * @valid_ops_mask: Operations which may be performed by consumers. *
@@ -154,6 +155,9 @@ struct regulation_constraints {int system_load; +/* used for coupled regulators */ +int max_spread; +/* valid regulator operating modes for this machine */ unsigned int valid_modes_mask;
Signature · 1 line
2.16.2