From: Shree Ramamoorthy <s-ramamoorthy@ti.com>
To: "Kory Maincent (TI.com)" <kory.maincent@bootlin.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Andreas Kemnade <andreas@kemnade.info>,
Kevin Hilman <khilman@baylibre.com>,
Roger Quadros <rogerq@kernel.org>,
Tony Lindgren <tony@atomide.com>, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Andrew Davis <afd@ti.com>, Bajjuri Praneeth <praneeth@ti.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
<linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Enable 1GHz OPP am335x-bonegreen-eco
Date: Fri, 7 Nov 2025 15:25:06 -0600 [thread overview]
Message-ID: <76078ce8-aec3-4a3c-b866-926fc284692e@ti.com> (raw)
In-Reply-To: <20251106-fix_tps65219-v2-0-a7d608c4272f@bootlin.com>
Hi Kory,
On 11/6/2025 4:49 AM, Kory Maincent (TI.com) wrote:
> The vdd_mpu regulator maximum voltage was previously limited to 1.2985V,
> which prevented the CPU from reaching the 1GHz operating point. This
> limitation was put in place because voltage changes were not working
> correctly, causing the board to stall when attempting higher frequencies.
> Increase the maximum voltage to 1.3515V to allow the full 1GHz OPP to be
> used.
>
> Add a TPS65219 PMIC driver fixes that properly implement the LOCK register
> handling, to make voltage transitions work reliably.
>
> Changes in v2:
> - Setup a custom regmap_bus only for the TPS65214 instead of checking
> the chip_id every time reg_write is called.
> - Add the am335x-bonegreen-eco devicetree change in the same patch
> series.
Reviewed-by: Shree Ramamoorthy <s-ramamoorthy@ti.com>
>
> Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
> ---
> Kory Maincent (TI.com) (2):
> mfd: tps65219: Implement LOCK register handling for TPS65214
> ARM: dts: am335x-bonegreen-eco: Enable 1GHz OPP by increasing vdd_mpu voltage
>
> arch/arm/boot/dts/ti/omap/am335x-bonegreen-eco.dts | 2 +-
> drivers/mfd/tps65219.c | 51 +++++++++++++++++++++-
> include/linux/mfd/tps65219.h | 2 +
> 3 files changed, 53 insertions(+), 2 deletions(-)
> ---
> base-commit: 1c353dc8d962de652bc7ad2ba2e63f553331391c
> change-id: 20251106-fix_tps65219-dd62141d22cf
>
> Best regards,
prev parent reply other threads:[~2025-11-07 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 10:49 [PATCH v2 0/2] Enable 1GHz OPP am335x-bonegreen-eco Kory Maincent (TI.com)
2025-11-06 10:49 ` [PATCH v2 1/2] mfd: tps65219: Implement LOCK register handling for TPS65214 Kory Maincent (TI.com)
2025-11-06 22:18 ` kernel test robot
2025-11-10 13:42 ` Lee Jones
2025-11-12 8:59 ` Kory Maincent
2025-11-06 10:49 ` [PATCH v2 2/2] ARM: dts: am335x-bonegreen-eco: Enable 1GHz OPP by increasing vdd_mpu voltage Kory Maincent (TI.com)
2025-11-07 21:25 ` Shree Ramamoorthy [this message]
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=76078ce8-aec3-4a3c-b866-926fc284692e@ti.com \
--to=s-ramamoorthy@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=afd@ti.com \
--cc=andreas@kemnade.info \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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