From: Felipe Balbi <balbi@kernel.org>
To: Heiko Schocher <hs@denx.de>, linux-arm-kernel@lists.infradead.org
Cc: Heiko Schocher <hs@denx.de>, Fabio Estevam <festevam@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Teresa Remmet <t.remmet@phytec.de>,
Zhen Lei <thunder.leizhen@huawei.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: imx8mp: detect dwc3 child nodes with name "usb*"
Date: Fri, 30 Apr 2021 13:03:45 +0300 [thread overview]
Message-ID: <87o8dwhywu.fsf@kernel.org> (raw)
In-Reply-To: <20210430091512.1026996-1-hs@denx.de>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
Heiko Schocher <hs@denx.de> writes:
> commit:
> d1689cd3c0f4: ("arm64: dts: imx8mp: Use the correct name for child node "snps, dwc3")
>
> renamed "dwc3@3*" nodes in imx8mp.dtsi to "usb@3*"
>
> glue layer dwc3-imx8mp.c searches for "dwc3" and so drop failure
> on boot:
> imx8mp-dwc3 32f10100.usb: failed to find dwc3 core child
> imx8mp-dwc3: probe of 32f10100.usb failed with error 1
> imx8mp-dwc3 32f10108.usb: failed to find dwc3 core child
> imx8mp-dwc3: probe of 32f10108.usb failed with error 1
>
> now. Fix this (and allow old style too)
>
> Tested on "PHYTEC phyBOARD-Pollux i.MX8MP" board.
>
> fixes: d1689cd3c0f4: ("arm64: dts: imx8mp: Use the correct name for child node "snps, dwc3")
> Signed-off-by: Heiko Schocher <hs@denx.de>
already sent, see https://lore.kernel.org/r/1619765836-20387-1-git-send-email-jun.li@nxp.com
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2021-04-30 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 9:15 [PATCH] usb: dwc3: imx8mp: detect dwc3 child nodes with name "usb*" Heiko Schocher
2021-04-30 10:03 ` Felipe Balbi [this message]
2021-04-30 10:15 ` Heiko Schocher
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=87o8dwhywu.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hs@denx.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=t.remmet@phytec.de \
--cc=thunder.leizhen@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox