From: Felipe Balbi <balbi@kernel.org>
To: Oliver Graute <oliver.graute@kococonnector.com>,
Peter Chen <peter.chen@nxp.com>
Cc: "linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
oliver.graute@gmail.com, dl-linux-imx <linux-imx@nxp.com>
Subject: Re: using cdns3-imx driver on imx8qm
Date: Wed, 01 Apr 2020 14:36:46 +0300 [thread overview]
Message-ID: <87sghna14h.fsf@kernel.org> (raw)
In-Reply-To: <20200401103434.GA38169@archlinux.localdomain>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Hi,
Oliver Graute <oliver.graute@kococonnector.com> writes:
>> Make sure the five clocks in dts are correct, and print the USB3_SSPHY_STATUS if
>> timeout still exists.
>
> ok I got this for USB3_SSPHY_STATUS
>
> [ 3.057122] cdns3-imx 5b110000.usb3: wait clkvld timeout 0xb0b03827
>
> Unfortunally my imx8qm spec is incomplete regarding the
> USB3_SSPHY_STATUS register.
for testing purposes, you could just have the bootloader enable the
necessary clocks and use dummy fixed-clock in your DTS.
At least you could get something working from USB-side and focus on the
clock tree after that.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-04-01 11:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 17:01 using cdns3-imx driver on imx8qm Oliver Graute
2020-03-27 9:05 ` Peter Chen
2020-03-27 9:50 ` Oliver Graute
2020-03-27 13:21 ` Peter Chen
2020-03-31 14:25 ` Oliver Graute
2020-03-31 14:39 ` Peter Chen
2020-04-01 10:34 ` Oliver Graute
2020-04-01 11:36 ` Felipe Balbi [this message]
2020-04-02 1:16 ` Peter Chen
2020-04-03 14:40 ` Oliver Graute
2020-04-06 16:25 ` Oliver Graute
2020-04-07 2:46 ` Peter Chen
2020-04-07 16:37 ` Oliver Graute
2020-04-07 19:57 ` Oliver Graute
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=87sghna14h.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=oliver.graute@gmail.com \
--cc=oliver.graute@kococonnector.com \
--cc=peter.chen@nxp.com \
--cc=s.hauer@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;
as well as URLs for NNTP newsgroup(s).