[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50D1C957.8090201@ti.com>
Date: Wed, 19 Dec 2012 15:04:07 +0100
From: Benoit Cousson <b-cousson@...com>
To: Luciano Coelho <coelho@...com>
CC: <balbi@...com>, Peter Ujfalusi <peter.ujfalusi@...com>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
<svenkatr@...com>, <linux-omap@...r.kernel.org>,
<linux-mmc@...r.kernel.org>, <cjb@...top.org>, <lrg@...com>,
<linux-kernel@...r.kernel.org>, Tony Lindgren <tony@...mide.com>,
<r.sricharan@...com>
Subject: Re: 32kHz clock removal causes problems omap_hsmmc
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists