Dear Wolfgang Denk,
On 10 January 2011 01:14, Wolfgang Denk <wd@denx.de> wrote:
> Dear Minkyu Kang,>> In message <4D22D59B.7030902@samsung.com> you wrote:>> Use the global data instead of bss variable, replace as follow.>> count_value -> timer_rate_hz>> timestamp -> timer_reset_value>> lastdec -> lastinc>> I object against using variables wich have somewhat self-explanatory> names for different purposes.>
Yes, I know.
If so, do I have to add new variables at global_data?
Maybe that is not good way too.
How you think?
One more question,
what is the purpose of tbl and tbu?
Thanks
Minkyu Kang

Dear Minkyu Kang,
In message <AANLkTikoZFrd9SYLg4v3AoqRFEd9bM0jpQQOi+Qzy6eg@mail.gmail.com> you wrote:
> > > I object against using variables wich have somewhat self-explanatory> > names for different purposes.> > Yes, I know.> If so, do I have to add new variables at global_data?> Maybe that is not good way too.> How you think?
I asked this several times before: ther eis currently ongoing efforts
for aunified clock handling for ARM in the Linux kernel. Maybe we can
benefit from this in any way?
> One more question,> what is the purpose of tbl and tbu?
tbl (time base, lower part) and tbu (time base, upper part) are the
software representation of two 32 bit hardware registers available in
Power Architecture systems, where they form a free-runnign 64 bit
counter that starts automatically as soon as the CPU comes out of
reeset.
There have been attempts to re-write the (sometimes somewhat obscure)
timer implementations on ARM based on such a model.
Best regards,
Wolfgang Denk