From: Vinod Koul <vkoul@kernel.org>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org,
fabrice.gasnier@foss.st.com, linux-phy@lists.infradead.org,
kishon@kernel.org, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, error27@gmail.com,
kernel@pengutronix.de, linux-stm32@st-md-mailman.stormreply.com,
amelie.delaunay@foss.st.com
Subject: Re: [PATCH v2] phy: stm32-usphyc: add 200 to 300 us delay to fix timeout on some machines
Date: Fri, 31 Mar 2023 18:59:24 +0530 [thread overview]
Message-ID: <ZCbgNNhFQZUo3VKH@matsya> (raw)
In-Reply-To: <20230227151318.1894938-1-m.grzeschik@pengutronix.de>
On 27-02-23, 16:13, Michael Grzeschik wrote:
> An minimum udelay of 200 us seems to be necessary on some machines. After
> the setup of the pll, which needs about 100 us to be locked there seem
> to be additional 100 us to get the phy really functional. Without this
> delay the usb runs not functional. With this additional short udelay
> this issue was not reported again.
Applied, thanks
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-31 13:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 20:45 [PATCH] phy: stm32-usphyc: add mdelay(1) to fix timeout on some machines Michael Grzeschik
2023-02-01 16:20 ` Fabrice Gasnier
2023-02-13 14:59 ` Michael Grzeschik
2023-02-16 8:30 ` Fabrice Gasnier
2023-02-27 15:13 ` [PATCH v2] phy: stm32-usphyc: add 200 to 300 us delay " Michael Grzeschik
2023-02-28 17:28 ` Fabrice Gasnier
2023-03-10 10:44 ` Michael Grzeschik
2023-03-20 12:02 ` Michael Grzeschik
2023-03-31 12:06 ` Michael Grzeschik
2023-03-31 13:19 ` Greg KH
2023-03-31 13:27 ` Vinod Koul
2023-03-31 13:29 ` Vinod Koul [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=ZCbgNNhFQZUo3VKH@matsya \
--to=vkoul@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=error27@gmail.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=m.grzeschik@pengutronix.de \
--cc=mcoquelin.stm32@gmail.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