mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Dhruva Gole <d-gole@ti.com>
Cc: <s-ramamoorthy@ti.com>, <lgirdwood@gmail.com>,
	<broonie@kernel.org>, <aaro.koskinen@iki.fi>,
	<khilman@baylibre.com>, <rogerq@kernel.org>, <tony@atomide.com>,
	<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<m-leonard@ti.com>, <praneeth@ti.com>,
	Robert Nelson <robertcnelson@gmail.com>
Subject: Re: [PATCH] Revert "regulator: tps65219: Add TI TPS65214 Regulator Support"
Date: Thu, 19 Jun 2025 19:30:38 +0200	[thread overview]
Message-ID: <20250619193038.4e1f42c8@akair> (raw)
In-Reply-To: <20250619153526.297398-1-d-gole@ti.com>

Am Thu, 19 Jun 2025 21:05:26 +0530
schrieb Dhruva Gole <d-gole@ti.com>:

> This reverts commit f1471bc435afa31c8c0c58551922830dc8f4b06b.
> 
> This was causing boot regressions [1] on many BeagleBoard platforms
> like the AM62x based BeaglePlay and PocketBeagle-2.
> 
> [1] https://gist.github.com/DhruvaG2000/75b7d5ced6c09d508ee0ad5ab1f19707
> 
> Signed-off-by: Dhruva Gole <d-gole@ti.com>https://gist.github.com/DhruvaG2000/75b7d5ced6c09d508ee0ad5ab1f19707
> ---
hmm, do you need to really revert everything? Apparently some code
slipped through affecting the tps65219.

[..]
>  static const struct regulator_desc tps65219_regs[] = {
> -	TPS65219_REGULATOR("LDO1", "ldo1", TPS65219_LDO_1,
> -			   REGULATOR_VOLTAGE, ldos_1_2_ops, 64,
> -			   TPS65219_REG_LDO1_VOUT,
> -			   TPS65219_BUCKS_LDOS_VOUT_VSET_MASK,
> -			   TPS65219_REG_ENABLE_CTRL,
> -			   TPS65219_ENABLE_LDO1_EN_MASK, 0, 0, ldo_1_range,
> -			   2, 0, 0, NULL, 0, TPS65219_LDOS_BYP_CONFIG_MASK),
>  	TPS65219_REGULATOR("LDO2", "ldo2", TPS65219_LDO_2,
>  			   REGULATOR_VOLTAGE, ldos_1_2_ops, 64,
>  			   TPS65219_REG_LDO2_VOUT,
> @@ -366,23 +326,13 @@ struct tps65219_chip_data {
>  };

e.g. this.

I think it should be relatively easy to only revert that part without
needing to revert it fully.

Regards,
Andreas

  reply	other threads:[~2025-06-19 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 15:35 Dhruva Gole
2025-06-19 17:30 ` Andreas Kemnade [this message]
2025-06-19 18:13   ` Mark Brown
2025-06-19 18:14 ` Mark Brown
2025-06-19 19:58 ` Shree Ramamoorthy
2025-06-19 23:24   ` Robert Nelson
2025-06-20  0:15     ` Shree Ramamoorthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250619193038.4e1f42c8@akair \
    --to=andreas@kemnade.info \
    --cc=aaro.koskinen@iki.fi \
    --cc=broonie@kernel.org \
    --cc=d-gole@ti.com \
    --cc=khilman@baylibre.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=m-leonard@ti.com \
    --cc=praneeth@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=rogerq@kernel.org \
    --cc=s-ramamoorthy@ti.com \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®