|To:||"Maciej W. Rozycki" <email@example.com>|
|Subject:||Re: [PATCH 3/5] Deforest the function pointer jungle in the time code.|
|From:||"Franck Bui-Huu" <firstname.lastname@example.org>|
|Date:||Thu, 14 Jun 2007 16:31:47 +0200|
|Cc:||"Thomas Bogendoerfer" <email@example.com>, firstname.lastname@example.org, "Ralf Baechle" <email@example.com>|
|Dkim-signature:||a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BO8ZE9KmjLS69JSvmvqmaTYny6OWZ0lp2SpFwkx5o4r9nv3QioxdqdhRlap3GGvXgrDsXxm7Dxh7axO58xh5lK7N9+VVTWIY2SFH+OEOoqs47vtLQaPv+bmQx2nhr50/GCQwhwfOLdSrX2wllGK/hOx6g1gceo3KA5n9moA5uGk=|
|Domainkey-signature:||a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LkRr9+DPds71/7er9fFBX2ACUR6NH3ryWyLRWqekr941rB8u5p0HVhFEQiZOfe/bkMLN/staCsl8UAj7nmPVADZEIdBTlfWqFuZ4Wmhvi8Ccac2KLtHTnKprRpoepM9sqbXqZCQaTTZOFTQI3HCawKuKK8Tcz/kWvlvYFXCqPbY=|
|References:||<firstname.lastname@example.org> <email@example.com> <20070614111748.GA8223@alpha.franken.de> <firstname.lastname@example.org> <Pine.LNX.4.64N.email@example.com>|
Hi, On 6/14/07, Maciej W. Rozycki <firstname.lastname@example.org> wrote:
On Thu, 14 Jun 2007, Franck Bui-Huu wrote: > The current code doesn't automatically calibrate any hpt. It was > really hard to guess which ones need that so now if you need to > calibrate your hpt, then you have to call calibrate_hpt(). You are wrong -- calibration is currently automatic if a platform provides a HPT, but has not set up its frequency:
Well it all depends on what you call "current" code... My own fault I should have said "new" instead of "current", sorry.
Which should normally be the case unless there is no way to do calibration, when a platform can provide a hardcoded value. There is nothing to guess here.
Are you sure it's the normal case? I would say that only DEC needs that calibration: Doing the following on the _current_ tree: $ git grep -l mips_timer_state arch/mips arch/mips/dec/time.c arch/mips/kernel/time.c
I'll have a look at your patches, but I hope you have got about the most interesting configuration right, which is the DEC platform, where you can have one of these:
As I said, all platforms haven't been migrated, but DEC seems an interesting one to migrate. I'll try to do it and see if you can accept such changes.
1. No HPT at all. 2. HPT in the chipset. 3. HPT in CP0. depending on the configuration as determined at the run time, with no predefined frequency in the cases #2 and #3.
Good to know. Thanks -- Franck
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH 3/5] Deforest the function pointer jungle in the time code., Maciej W. Rozycki|
|Next by Date:||Re: [PATCH 3/5] Deforest the function pointer jungle in the time code., Franck Bui-Huu|
|Previous by Thread:||Re: [PATCH 3/5] Deforest the function pointer jungle in the time code., Maciej W. Rozycki|
|Next by Thread:||Re: [PATCH 3/5] Deforest the function pointer jungle in the time code., Maciej W. Rozycki|
|Indexes:||[Date] [Thread] [Top] [All Lists]|