From: Sascha Hauer <s.hauer@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: zii-imx8mq-dev: disable GPU and VPU power domain in DT
Date: Mon, 4 Nov 2019 09:11:28 +0100 [thread overview]
Message-ID: <20191104081128.rq3wgisjpseprri2@pengutronix.de> (raw)
In-Reply-To: <20191030111640.12367-2-l.stach@pengutronix.de>
On Wed, Oct 30, 2019 at 12:16:40PM +0100, Lucas Stach wrote:
> In Barebox we don't have a driver for the PMIC powering those domains,
> so we get a "probe permanently deferred" warning for those domains. As
> they are not actually used in Barebox, we can just disable them to get
> rid of the warning.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> arch/arm/dts/imx8mq-zii-ultra.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm/dts/imx8mq-zii-ultra.dtsi b/arch/arm/dts/imx8mq-zii-ultra.dtsi
> index 6180f21ab0a4..bde70901a331 100644
> --- a/arch/arm/dts/imx8mq-zii-ultra.dtsi
> +++ b/arch/arm/dts/imx8mq-zii-ultra.dtsi
> @@ -56,6 +56,14 @@
> };
> };
>
> +&pgc_gpu {
> + status = "disabled";
> +};
> +
> +&pgc_vpu {
> + status = "disabled";
> +};
This breaks GPU support under Linux when started with the barebox device
tree, right? Is there a better solution?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-11-04 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 11:16 [PATCH 1/2] soc: imx: gpcv2: skip registering devices for unavailable power domains Lucas Stach
2019-10-30 11:16 ` [PATCH 2/2] ARM: zii-imx8mq-dev: disable GPU and VPU power domain in DT Lucas Stach
2019-11-04 8:11 ` Sascha Hauer [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=20191104081128.rq3wgisjpseprri2@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=l.stach@pengutronix.de \
/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