From: Benoit Cousson <b-cousson@ti.com>
To: Luciano Coelho <coelho@ti.com>
Cc: balbi@ti.com, Peter Ujfalusi <peter.ujfalusi@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
svenkatr@ti.com, linux-omap@vger.kernel.org,
linux-mmc@vger.kernel.org, cjb@laptop.org, lrg@ti.com,
linux-kernel@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
r.sricharan@ti.com
Subject: Re: 32kHz clock removal causes problems omap_hsmmc
Date: Wed, 19 Dec 2012 15:04:07 +0100 [thread overview]
Message-ID: <50D1C957.8090201@ti.com> (raw)
In-Reply-To: <1355925504.5273.26.camel@cumari.coelho.fi>
On 12/19/2012 02:58 PM, Luciano Coelho wrote:
> On Wed, 2012-12-19 at 14:51 +0100, Benoit Cousson wrote:
>> On 12/19/2012 02:01 PM, Felipe Balbi wrote:
>>> On Wed, Dec 19, 2012 at 11:56:20AM +0100, Peter Ujfalusi wrote:
>>>> BTW: have you happened to ubdate u-boot recently? There is a nice easter egg
>>>> added there:
>>>> f3f98bb ARM: OMAP4/5: Do not configure non essential pads, clocks, dplls.
>>>>
>>>> Which means that _essential_ clocks and pads are no longer configured.
>>>
>>> anything essential you can list ?
>>
>> Yeah, that u-boot version is just unusable at all with any mainline
>> kernel, since we are still missing pads conf for every drivers.
>>
>> Regarding the 32k clock, I noticed as well that the OMAP4460 panda
>> u-boot is the only one to enable it at boot time, and thus this is the
>> only board that can probe the wilink chip properly as of today.
>
> Do you mean that with the latest mainline u-boot all boards will have
> trouble except panda?
I don't know since the u-boot mainline has never ever supported properly
the SDP4430, I stopped wasting my time with that code a long time ago.
But the braves who tried using the latest u-boot mainline code that does
not configure anything anymore had some troubles...
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: Benoit Cousson <b-cousson@ti.com>
To: Luciano Coelho <coelho@ti.com>
Cc: <balbi@ti.com>, Peter Ujfalusi <peter.ujfalusi@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
<svenkatr@ti.com>, <linux-omap@vger.kernel.org>,
<linux-mmc@vger.kernel.org>, <cjb@laptop.org>, <lrg@ti.com>,
<linux-kernel@vger.kernel.org>, Tony Lindgren <tony@atomide.com>,
<r.sricharan@ti.com>
Subject: Re: 32kHz clock removal causes problems omap_hsmmc
Date: Wed, 19 Dec 2012 15:04:07 +0100 [thread overview]
Message-ID: <50D1C957.8090201@ti.com> (raw)
In-Reply-To: <1355925504.5273.26.camel@cumari.coelho.fi>
On 12/19/2012 02:58 PM, Luciano Coelho wrote:
> On Wed, 2012-12-19 at 14:51 +0100, Benoit Cousson wrote:
>> On 12/19/2012 02:01 PM, Felipe Balbi wrote:
>>> On Wed, Dec 19, 2012 at 11:56:20AM +0100, Peter Ujfalusi wrote:
>>>> BTW: have you happened to ubdate u-boot recently? There is a nice easter egg
>>>> added there:
>>>> f3f98bb ARM: OMAP4/5: Do not configure non essential pads, clocks, dplls.
>>>>
>>>> Which means that _essential_ clocks and pads are no longer configured.
>>>
>>> anything essential you can list ?
>>
>> Yeah, that u-boot version is just unusable at all with any mainline
>> kernel, since we are still missing pads conf for every drivers.
>>
>> Regarding the 32k clock, I noticed as well that the OMAP4460 panda
>> u-boot is the only one to enable it at boot time, and thus this is the
>> only board that can probe the wilink chip properly as of today.
>
> Do you mean that with the latest mainline u-boot all boards will have
> trouble except panda?
I don't know since the u-boot mainline has never ever supported properly
the SDP4430, I stopped wasting my time with that code a long time ago.
But the braves who tried using the latest u-boot mainline code that does
not configure anything anymore had some troubles...
Benoit
next prev parent reply other threads:[~2012-12-19 14:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 8:31 32kHz clock removal causes problems omap_hsmmc Luciano Coelho
2012-11-15 8:31 ` Luciano Coelho
2012-12-18 9:54 ` Felipe Balbi
2012-12-18 9:54 ` Felipe Balbi
2012-12-19 9:45 ` Mark Brown
2012-12-19 10:00 ` Peter Ujfalusi
2012-12-19 10:00 ` Peter Ujfalusi
2012-12-19 10:09 ` Mark Brown
2012-12-19 10:18 ` Peter Ujfalusi
2012-12-19 10:18 ` Peter Ujfalusi
2012-12-19 10:32 ` Mark Brown
2012-12-19 10:45 ` Luciano Coelho
2012-12-19 10:45 ` Luciano Coelho
2012-12-19 10:56 ` Peter Ujfalusi
2012-12-19 10:56 ` Peter Ujfalusi
2012-12-19 11:00 ` Peter Ujfalusi
2012-12-19 11:00 ` Peter Ujfalusi
2012-12-19 11:02 ` Mark Brown
2012-12-19 11:07 ` Luciano Coelho
2012-12-19 11:07 ` Luciano Coelho
2012-12-19 13:01 ` Felipe Balbi
2012-12-19 13:01 ` Felipe Balbi
2012-12-19 13:51 ` Benoit Cousson
2012-12-19 13:51 ` Benoit Cousson
2012-12-19 13:54 ` Felipe Balbi
2012-12-19 13:54 ` Felipe Balbi
2012-12-19 13:58 ` Mark Brown
2012-12-19 13:58 ` Luciano Coelho
2012-12-19 13:58 ` Luciano Coelho
2012-12-19 14:04 ` Benoit Cousson [this message]
2012-12-19 14:04 ` Benoit Cousson
2012-12-19 18:06 ` R Sricharan
2012-12-19 18:06 ` R Sricharan
2012-12-19 14:31 ` Peter Ujfalusi
2012-12-19 14:31 ` Peter Ujfalusi
2012-12-19 16:28 ` Tony Lindgren
2012-12-19 10:01 ` Luciano Coelho
2012-12-19 10:01 ` Luciano Coelho
2012-12-19 10:28 ` Mark Brown
2012-12-19 10:42 ` Luciano Coelho
2012-12-19 10:42 ` Luciano Coelho
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=50D1C957.8090201@ti.com \
--to=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cjb@laptop.org \
--cc=coelho@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=r.sricharan@ti.com \
--cc=svenkatr@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.