From: Alexander Shiyan <shc_work@mail.ru>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: PCM038 USB is broken again
Date: Thu, 15 Aug 2013 23:32:41 +0400 [thread overview]
Message-ID: <20130815233241.67b6727ce65114b59807f8ea@mail.ru> (raw)
In-Reply-To: <20130813062607.GQ26614@pengutronix.de>
On Tue, 13 Aug 2013 08:26:07 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Mon, Aug 12, 2013 at 02:56:56PM +0400, Alexander Shiyan wrote:
> > ...
> > And yes, this works after "usb" command:
> > barebox@ConnectCore i.MX51:/ usb
> > USB: scanning bus for devices...
> > Found NXP ISP150x ULPI transceiver (0x04cc:0x1504).
> > Bus 001 Device 001: ID 0000:0000 EHCI Host Controller
> > 1 USB Device(s) found
> >
> > So, you consider this is not a bug?
>
> Doing the initialization twice is not nice and wasn't intended, so
> indeed this is something worth fixing.
Datasheet MCIMX51RM.pdf says:
60.3.8 ULPI/Serial MUX
Host1, Host2, and OTG cores can be configured by software for ULPI or Serial PHY operation. The
ULPI/Serial mux selects between ULPI interface signals and Serial PHY interface signals. The mux is
controlled by the PHY Select signals from the USB core and is switched when the software selects the
interface mode.
The default configuration for the mux is Serial mode. Switching to ULPI mode is done by writing the
Parallel Transceiver Select (PTS) bits in the PORTSC register with 0b10.
So, we need to setup PORTSC to ULPI mode first.
--
Alexander Shiyan <shc_work@mail.ru>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-08-15 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 4:10 Alexander Shiyan
2013-08-12 7:07 ` Sascha Hauer
2013-08-12 10:56 ` Alexander Shiyan
2013-08-13 6:26 ` Sascha Hauer
2013-08-15 19:32 ` Alexander Shiyan [this message]
2013-08-16 8:01 ` Sascha Hauer
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=20130815233241.67b6727ce65114b59807f8ea@mail.ru \
--to=shc_work@mail.ru \
--cc=barebox@lists.infradead.org \
--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