linux-kernel - Re: 32kHz clock removal causes problems omap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <50D2023F.1000609@ti.com>
Date:	Wed, 19 Dec 2012 23:36:55 +0530
From:	R Sricharan <r.sricharan@...com>
To:	Benoit Cousson <b-cousson@...com>
CC:	Luciano Coelho <coelho@...com>, <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>
Subject: Re: 32kHz clock removal causes problems omap_hsmmc

Hi,

On Wednesday 19 December 2012 07:34 PM, Benoit Cousson wrote:
> 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...
>
   Configuring every pad and clocks in the u-boot was removed to
   force kernel drivers to fix up things. Dependency on boot loader
   was always a problem. Bootloader should not configure anything apart
   from what is required for boot.

Regards,
  Sricharan


--
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/