From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [patch] pnx8xxx clocksource cleanups
Date: Sat, 12 Jan 2008 20:21:02 +0300 [thread overview]
Message-ID: <4788F6FE.6000803@ru.mvista.com> (raw)
In-Reply-To: <4788BAAC.3020908@gmail.com>
Hello.
Vitaly Wool wrote:
> This patch does some PNX8XXX clocksource cleanups.
> Signed-off-by: Vitaly Wool <vitalywool@gmail.com>
> Index: linux-mips.git/arch/mips/philips/pnx8550/common/time.c
> ===================================================================
> --- linux-mips.git.orig/arch/mips/philips/pnx8550/common/time.c
> +++ linux-mips.git/arch/mips/philips/pnx8550/common/time.c
> @@ -47,11 +47,6 @@ static struct clocksource pnx_clocksourc
> .flags = CLOCK_SOURCE_IS_CONTINUOUS,
> };
>
> -static void timer_ack(void)
> -{
> - write_c0_compare(cpj);
> -}
> -
> static irqreturn_t pnx8xxx_timer_interrupt(int irq, void *dev_id)
> {
> struct clock_event_device *c = dev_id;
> @@ -94,30 +89,22 @@ static struct clock_event_device pnx8xxx
> .set_next_event = pnx8xxx_set_next_event,
> };
>
> -/*
> - * plat_time_init() - it does the following things:
> - *
> - * 1) plat_time_init() -
> - * a) (optional) set up RTC routines,
> - * b) (optional) calibrate and set the mips_hpt_frequency
> - * (only needed if you intended to use cpu counter as timer
> interrupt
> - * source)
> - */
> +static inline void timer_ack(void)
> +{
> + write_c0_compare(cpj);
> +}
I still don't understand why you need this function at all, and the 'cpj'
variable as well -- clockevents core will set the comparator to a needed
value. Also, I don't see much value in moving that function...
WBR, Sergei
next prev parent reply other threads:[~2008-01-12 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 13:03 [patch] pnx8xxx clocksource cleanups Vitaly Wool
2008-01-12 17:21 ` Sergei Shtylyov [this message]
2008-01-12 20:40 ` Vitaly Wool
2008-01-14 0:18 ` Ralf Baechle
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=4788F6FE.6000803@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=vitalywool@gmail.com \
/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