From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CEA9E18E25 for ; Wed, 22 Jan 2025 13:18:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737551881; cv=none; b=A3lX7oaQn4kGaNMgwdB6R5+gL6gGLqevYUSrEbOTAkc2kYB3Oh3kxl8r0/+bjyr30DeTSudMlnvxKqxZcKbnv8WPesdibRsfur8nPEKMJX4CGAA0mBxyfNTq6Cjybd3fSjS06YwRcFdncrjZtzc+iJqWVXu708OWyvbwQek1cU4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737551881; c=relaxed/simple; bh=eB3rYLVyc7MJ/xHNoRmYePdyQOcQmzM4Wmr+zAf8rAg=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=gJs3hTKfy0m+YRrxyUB5ARuAxKLXkVD5rsb5RqBORKTODGRJteUrSwps31v7sE3AJKNR8NrsFSbCiCr65x3dOgiXgWy/Vi6ovKwy+76tGaQwNerMQe0om0/UsovvoC/zDZtGOYaYVGsc8u3eZu5SUg3/LRhC3tRhnpYr2pVsrDk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=SjEWeLvG; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="SjEWeLvG" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 62245C4CED6; Wed, 22 Jan 2025 13:18:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1737551881; bh=eB3rYLVyc7MJ/xHNoRmYePdyQOcQmzM4Wmr+zAf8rAg=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=SjEWeLvGpAzplecL/ObtDE3hLGkJc6VtPr0WsfGgY3Kjlhpkk7wQZHkD3ng4ShvhX xPDgsVVOz+suPWfrhYtPq893aHUqPxKM80AgnM9eoZE/TjP4T9NZ2I1zgcDbquSH+x QEqOdxraJVAs0rGTfIZMLkj5goiyI3EneBAymx9/SIcwk8AoFKlusFzVTf0nHukBNN 0YE5oG5HeKtK0RNMgOk+c3jaPaCQMJafXH8wkLZ4uE2iwqbN6RQkZeADEuHa4Nc2ze hYH3PehKXe6y965P9ddH4VlYaMfED2Ieml1cMI8TbjuOZH/C9YcaQ6qOmEMhP48W1K kPup5CKvYg+tw== From: Mark Brown To: Liam Girdwood , Jonas Andreasson Cc: linux-kernel@vger.kernel.org, kernel@axis.com In-Reply-To: <20250121-tps-fix-v2-1-50cc4d0f1635@axis.com> References: <20250121-tps-fix-v2-1-50cc4d0f1635@axis.com> Subject: Re: [PATCH v2] regulator: TPS6287X: Use min/max uV to get VRANGE Message-Id: <173755188009.28873.342950627100571333.b4-ty@kernel.org> Date: Wed, 22 Jan 2025 13:18:00 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-1b0d6 On Tue, 21 Jan 2025 15:37:50 +0100, Jonas Andreasson wrote: > Changing voltage might ignore slew rate and cause a current surge. > > With current implementation the driver will get the regulator to change > the voltage range used during run time. According to communication I > have had with Texas Instruments, this is not intended, since the > Dynamic Voltage Scaling in the hardware is only designed to work > within a voltage range. The current implementation will therefore > ignore the slew rate that is defined in devicetree when the voltage > range is changed during use. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: TPS6287X: Use min/max uV to get VRANGE commit: 3028583d1314a70ca273c51e0265f698c0bd5760 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