public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Thomas Chou <thomas@wytron.com.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] nios2: Set CONFIG_SYS_HZ to 1000 all nios2 boards.
Date: Wed, 31 Mar 2010 11:04:27 +0800	[thread overview]
Message-ID: <4BB2BBBB.4000702@wytron.com.tw> (raw)
In-Reply-To: <4BB2AEC0.7000501@psyent.com>

On 03/31/2010 10:09 AM, Scott McNutt wrote:
>> So it might be cleaner to let user define the HZ as the actual tick rate
>> and increase the tick count by one in the tmr_isr.
>>      
> This was discussed/debated thoroughly over the past year:
> CONFIG_SYS_HZ at 1000 is mandatory.
>
>    
>> -    timestamp += CONFIG_SYS_NIOS_TMRMS;
>> +    timestamp++;
>>      
> This means that each interrupt is exactly 1 msec. That's not what
> was intended and not what was implemented Forcing the interrupt
> period to 1 msec is an unnecessary constraint. If you want the isr
> to increment the timestamp by 1, then set CONFIG_SYS_NIOS_TMRMS to 1
> ... and set your timer accordingly.
>
> -
>    
Hi Scott,

Thanks for the explanation. I will set HZ to 1000 and TMRMS to 1.

I tried to follow your patch "nios2: Set CONFIG_SYS_HZ to 1000 all nios2 
boards". But got cfi flash buffer write timeout on EP2C35 board. If I 
set TMRMS to 1, it works with HZ at 100, 1000 and 2000.

Best regards,
Thomas

  reply	other threads:[~2010-03-31  3:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31  2:09 [U-Boot] [PATCH] nios2: Set CONFIG_SYS_HZ to 1000 all nios2 boards Scott McNutt
2010-03-31  3:04 ` Thomas Chou [this message]
2010-03-31  4:14   ` Scott McNutt
  -- strict thread matches above, loose matches on Subject: below --
2010-03-31  1:00 Scott McNutt
2010-04-01  7:23 ` Michal Simek
2010-04-01 11:46   ` Scott McNutt
2010-04-01 16:59     ` Michal Simek
2010-04-02  1:15       ` Scott McNutt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BB2BBBB.4000702@wytron.com.tw \
    --to=thomas@wytron.com.tw \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox