From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC] OMAP5: uEVM: Enable USB EHCI functionality (preliminary, not tested)
Date: Sat, 18 May 2013 21:16:14 +0200 [thread overview]
Message-ID: <5197D37E.8030202@xenomai.org> (raw)
In-Reply-To: <53e99e454e70c1b63eaeec288dba8d18.squirrel@www.mm-sol.com>
On 05/18/2013 09:13 PM, Lubomir Popov wrote:
> Hi Gilles,
>
>> On 05/16/2013 10:39 AM, Lubomir Popov wrote:
>>
>>> Hi Gilles,
>>>
>>> On 16/05/13 01:31, Gilles Chanteperdrix wrote:
>>>> On 05/15/2013 05:55 PM, Lubomir Popov wrote:
>>>>
>>>>> Prerequisites: appropriate patches to the USB EHCI and Eth
>>>>> drivers, and to the OMAP5 clock register definitions.
>>>>
>>>>
>>>> Hi Lubomir,
>>>>
>>>> I have been trying to get the USB working on omap5 uEVM yesterday. In
>>>> addition to your code, I added the changes necessary to pinmux the 79
>>>> and 80 GPIOS correctly, but it does not seem to work. I suspect there
>>>> is
>>>> something else missing than simply USB specific bits, because when the
>>>> ethernet phy is supposedly out of reset, the ethernet leds keep turned
>>>> off. I was thinking about checking the PMIC registers.
>>> PMIC wouldn't be related.
>>
>>
>> Hi,
>>
>> My idea was that if the ethernet chip does not power up, maybe it is
>> because some LDO or SMPS needs to be powered on. The board documentation
>> says for some LDOs that they are enabled on boot and does not say for
>> others, so that may be because they need to be enabled.
> Both USB devices are powered by VCC_3V3_MAIN, provided by an external SMPS
> chip (U3). With the default configuration of the uEVM, this SMPS turns on
> whenever DC wall power is present; the other option - control by the PMIC
> SYSEN1 output, has no relation to software as well (SYSEN1 is driven by
> the PMIC power-on/off sequencer, which is burnt into the PMIC EPROM. Upon
> power-on it goes high at the very beginning of the sequence). So,
> unfortunately, this could not be the cause.
> Regarding the Ethernet LEDs, as far as I remember, they didn't light up at
> all, although Ethernet worked. The smsc95xx driver in u-boot supports the
> LAN9730 in compatibility mode and probably does not setup LED operation
> properly.
Reading the schematics, it seems to me that the ethernet reset arrives
on a component using 1.8V which if I am not mistaken comes from the PMIC
SMPS7.
--
Gilles.
next prev parent reply other threads:[~2013-05-18 19:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 15:55 [U-Boot] [PATCH RFC] OMAP5: uEVM: Enable USB EHCI functionality (preliminary, not tested) Lubomir Popov
2013-05-15 16:09 ` Nishanth Menon
2013-05-15 22:06 ` Tom Rini
2013-05-15 22:33 ` Gilles Chanteperdrix
2013-05-16 8:23 ` Lubomir Popov
2013-05-16 12:28 ` Tom Rini
2013-05-16 14:56 ` Lubomir Popov
2013-05-16 15:29 ` Tom Rini
2013-05-16 18:43 ` Lubomir Popov
2013-05-17 13:52 ` Tom Rini
2013-05-17 5:34 ` Sricharan R
2013-05-17 9:35 ` Lubomir Popov
2013-05-15 22:31 ` Gilles Chanteperdrix
2013-05-16 8:39 ` Lubomir Popov
2013-05-18 15:25 ` Gilles Chanteperdrix
2013-05-18 17:07 ` Tom Rini
2013-05-18 17:12 ` Gilles Chanteperdrix
2013-05-18 19:13 ` Lubomir Popov
2013-05-18 19:16 ` Gilles Chanteperdrix [this message]
2013-05-18 19:24 ` Lubomir Popov
2013-05-18 20:46 ` Gilles Chanteperdrix
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=5197D37E.8030202@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--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