regulator: lochnagar: Add additional VDDCORE range
Charles Keepax
maintainerPATCH 1/1 regulator: lochnagar: Add additional VDDCORE range
In the case of an unrecognised mini-card the Lochnagar will not initialise the VDDCORE voltage register leading to a value outside of the current range. Add an additional range to cover these values, initially this wasn't done since they are duplicates of the existing minimum value.
--- drivers/regulator/lochnagar-regulator.c | 1 + 1 file changed, 1 insertion(+)
drivers/regulator/lochnagar-regulator.c +1 -0
@@ -98,6 +98,7 @@ static const struct regulator_ops lochnagar_vddcore_ops = { };static const struct linear_range lochnagar_vddcore_ranges[] = { +REGULATOR_LINEAR_RANGE (600000 ,0 ,0x7 ,0 ),REGULATOR_LINEAR_RANGE (600000 ,0x8 ,0x41 ,12500 ), };
Signature · 1 line
2.11.0
Mark Brown
maintainerQuoted 5 lines · Charles Keepax
In the case of an unrecognised mini-card the Lochnagar will not initialise the VDDCORE voltage register leading to a value outside of the current range. Add an additional range to cover these values, initially this wasn't done since they are duplicates of the existing minimum value.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: lochnagar: Add additional VDDCORE range
commit: 6dc9674d95b8a8a81b85a4bed77f86d1b039be10
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