From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
NXP Linux Team <linux-imx@nxp.com>,
Fabio Estevam <festevam@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
patchwork-lst@pengutronix.de
Subject: Re: (EXT) [PATCH 9/9] arm64: dts: imx8mp: add GPU nodes
Date: Wed, 26 Jan 2022 14:51:58 +0100 [thread overview]
Message-ID: <4527167.VLH7GnMWUR@steina-w> (raw)
In-Reply-To: <20220119134027.2931945-10-l.stach@pengutronix.de>
Am Mittwoch, 19. Januar 2022, 14:40:27 CET schrieb Lucas Stach:
> Add the DT nodes for both the 3D and 2D GPU cores found on the i.MX8MP.
>
> etnaviv-gpu 38000000.gpu: model: GC7000, revision: 6204
> etnaviv-gpu 38008000.gpu: model: GC520, revision: 5341
> [drm] Initialized etnaviv 1.3.0 20151214 for etnaviv on minor 0
Unfortunately it does not work when CONFIG_DRM_ETNAVIV=m
etnaviv-gpu 38000000.gpu: model: GC0, revision: 0
etnaviv-gpu 38000000.gpu: Unknown GPU model
etnaviv-gpu 38008000.gpu: model: GC0, revision: 0
etnaviv-gpu 38008000.gpu: Unknown GPU model
When I use CONFIG_DRM_ETNAVIV=y, I get the same log message as you. It's not
related to this patch, but I have no clue if the cause is in blk-ctrl or pgc.
I think (don't know for sure yet) my random errors on USB side are gone when
USB drivers (PHY as well) are built-in. But I might be wrong here.
Best regards,
Alexander
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-01-26 13:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 13:40 [PATCH 0/9] i.MX8MP power-domains part 1 and GPU support Lucas Stach
2022-01-19 13:40 ` [PATCH 1/9] soc: imx: gpcv2: add PGC control register indirection Lucas Stach
2022-01-19 13:40 ` [PATCH 2/9] dt-bindings: power: add defines for i.MX8MP power domain Lucas Stach
2022-01-19 13:40 ` [PATCH 3/9] soc: imx: gpcv2: add support for i.MX8MP power domains Lucas Stach
2022-01-19 13:40 ` [PATCH 4/9] dt-bindings: power: imx8mp: add defines for HSIO blk-ctrl domains Lucas Stach
2022-01-19 13:40 ` [PATCH 5/9] dt-bindings: soc: add binding for i.MX8MP HSIO blk-ctrl Lucas Stach
2022-01-19 13:49 ` Fabio Estevam
2022-01-19 14:07 ` Lucas Stach
2022-01-19 14:49 ` Rob Herring
2022-01-19 13:40 ` [PATCH 6/9] soc: imx: add " Lucas Stach
2022-01-21 9:04 ` Abel Vesa
2022-01-21 9:19 ` Lucas Stach
2022-01-19 13:40 ` [PATCH 7/9] arm64: dts: imx8mp: add HSIO power-domains Lucas Stach
2022-01-26 14:02 ` (EXT) " Alexander Stein
2022-01-19 13:40 ` [PATCH 8/9] arm64: dts: imx8mp: add GPU power domains Lucas Stach
2022-01-19 13:40 ` [PATCH 9/9] arm64: dts: imx8mp: add GPU nodes Lucas Stach
2022-01-26 13:51 ` Alexander Stein [this message]
2022-02-07 19:27 ` (EXT) " Lucas Stach
2022-01-19 14:38 ` [PATCH 0/9] i.MX8MP power-domains part 1 and GPU support Abel Vesa
2022-01-19 15:01 ` Lucas Stach
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=4527167.VLH7GnMWUR@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).