[PATCH] drivers: regulator: tps6594-regulator: Correct multi-phase configuration

Neha Malcom Francis posted 1 patch 1 year, 8 months ago
drivers/regulator/tps6594-regulator.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
[PATCH] drivers: regulator: tps6594-regulator: Correct multi-phase configuration
Posted by Neha Malcom Francis 1 year, 8 months ago
According to the TPS6594 PMIC Manual (linked) 8.3.2.1.4 Multi-Phase BUCK
Regulator Configurations section, the PMIC ignores all the other bucks'
except the primary buck's regulator registers. This is BUCK1 for
configurations BUCK12, BUCK123 and BUCK1234 while it is BUCK3 for
BUCK34. Correct the registers mapped for these configurations
accordingly.

Fixes: f17ccc5deb4d ("regulator: tps6594-regulator: Add driver for TI TPS6594 regulators")
Link: https://www.ti.com/lit/gpn/tps6594-q1
Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
---
Boot logs: https://gist.github.com/nehamalcom/94595895a7f28385fb5c1ec6c1abda23

 drivers/regulator/tps6594-regulator.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/regulator/tps6594-regulator.c b/drivers/regulator/tps6594-regulator.c
index b7f0c8779757..5fad61785e72 100644
--- a/drivers/regulator/tps6594-regulator.c
+++ b/drivers/regulator/tps6594-regulator.c
@@ -287,30 +287,30 @@ static struct tps6594_regulator_irq_type *tps6594_ldos_irq_types[] = {
 static const struct regulator_desc multi_regs[] = {
 	TPS6594_REGULATOR("BUCK12", "buck12", TPS6594_BUCK_1,
 			  REGULATOR_VOLTAGE, tps6594_bucks_ops, TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_VOUT_1(1),
+			  TPS6594_REG_BUCKX_VOUT_1(0),
 			  TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_CTRL(1),
+			  TPS6594_REG_BUCKX_CTRL(0),
 			  TPS6594_BIT_BUCK_EN, 0, 0, bucks_ranges,
 			  4, 4000, 0, NULL, 0, 0),
 	TPS6594_REGULATOR("BUCK34", "buck34", TPS6594_BUCK_3,
 			  REGULATOR_VOLTAGE, tps6594_bucks_ops, TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_VOUT_1(3),
+			  TPS6594_REG_BUCKX_VOUT_1(2),
 			  TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_CTRL(3),
+			  TPS6594_REG_BUCKX_CTRL(2),
 			  TPS6594_BIT_BUCK_EN, 0, 0, bucks_ranges,
 			  4, 0, 0, NULL, 0, 0),
 	TPS6594_REGULATOR("BUCK123", "buck123", TPS6594_BUCK_1,
 			  REGULATOR_VOLTAGE, tps6594_bucks_ops, TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_VOUT_1(1),
+			  TPS6594_REG_BUCKX_VOUT_1(0),
 			  TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_CTRL(1),
+			  TPS6594_REG_BUCKX_CTRL(0),
 			  TPS6594_BIT_BUCK_EN, 0, 0, bucks_ranges,
 			  4, 4000, 0, NULL, 0, 0),
 	TPS6594_REGULATOR("BUCK1234", "buck1234", TPS6594_BUCK_1,
 			  REGULATOR_VOLTAGE, tps6594_bucks_ops, TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_VOUT_1(1),
+			  TPS6594_REG_BUCKX_VOUT_1(0),
 			  TPS6594_MASK_BUCKS_VSET,
-			  TPS6594_REG_BUCKX_CTRL(1),
+			  TPS6594_REG_BUCKX_CTRL(0),
 			  TPS6594_BIT_BUCK_EN, 0, 0, bucks_ranges,
 			  4, 4000, 0, NULL, 0, 0),
 };
-- 
2.34.1
Re: [PATCH] drivers: regulator: tps6594-regulator: Correct multi-phase configuration
Posted by Mark Brown 1 year, 8 months ago
On Tue, 21 May 2024 15:17:58 +0530, Neha Malcom Francis wrote:
> According to the TPS6594 PMIC Manual (linked) 8.3.2.1.4 Multi-Phase BUCK
> Regulator Configurations section, the PMIC ignores all the other bucks'
> except the primary buck's regulator registers. This is BUCK1 for
> configurations BUCK12, BUCK123 and BUCK1234 while it is BUCK3 for
> BUCK34. Correct the registers mapped for these configurations
> accordingly.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] drivers: regulator: tps6594-regulator: Correct multi-phase configuration
      commit: 74b38cd77d3eb63c6d0ad9cf2ae59812ae54d3ee

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
Re: [PATCH] drivers: regulator: tps6594-regulator: Correct multi-phase configuration
Posted by Mark Brown 1 year, 8 months ago
On Tue, May 21, 2024 at 03:17:58PM +0530, Neha Malcom Francis wrote:
> According to the TPS6594 PMIC Manual (linked) 8.3.2.1.4 Multi-Phase BUCK
> Regulator Configurations section, the PMIC ignores all the other bucks'
> except the primary buck's regulator registers. This is BUCK1 for
> configurations BUCK12, BUCK123 and BUCK1234 while it is BUCK3 for
> BUCK34. Correct the registers mapped for these configurations
> accordingly.

Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
Re: [PATCH] drivers: regulator: tps6594-regulator: Correct multi-phase configuration
Posted by Neha Malcom Francis 1 year, 8 months ago
Hi Mark

On 21-May-24 4:57 PM, Mark Brown wrote:
> On Tue, May 21, 2024 at 03:17:58PM +0530, Neha Malcom Francis wrote:
>> According to the TPS6594 PMIC Manual (linked) 8.3.2.1.4 Multi-Phase BUCK
>> Regulator Configurations section, the PMIC ignores all the other bucks'
>> except the primary buck's regulator registers. This is BUCK1 for
>> configurations BUCK12, BUCK123 and BUCK1234 while it is BUCK3 for
>> BUCK34. Correct the registers mapped for these configurations
>> accordingly.
> 
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.

Sorry about this, thanks for explaining; I will definitely take care the 
next time.

-- 
Thanking You
Neha Malcom Francis