[PATCHv2 00/27] ARM: OMAP2+: clock code migration to drivers/clk/ti

[Tero Kristo]

On 05/13/2015 05:55 PM, Paul Walmsley wrote:
> On Wed, 13 May 2015, Tero Kristo wrote:
>
>> I clipped the boot-loader traces as they contain lots of noise from the
>> test-automation system.
>>
>> Looking at the farm traces, I see this on the omap3 boards:
>>
>> beagleboard-vanilla.txt:ver=U-Boot 2014.04-00071-g8543283 (Apr 22 2014 -
>> 15:49:50)
>>
>> beagle-xm.txt:U-Boot 2014.10-00004-g9ade0ab-dirty (Dec 16 2014 - 13:40:24)
>>
>> craneboard.txt:U-Boot 2009.11-00005-ge83d2db (Dec 07 2010 - 11:55:34)
>>
>> ldp.txt:U-Boot 2014.04-00071-g8543283-dirty (Apr 25 2014 - 14:59:48)
>>
>> n900.txt:U-Boot 2014.04-00073-g4fa5b9e (Apr 22 2014 - 14:37:10)
>>
>> sdp3430.txt:U-Boot 2009.11-rc1-00485-g7d1e865 (Nov 09 2009 - 11:21:55)
>>
>> Maybe some DTB issues? When did you update your DTB files?
>
> For all of the uImage+DTB boots, the DTB files in use follow the kernel
> version:
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc1/20150426200156/dtbs/
>
> which are then subsequently combined to produce:
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc1/20150426200156/dtcat/
>
> So, using the OMAP35xx Beagle as an example, you can prove to yourself
> that the current DTB is in use by observing that U-boot is loading a
> combined uImage+DTB file of 3495180 bytes from here:
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc1/20150426200156/boot/3530es3beagle/3530es3beagle_log.txt
>
> and comparing that with the size of this file (3495180 bytes):
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc1/20150426200156/dtcat/omap2plus_defconfig/uImage-dtb.omap3-beagle
>
> and observing that this file size is the sum of the DTB file size (63180
> bytes):
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc1/20150426200156/dtbs/omap3-beagle.dtb
>
> and the zImage file size (3431936 bytes):
>
> http://www.pwsan.com/omap/testlogs/test_v4.1-rc1/20150426200156/build_z/omap2plus_defconfig/zImage
>
> and the 64 byte uImage header.
>
>
> The only board that I suspect may be using an old DTB is the 4460
> VAR-SOM-OM.
>
>
> - Paul
>

Any news on this? As noted previously, I am not able to reproduce the 
issue you are seeing currently, can you give DEBUG_LL a shot?

-Tero