Skip to content

ARM: OMAP2+: clock code migration to drivers/clk/ti

Tony Lindgren linux-arm-kernel linux-clk linux-omap 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v2 Latest1 of 27 patches 0 repliesNew

1 of 27 patches is in this archive. The cover letter announces 27.

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
2/27clk: ti: move generic OMAP DPLL implementation under drivers/clk+0 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCHv2 00/27] ARM: OMAP2+: clock code migration to drivers/clk/ti
Quoted 36 lines · Nishanth Menon
Quoted 35 lines · Tero Kristo
Quoted 33 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 give DEBUG_LL a shot?

Yeah I just bisected it, it was caused by this:

commit cc4a5fe972ad7834e8662b49b3a5fdb597e9e15e

Author: Felipe Balbi <[email protected]>
Date:   Fri Jan 30 11:18:56 2015 -0600

arm: config: omap2plus_defconfig: switch over to LZMA compression

LZMA 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.

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.

- Paul

Quoted 8 lines
Quoted 3 lines

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 :(

If it affects people using the slower 34xx systems we should probably revert it though. Or make the uncompress somehow faster :)

Regards,

Tony