linux-mips
[Top] [All Lists]

Re: [PATCH 3/5] Deforest the function pointer jungle in the time code.

To: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Subject: Re: [PATCH 3/5] Deforest the function pointer jungle in the time code.
From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
Date: Tue, 19 Jun 2007 19:00:12 +0200
Cc: ralf@linux-mips.org, macro@linux-mips.org, sshtylyov@ru.mvista.com, linux-mips@linux-mips.org
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=qkRQ8v31O+zOx3AnZN9L5KRleg3UavN8+sFeyWt9D7v/tQrz+EI+A7AFigroKxDIxb726O4kn+JceDK6VtGiAp2kSiGyCpZHAXfrcP5HEtq7KU/UAgiFb1HJDkXzERHKlOLF/L+jJtKKrz0IqL+lkAiNldic1kQlbfbejCj/wJY=
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=hcZ9gCw2DLnJeeghY+jAyC2FscgIPCK7m1Bqso8liuo94ZCo5+zkF2kymNSSDpR5oTkjxznMHtjYlXJjl7P1bojsw6buW0UCf/JP/IxbOoXnYp0jgv26DkkL57joH3em81h/3kZYeY+UqhW4TIhKI9z/OzP6rwQrMtqJOUIn0Y0=
In-reply-to: <20070620.010805.23009775.anemo@mba.ocn.ne.jp>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <cda58cb80706180238r17da4434jcdee307b0385729b@mail.gmail.com> <20070619.005121.118948229.anemo@mba.ocn.ne.jp> <cda58cb80706190033y47ccec58u8fc8254ced24f96f@mail.gmail.com> <20070620.010805.23009775.anemo@mba.ocn.ne.jp>
Sender: linux-mips-bounce@linux-mips.org
On 6/19/07, Atsushi Nemoto <anemo@mba.ocn.ne.jp> wrote:
On Tue, 19 Jun 2007 09:33:33 +0200, "Franck Bui-Huu" <vagabon.xyz@gmail.com> 
wrote:
> What do you mean by "pnx8550 can have customized copy of cp0_hpt
> routines" ? Do you mean that it should copy the whole clock event
> driver ?
>
> It seems to me that using cp0 hpt as a clock event only is a valid usage...

Well, I thought the customized cp0 clockevent codes (custom
.set_next_event routine is needed anyway, isn't it?)

I don't think so.

hpt-cp0.c clock event part doesn't care if the counter is cleared when
an interrupt is triggered. It matters only for clock source (well I
think) that's why I suggested to rewrite a clock source driver only
for this platform...

--
              Franck

<Prev in Thread] Current Thread [Next in Thread>