From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dirk Behme Date: Mon, 27 Apr 2009 17:07:01 +0200 Subject: [U-Boot] [PATCH v3] OMAP3: Fix timer handling to 1ms and CONFIG_SYS_HZ to 1000 In-Reply-To: <20090426212427.GA32215@game.jcrosoft.org> References: <1240327745-8917-1-git-send-email-dirk.behme@googlemail.com> <20090426212427.GA32215@game.jcrosoft.org> Message-ID: <49F5CA15.9080007@googlemail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Jean-Christophe, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 17:29 Tue 21 Apr , Dirk Behme wrote: >> From: Manikandan Pillai >> Signed-off-by: Dirk Behme >> Signed-off-by: Manikandan Pillai >> --- > as Request precedently switch to 12Mhz source clock or As answered already in (unanswered) http://lists.denx.de/pipermail/u-boot/2009-April/050078.html switch to 12MHz will have a larger code and implementation impact while we won't win anything compared to well tested 13MHz usage http://lists.denx.de/pipermail/u-boot/2009-April/051258.html > please specify the timer resolution & precision of your implementation and > put in the commit message & code It seems to me that you mix here OMAP1 and OMAP3 patches? I remember about http://lists.denx.de/pipermail/u-boot/2009-April/051271.html which is regarding arm925/OMAP1 changes, not OMAP3 patch. I can't remember anything similar regarding OMAP3 patch. And similar comment for OMAP3 patch wouldn't make sense as http://lists.denx.de/pipermail/u-boot/2009-April/051178.html has clear info + * We run the counter with 13MHz, divided by 8, resulting in timer + * frequency of 1.625MHz. With 32bit counter register, counter + * overflows in ~44min Dirk