From: Thomas Gleixner <tglx@linutronix.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/platform: add a wallclock_init func to x86_platforms ops
Date: Tue, 25 Jan 2011 16:20:17 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1101251618210.31804@localhost6.localdomain6> (raw)
In-Reply-To: <20110125142613.9886.69516.stgit@bob.linux.org.uk>
On Tue, 25 Jan 2011, Alan Cox wrote:
> From: Feng Tang <feng.tang@intel.com>
>
> Some wall clock devices use MMIO based HW register, this new function will
> give them a chance to do some initialization work before their get/set_time
> service get called.
>
> Signed-off-by: Feng Tang <feng.tang@intel.com>
> Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>
> arch/x86/include/asm/x86_init.h | 2 ++
> arch/x86/kernel/setup.c | 2 ++
> arch/x86/kernel/x86_init.c | 2 ++
> 3 files changed, 6 insertions(+), 0 deletions(-)
>
>
> diff --git a/arch/x86/include/asm/x86_init.h b/arch/x86/include/asm/x86_init.h
> index 64642ad..f7fa2e7 100644
> --- a/arch/x86/include/asm/x86_init.h
> +++ b/arch/x86/include/asm/x86_init.h
> @@ -138,6 +138,7 @@ struct x86_cpuinit_ops {
> /**
> * struct x86_platform_ops - platform specific runtime functions
> * @calibrate_tsc: calibrate TSC
> + * @wallclock_init: init the wallclock device
That's a one time called init function, so it should go into
x86_init_ops.
Thanks,
tglx
next prev parent reply other threads:[~2011-01-25 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 14:26 Alan Cox
2011-01-25 14:26 ` [PATCH 2/2] mrst/vrtc: avoid using CMOS RTC ops Alan Cox
[not found] ` <AANLkTi=KQ-5=h-iDPRtBRvy45jafQxxhyJu4UPCxZ6Lg@mail.gmail.com>
2011-01-27 1:50 ` Feng Tang
2011-01-25 15:20 ` Thomas Gleixner [this message]
[not found] <20110125153813.4aa1e7cc@lxorguk.ukuu.org.uk>
2011-01-26 3:03 ` [PATCH 1/2] x86/platform: add a wallclock_init func to x86_platforms ops Feng Tang
2011-01-26 12:26 ` Thomas Gleixner
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=alpine.LFD.2.00.1101251618210.31804@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®