From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Tue, 21 May 2013 21:25:33 +0200
Subject: [U-Boot] [PATCH] arm: pxa: config option for PXA270 turbo mode
In-Reply-To: <1369153427.12900.19.camel@host5.omatika.ru>
References: <1369086285-25838-1-git-send-email-ynvich@gmail.com>
	<201305211322.57243.marex@denx.de>
	<1369153427.12900.19.camel@host5.omatika.ru>
Message-ID: <201305212125.33226.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Sergey Yanovich,

> On Tue, 2013-05-21 at 13:22 +0200, Marek Vasut wrote:
> > > Actually, I wonder if Linux's cpufreq still does depend on bootloader
> > > speed settings. Especially the turbo bit. Can you please check that?
> > > It'd be interesting to know ...
> > > 
> > > I'd say enable it by default ... I probably have all the PXA devices
> > > supported in U-Boot and I'm quite sure none of them will mind ;-)
> > 
> > Still, I'm surprised it wasn't enabled. I recall seeing it enabled. Weird
> > ...
> 
> Yes, you are right. Linux's cpufreq-pxa2xx.c always sets the turbo bit.
> 
> However, if CONFIG_CPU_FREQ is not set (my case), bootloader's settings
> are used.
> 
> I work on a system that has focus on low latency (industrial controller)
> rather than battery life (since it has no battery).

So why not just make this patch into

-(2)
+(0xb)

instead of adding new (and undocumented ...) macro?

Best regards,
Marek Vasut