ARM: OMAP2+: clock code migration to drivers/clk/ti
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest0 of 27 patches 0 repliesNew
Patches in v2 No applies recorded yet
None of the 27 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCHv2 00/27] ARM: OMAP2+: clock code migration to drivers/clk/ti
Quoted 32 lines · Tero Kristo
Quoted 31 lines · Paul Walmsley
Quoted 3 lines · Tero Kristo
Any news on this? As noted previously, I am not able to reproduce the issue
you are seeing currently, can you giveDEBUG_LLa shot?Yeah I just bisected it, it was caused by this:
commit
cc4a5fe972ad7834e8662b49b3a5fdb597e9e15eAuthor: Felipe Balbi <[email protected]> Date: Fri Jan 30 11:18:56 2015 -0600arm: config:
omap2plus_defconfig: switch over to LZMA compressionLZMA compression makes about 33% smaller zImage with just a slight extra decompression time.
Before this patch, zImage built with o2+_dc
is 4.5MiB and after it's about 3.3MiB.Suggested-by David Cohen <[email protected]>Signed-off-by Felipe Balbi <[email protected]>Signed-off-by Tony Lindgren <[email protected]>and the timeouts on the testbed being set to fail if a kernel takes longer
than five seconds to start. Seems that the part about a "slight extra decompression time" probably only applies to relatively recent chips.
Quoted 6 lines
Quoted 2 lines
- Paul
Oh, so this explains why I was thinking it took very long time to boot the recent kernels also. The boot lag is clearly noticeable without any measurement. I wonder if we should probably revert this patch.
we already have issues with zImage size bloating up and running headlong into dtb - esp on platforms like N900. Felipe spend quiet some time getting things into a manageable size here -> loosing 33% sounds like bad idea to me :(
Signature · 2 lines
Regards, Nishanth Menon