From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jon Hunter <jon-hunter@ti.com>
Date: Thu, 21 Mar 2013 10:17:22 -0500
Subject: [U-Boot] [PATCH 1/1 v3] console: USB: KBD: Fix incorrect
 autoboot timeout
In-Reply-To: <20130321065742.9271E200547@gemini.denx.de>
References: <1359025555-15119-1-git-send-email-jilin@nvidia.com>
	<514A4CBA.1040203@ti.com> <514AA642.3090107@wwwdotorg.org>
	<20130321065742.9271E200547@gemini.denx.de>
Message-ID: <514B2482.5000002@ti.com>
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


On 03/21/2013 01:57 AM, Wolfgang Denk wrote:
> Dear Stephen Warren,
> 
> In message <514AA642.3090107@wwwdotorg.org> you wrote:
>>
>> Interesting. I just noticed the same problem, and posted the following
>> patch to fix it:
>>
>> http://lists.denx.de/pipermail/u-boot/2013-March/149625.html
>>
>> This was on the Raspberry Pi.
> 
> You mean the Raspberry Pi uses SYS_HZ != 1000 ???
> 
> This needs fixing!!

I understand that you may wish to have SYS_HZ == 1000, but shouldn't the
code still normalise the get_timer() value to SYS_HZ?

If I grep through the u-boot source I see a lot of instances where
get_timer() is normalised to SYS_HZ.

grep -r "get_timer" * | grep "SYS_HZ"

Cheers
Jon