Re: [RFC PATCH v2 0/3] regulator: pwm-regulator: Fixes for disabled PWMs at boot

From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-pwm@vger.kernel.org, linux-amlogic@lists.infradead.org,
	"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>
Cc: linux-kernel@vger.kernel.org,
	Heiner Kallweit <hkallweit1@gmail.com>,
	 Dmitry Rokosov <ddrokosov@sberdevices.ru>
Subject: Re: [RFC PATCH v2 0/3] regulator: pwm-regulator: Fixes for disabled PWMs at boot
Date: Mon, 22 Jan 2024 20:44:39 +0000	[thread overview]
Message-ID: <170595627996.145638.15681759676659435096.b4-ty@kernel.org> (raw)
In-Reply-To: <20240113224628.377993-1-martin.blumenstingl@googlemail.com>

On Sat, 13 Jan 2024 23:46:25 +0100, Martin Blumenstingl wrote:
> This is the second version of an attempt to fix booting mainline Linux
> on Meson8b Odroid-C1.
> This series is an update to an RFC patch that I sent some time ago [0]
> and incorporates a lot of the feedback from that v1.
> 
> The main changes since v1 [0] are:
> - new patch checking the voltage limits in pwm_regulator_get_voltage()
> - updated calculation for disabled regulators in+
>   pwm_regulator_get_voltage() utilizing above limit checking
> - new pwm_regulator_init_boot_on() to preserve the output voltage when
>   pwm_regulator_enable() later enables the PWM output without and
>   preceding pwm_regulator_set_voltage().
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: pwm-regulator: Add validity checks in continuous .get_voltage
      commit: c92688cac239794e4a1d976afa5203a4d3a2ac0e
[2/3] regulator: pwm-regulator: Calculate the output voltage for disabled PWMs
      commit: 6a7d11efd6915d80a025f2a0be4ae09d797b91ec
[3/3] regulator: pwm-regulator: Manage boot-on with disabled PWM channels
      commit: b3cbdcc191819b75c04178142e2d0d4c668f68c0

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