All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Eichenberger <eichest@gmail.com>
To: trini@konsulko.com, ilias.apalodimas@linaro.org,
	sbabic@nabladev.com, festevam@gmail.com, uboot-imx@nxp.com,
	stefan.eichenberger@toradex.com, francesco.dolcini@toradex.com
Cc: u-boot@lists.u-boot-project.org
Subject: [PATCH v1 0/2] imx: mach: imx8: fdt: fix industrial GPU frequencies
Date: Mon, 19 Oct 2026 14:58:51 +0200	[thread overview]
Message-ID: <20261019125930.111608-1-eichest@gmail.com> (raw)

On the industrial i.MX 8 variant, U-Boot limits the GPU clocks to
625 MHz by patching the device tree of the kernel. This series fixes two
issues with that code.

The first patch makes the helpers return the libfdt error codes, so
missing nodes are ignored again and real errors are printed with a
meaningful message. Before, booting a device tree without the GPU1
nodes printed a misleading error:

    Failed to set assigned-clock-rates for GPU1: FDT_ERR_BADPHANDLE

The second patch adds support for the GPU0 bus node name used by
mainline Linux and NXP downstream kernels starting with 6.18
(bus@53000000 instead of bus@53100000). Without it, GPU0 runs at the
default 700/850 MHz instead of the 625 MHz limit of the industrial SoC.

Stefan Eichenberger (2):
  imx: mach: imx8: fdt: return libfdt errors from helpers
  imx: mach: imx8: fdt: support newer GPU0 bus node name

 arch/arm/mach-imx/imx8/fdt.c | 35 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 20 deletions(-)

-- 
2.56.0


             reply	other threads:[~2026-10-19 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 12:58 Stefan Eichenberger [this message]
2026-10-19 12:58 ` [PATCH v1 1/2] imx: mach: imx8: fdt: return libfdt errors from helpers Stefan Eichenberger
2026-10-19 12:58 ` [PATCH v1 2/2] imx: mach: imx8: fdt: support newer GPU0 bus node name Stefan Eichenberger

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=20261019125930.111608-1-eichest@gmail.com \
    --to=eichest@gmail.com \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=sbabic@nabladev.com \
    --cc=stefan.eichenberger@toradex.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=uboot-imx@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.