From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCHv2 00/27] ARM: OMAP2+: clock code migration to
 drivers/clk/ti
Date: Thu, 21 May 2015 11:38:32 -0700
Message-ID: <20150521183832.GU10274@atomide.com>
References: <1431334493-24455-1-git-send-email-t-kristo@ti.com>
 <alpine.DEB.2.02.1505111747460.19833@utopia.booyaka.com>
 <5551D178.3000904@ti.com>
 <alpine.DEB.2.02.1505122019220.21747@utopia.booyaka.com>
 <5552F32C.7060606@ti.com>
 <alpine.DEB.2.02.1505131438430.7921@utopia.booyaka.com>
 <555B8DC0.5080905@ti.com>
 <alpine.DEB.2.02.1505202234330.7960@utopia.booyaka.com>
 <555D7D52.8010501@ti.com>
 <555D82CB.5060300@ti.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <linux-omap-owner@vger.kernel.org>
Received: from muru.com ([72.249.23.125]:52878 "EHLO muru.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756325AbbEUSif (ORCPT <rfc822;linux-omap@vger.kernel.org>);
	Thu, 21 May 2015 14:38:35 -0400
Content-Disposition: inline
In-Reply-To: <555D82CB.5060300@ti.com>
Sender: linux-omap-owner@vger.kernel.org
List-Id: linux-omap@vger.kernel.org
To: Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, Paul Walmsley <paul@pwsan.com>, mturquette@linaro.org, linux-omap@vger.kernel.org, linux-clk@vger.kernel.org, sboyd@codeaurora.org, linux-arm-kernel@lists.infradead.org

* Nishanth Menon <nm@ti.com> [150521 00:03]:
> On 05/21/2015 01:38 AM, Tero Kristo wrote:
> > On 05/21/2015 01:40 AM, Paul Walmsley wrote:
> >> On Tue, 19 May 2015, Tero Kristo wrote:
> >>
> >>> 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 <balbi@ti.com>
> >> 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.
> >>
> >>      Suggested-by: David Cohen <david.a.cohen@linux.intel.com>
> >>      Signed-off-by: Felipe Balbi <balbi@ti.com>
> >>      Signed-off-by: Tony Lindgren <tony@atomide.com>
> >>
> >>
> >> 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
> >>
> > 
> > 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