From: Greg Ungerer <gerg@linux-m68k.org>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: peng.fan@nxp.com,
Alexander Stein <alexander.stein@ew.tq-group.com>,
abailon@baylibre.com, krzysztof.kozlowski+dt@linaro.org,
festevam@gmail.com, abelvesa@kernel.org, marex@denx.de,
Markus.Niebel@ew.tq-group.com,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
paul.elder@ideasonboard.com, gerg@kernel.org, linux-imx@nxp.com,
devicetree@vger.kernel.org,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
linux-pm@vger.kernel.org, s.hauer@pengutronix.de,
robh+dt@kernel.org, aford173@gmail.com,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, djakov@kernel.org, shawnguo@kernel.org,
l.stach@pengutronix.de
Subject: Re: [PATCH V3 7/7] arm64: dts: imx8mp: add interconnect for hsio blk ctrl
Date: Wed, 29 Mar 2023 00:34:31 +1000 [thread overview]
Message-ID: <c368a0f8-41f0-69ac-04f4-459e5fc8b9d6@linux-m68k.org> (raw)
In-Reply-To: <20230328135100.rbmnfelphe7juhxo@pengutronix.de>
Hi Marco,
On 28/3/23 23:51, Marco Felsch wrote:
> On 23-03-28, Marco Felsch wrote:
>> Hi Greg,
>>
>> On 23-03-28, Greg Ungerer wrote:
>>> Hi Marco,
>>>
>>> On 28/3/23 17:33, Marco Felsch wrote:
>>>> Hi Greg,
>>>>
>>>> On 23-03-27, Greg Ungerer wrote:
>>>>> Hi Ahmad,
>>>>>
>>>>> On 27/3/23 17:16, Ahmad Fatoum wrote:
>>>>>> On 27.03.23 08:27, Alexander Stein wrote:
>>>>>>> Am Montag, 27. März 2023, 06:50:37 CEST schrieb Greg Ungerer:
>>>>>>>> Any thoughts on why this breaks USB?
>>>>>>>
>>>>>>> Maybe you are missing CONFIG_INTERCONNECT_IMX8MP?
>>>>>>
>>>>>> And if that's the case, did you check /sys/kernel/debug/devices_deferred
>>>>>> to see if there was any indication that this is the reason?
>>>>>
>>>>> Yeah, it does:
>>>>>
>>>>> # cat /sys/kernel/debug/devices_deferred
>>>>> 32f10100.usb platform: supplier 32f10000.blk-ctrl not ready
>>>>> 32f10108.usb platform: supplier 32f10000.blk-ctrl not ready
>>>>> 32ec0000.blk-ctrl imx8m-blk-ctrl: failed to get noc entries
>>>>> 381f0040.usb-phy platform: supplier 32f10000.blk-ctrl not ready
>>>>> 382f0040.usb-phy platform: supplier 32f10000.blk-ctrl not ready
>>>>> imx-pgc-domain.11
>>>>> imx-pgc-domain.12
>>>>> imx-pgc-domain.13
>>>>> 38330000.blk-ctrl platform: supplier imx-pgc-domain.11 not ready
>>>>> 32f10000.blk-ctrl imx8mp-blk-ctrl: failed to get noc entries
>>>>>
>>>>> As far as I can tell blk-ctrl should be good:
>>>>>
>>>>> #
>>>>> # i.MX SoC drivers
>>>>> #
>>>>> CONFIG_IMX_GPCV2_PM_DOMAINS=y
>>>>> CONFIG_SOC_IMX8M=y
>>>>> # CONFIG_SOC_IMX9 is not set
>>>>> CONFIG_IMX8M_BLK_CTRL=y
>>>>> # end of i.MX SoC drivers
>>>>>
>>>>>
>>>>>> If you didn't find any hint there, you might want to place a
>>>>>> dev_err_probe with a suitable message at the place where -EPROBE_DEFER
>>>>>> was returned.
>>>>>
>>>>> I will try that.
>>>>
>>>> Can you check that CONFIG_ARM_IMX_BUS_DEVFREQ is enabled? This is the
>>>> noc/interconnect driver. This could also the problem for you vpu issue.
>>>
>>> I do not have that enabled. Enabling that fixes the USB probing.
>>> So that is good, thanks.
>>>
>>> It doesn't fix the other problem I mentioned with the vpu pgc nodes though.
>>> I do get some extra messages now with this enabled and the 6.1 kernel:
>>>
>>> imx-pgc imx-pgc-domain.8: failed to command PGC
>>> imx-pgc imx-pgc-domain.8: failed to command PGC
>>> imx8m-blk-ctrl 38330000.blk-ctrl: deferred probe timeout, ignoring dependency
>>> imx8m-blk-ctrl 38330000.blk-ctrl: error -110: failed to attach power domain "g1"
>>> imx8m-blk-ctrl: probe of 38330000.blk-ctrl failed with error -110
>>
>> Okay, this seems more like a "real" issue not related to some missing
>> drivers. I followed the code and found a poll within the
>> imx_pgc_power_up() in gpcv2.c. Power-domain 8 is the vpumix domain which
>> is used as power-domain for the g1 power-domain. My assumption is that
>> this poll does run into the timeout. Maybe Peng can support you here
>> since I didn't had the time for to test the VPUs yet and he did the
>> integration patches.
>>
>> Just ignore the errors if you don't use the VPUs or disable the
>> blk-ctrl@38330000 node via status = "disabled".
>
> I forgot to ask: Does your i.MX8MP have a VPU? There are i.MX8MP devices
> (don't know the name) which don't have support for certain IPs. If this
The hardware platform I have is using the MIMX8ML4CVNKZAB "i.MX 8M Plus QuadLite"
(https://www.nxp.com/part/MIMX8ML4CVNKZAB#/) which does not have the hardware
video encode/decoder module (like the "i.MX 8M Plus Quad" parts).
> is the case the bootloader will fixup your devicetree by disable the
> corresponding nodes, we call this feature-controller:
>
> https://elixir.bootlin.com/barebox/latest/source/arch/arm/dts/imx8mp.dtsi
>
> As you can see the imx8mp.dtsi is missing the feature bits for the VPU
> but you can check the i.mx8mm.dtsi. Here you can see that barebox will
> check the availability of the vpu:
>
> https://elixir.bootlin.com/barebox/latest/source/arch/arm/dts/imx8mm.dtsi
Ok, thanks, I'll take a look.
Regards
Greg
next prev parent reply other threads:[~2023-03-28 14:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 9:14 [PATCH V3 0/7] imx: blk-ctrl: Add interconnect for i.MX8MP Peng Fan (OSS)
2022-07-03 9:14 ` [PATCH V3 1/7] dt-bindings: soc: imx: add interconnect property for i.MX8MP media blk ctrl Peng Fan (OSS)
2022-07-03 9:14 ` [PATCH V3 2/7] dt-bindings: soc: imx: add interconnect property for i.MX8MP hdmi " Peng Fan (OSS)
2022-07-03 9:14 ` [PATCH V3 3/7] dt-bindings: soc: imx: add interconnect property for i.MX8MP hsio " Peng Fan (OSS)
2022-07-03 9:14 ` [PATCH V3 4/7] soc: imx: add icc paths for i.MX8MP media " Peng Fan (OSS)
2022-07-03 9:14 ` [PATCH V3 5/7] soc: imx: add icc paths for i.MX8MP hsio/hdmi " Peng Fan (OSS)
2022-07-03 9:14 ` [PATCH V3 6/7] arm64: dts: imx8mp: add interconnects for media " Peng Fan (OSS)
2022-07-07 11:38 ` Marco Felsch
2022-07-08 0:06 ` Peng Fan
2022-07-03 9:14 ` [PATCH V3 7/7] arm64: dts: imx8mp: add interconnect for hsio " Peng Fan (OSS)
2023-03-27 4:50 ` Greg Ungerer
2023-03-27 6:27 ` Alexander Stein
2023-03-27 7:16 ` Ahmad Fatoum
2023-03-27 8:07 ` Greg Ungerer
2023-03-28 7:33 ` Marco Felsch
2023-03-28 12:58 ` Greg Ungerer
2023-03-28 13:42 ` Marco Felsch
2023-03-28 13:51 ` Marco Felsch
2023-03-28 14:34 ` Greg Ungerer [this message]
2023-03-28 15:11 ` Marco Felsch
2023-03-31 5:55 ` Greg Ungerer
2023-03-31 7:45 ` Markus Niebel
2023-03-31 8:11 ` Ahmad Fatoum
2023-03-31 15:09 ` Greg Ungerer
2023-03-27 7:51 ` Greg Ungerer
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=c368a0f8-41f0-69ac-04f4-459e5fc8b9d6@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=a.fatoum@pengutronix.de \
--cc=abailon@baylibre.com \
--cc=abelvesa@kernel.org \
--cc=aford173@gmail.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=festevam@gmail.com \
--cc=gerg@kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=marex@denx.de \
--cc=paul.elder@ideasonboard.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--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
all inboxes | Powered by JetHome®