From: Francesco Dolcini <francesco@dolcini.it>
To: Stefan Eichenberger <eichest@gmail.com>
Cc: 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,
u-boot@lists.u-boot-project.org
Subject: Re: [PATCH v1 2/2] imx: mach: imx8: fdt: support newer GPU0 bus node name
Date: Tue, 20 Oct 2026 07:40:16 +0200 [thread overview]
Message-ID: <20261020054016.GB6592@francesco-nb> (raw)
In-Reply-To: <20261019125930.111608-3-eichest@gmail.com>
On Mon, Oct 19, 2026 at 02:58:53PM +0200, Stefan Eichenberger wrote:
> From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
>
> Mainline Linux and NXP downstream kernels starting with 6.18 name the
> GPU0 subsystem bus@53000000, while older downstream kernels used
> bus@53100000. Because of that, the industrial GPU clock rates were not
> applied and GPU0 kept running at the default 700/850 MHz instead of
> the 625 MHz limit of the industrial SoC.
>
> Use /bus@53000000/gpu@53100000 and, if it does not exist, fall back to
> the legacy /bus@53100000/gpu@53100000.
>
> Signed-off-by: Stefan Eichenberger <stefan.eichenberger@toradex.com>
Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
prev parent reply other threads:[~2026-10-20 5:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 12:58 [PATCH v1 0/2] imx: mach: imx8: fdt: fix industrial GPU frequencies Stefan Eichenberger
2026-10-19 12:58 ` [PATCH v1 1/2] imx: mach: imx8: fdt: return libfdt errors from helpers Stefan Eichenberger
2026-10-20 5:31 ` Francesco Dolcini
2026-10-19 12:58 ` [PATCH v1 2/2] imx: mach: imx8: fdt: support newer GPU0 bus node name Stefan Eichenberger
2026-10-20 5:40 ` Francesco Dolcini [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=20261020054016.GB6592@francesco-nb \
--to=francesco@dolcini.it \
--cc=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.