public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhu, Yi" <yi.zhu@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] RTC support on ia64
Date: Tue, 01 Jul 2003 06:11:13 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105704038522357@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805600@msgid-missing>


Hi Joel,

Do you have the ia64 rtc patch for 2.4 kernel? I need the rtc
driver to test the latency with realfeel.

Thanks,
-yi

> -----Original Message-----
> From: Joel GUILLET [mailto:Joel.Guillet@bull.net]
> Sent: Wednesday, December 18, 2002 12:26 AM
> To: linux-ia64@linuxia64.org
> Subject: [Linux-ia64] RTC support on ia64
> 
> 
> 
> Hi,
> 
> Here is a patch to use the Real Time Clock (RTC) on ia64.
> It works on a tiger. It doesn't on early lion machines. (Why ?)
> I don't know about others ia64 machines. Please report me - 
> if you test
> it.
> To see if it works, please check the /var/log/messages. The 
> driver reports
> sometimes that "rtc losts some interrupts..." It usually 
> means that the
> rtc doesn't work, and the interruptions that arrived were 
> coming from a
> software-timer (see the driver code).
> 
> 
> This patch is very simple.
> I changed the irq affected for the rtc as it is an "ex-i386" 
> interruption.
> (an Ox20 offset)
> And copied some files from the asm-i386 to asm-ia64...
> The duplication of these files is a waste of disk space, but 
> it's coherent
> with the way it has been made on i386.
> 
> You may want to try this patch and test it.
> There is a program test included in the Documentation/rtc.txt of the
> kernel tree.
> 
> The actual priority of the interruption is low but perhaps it might be
> changed (Do anyone know how to make it ?) for some usages.
> 
> For the kernel releases after 2.5.45, I've seen that the 
> Kconfig will be
> modified so that the option will not be available (unless you 
> activate it
> manually).
> 
> This can be used for example to run scheduler latencies tests 
> (a way of
> using amlat) - I've got some more stuff for this, please mail me.
> 
> Here is the patch :
> 
> 
> ********************************************
> diff -urN linux-2.5.45/arch/ia64/kernel/ia64_ksyms.c 
> linux-2.5.45-clean/arch/ia64/kernel/ia64_ksyms.c
> --- linux-2.5.45/arch/ia64/kernel/ia64_ksyms.c	Thu Oct 
> 31 01:42:54 2002
> +++ linux-2.5.45-clean/arch/ia64/kernel/ia64_ksyms.c	Tue Dec 
> 17 15:08:19 2002
> @@ -143,3 +143,5 @@
>  #endif
>  EXPORT_SYMBOL(machvec_noop);
> 
> +extern spinlock_t rtc_lock;
> +EXPORT_SYMBOL(rtc_lock);
> diff -urN linux-2.5.45/arch/ia64/kernel/time.c 
> linux-2.5.45-clean/arch/ia64/kernel/time.c
> --- linux-2.5.45/arch/ia64/kernel/time.c	Thu Oct 31 01:42:20 2002
> +++ linux-2.5.45-clean/arch/ia64/kernel/time.c	Tue Dec 
> 17 15:08:19 2002
> @@ -27,6 +27,7 @@
>  extern rwlock_t xtime_lock;
>  extern unsigned long wall_jiffies;
>  extern unsigned long last_time_offset;
> +spinlock_t rtc_lock = SPIN_LOCK_UNLOCKED;
> 
>  u64 jiffies_64;
> 
> diff -urN linux-2.5.45/include/asm-ia64/mc146818rtc.h 
> linux-2.5.45-clean/include/asm-ia64/mc146818rtc.h
> --- linux-2.5.45/include/asm-ia64/mc146818rtc.h	Thu Oct 
> 31 01:43:38 2002
> +++ linux-2.5.45-clean/include/asm-ia64/mc146818rtc.h	Tue Dec 
> 17 15:10:12 2002
> @@ -1,10 +1,29 @@
> +/*
> + * Machine dependent access functions for RTC registers.
> + */
>  #ifndef _ASM_IA64_MC146818RTC_H
>  #define _ASM_IA64_MC146818RTC_H
> 
> +#include <asm/io.h>
> +
> +#ifndef RTC_PORT
> +#define RTC_PORT(x)	(0x70 + (x))
> +#define RTC_ALWAYS_BCD	1	/* RTC operates in 
> binary mode */
> +#endif
> +
>  /*
> - * Machine dependent access functions for RTC registers.
> + * The yet supported machines all access the RTC index register via
> + * an ISA port access but the way to access the date 
> register differs ...
>   */
> +#define CMOS_READ(addr) ({ \
> +outb_p((addr),RTC_PORT(0)); \
> +inb_p(RTC_PORT(1)); \
> +})
> +#define CMOS_WRITE(val, addr) ({ \
> +outb_p((addr),RTC_PORT(0)); \
> +outb_p((val),RTC_PORT(1)); \
> +})
> 
> -/* empty include file to satisfy the include in genrtc.c */
> +#define RTC_IRQ 40 /* irq on a i386 + Ox20  */
> 
>  #endif /* _ASM_IA64_MC146818RTC_H */
> diff -urN linux-2.5.45/include/asm-ia64/rtc.h 
> linux-2.5.45-clean/include/asm-ia64/rtc.h
> --- linux-2.5.45/include/asm-ia64/rtc.h	Thu Jan  1 01:00:00 1970
> +++ linux-2.5.45-clean/include/asm-ia64/rtc.h	Tue Dec 17 15:09:03 2002
> @@ -0,0 +1,10 @@
> +#ifndef _IA64_RTC_H
> +#define _IA64_RTC_H
> +
> +/*
> + * ia64 uses the default access methods for the RTC.
> + */
> +
> +#include <asm-generic/rtc.h>
> +
> +#endif
> **************************************************************
> 
> 
> --------------
> **  Joel
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 

  parent reply	other threads:[~2003-07-01  6:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 16:26 [Linux-ia64] RTC support on ia64 Joel GUILLET
2002-12-17 20:13 ` Alex Williamson
2002-12-17 21:57 ` Peter Chubb
2002-12-17 23:57 ` David Mosberger
2002-12-18 15:01 ` Joel GUILLET
2002-12-18 18:18 ` Stephane Eranian
2002-12-18 19:26 ` Alex Williamson
2003-07-01  6:11 ` Zhu, Yi
2003-07-01  6:11 ` Zhu, Yi [this message]
2003-07-01 12:15 ` Eric Piel
2003-07-01 22:53 ` Peter Chubb
2003-07-02  0:45 ` Zhu, Yi

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=marc-linux-ia64-105704038522357@msgid-missing \
    --to=yi.zhu@intel.com \
    --cc=linux-ia64@vger.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