From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] ppc4xx: Canyonlands: Fix USB host PHY reset sequence
Date: Thu, 14 Jan 2010 11:18:32 +0100 [thread overview]
Message-ID: <201001141118.32560.sr@denx.de> (raw)
In-Reply-To: <AC5E1C3367E37D44970B81A6ADD1DA2C087E78B7@SDCEXCHANGE01.ad.amcc.com>
Hi Dave,
On Monday 14 December 2009 22:33:56 David Mitchell wrote:
> > > Current de-assert reset is not sufficient for the USB PHY reset
> > > on some Canyonlands platforms. The patch adds an assert/de-assert
> > > sequence. This addresses a USB detection problem for devices
> > > attached prior to power-up. The delay lengths are needed for
> > > power to the PHY to stabilize.
> > >
> > > Signed-off-by: Jeff Mann <MannJ@embeddedplanet.com>
> > > Signed-off-by: Dave Mitchell <dmitchell@appliedmicro.com>
> > > Acked-by: Tirumala Reddy Marri <tmarri@appliedmicro.com>
> > > ---
> > > v1->v2: fixed typo
> >
> > NAK again. This does not belong in generic board init code.
>
> I see. Are you asking that all of the USB code be removed? Including the
> previous PHY reset implementation done by the original Canyonlands port
> (toggling the CPLD reset for the PHY).
Yes, it's probably best to move this USB init code to some place that's called
in U-Boot only when USB is really used (a board specific USB init function).
And we need to add it to the Linux driver(s) as well.
Will you find the time soon to submit such patches?
Thanks.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
prev parent reply other threads:[~2010-01-14 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 21:04 [U-Boot] [PATCH V2] ppc4xx: Canyonlands: Fix USB host PHY reset sequence Dave Mitchell
2009-12-14 21:16 ` Wolfgang Denk
2009-12-14 21:33 ` David Mitchell
2010-01-14 10:18 ` Stefan Roese [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=201001141118.32560.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.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