1993-06-12 14:58:17 +00:00
|
|
|
/*-
|
2017-11-27 15:11:47 +00:00
|
|
|
* SPDX-License-Identifier: BSD-2-Clause-FreeBSD
|
|
|
|
*
|
2008-04-14 07:57:15 +00:00
|
|
|
* Copyright (c) 2008 Poul-Henning Kamp
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
* Copyright (c) 2010 Alexander Motin <mav@FreeBSD.org>
|
1993-06-12 14:58:17 +00:00
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
*
|
2008-04-14 07:57:15 +00:00
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
1993-06-12 14:58:17 +00:00
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
2008-04-14 07:57:15 +00:00
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
1993-06-12 14:58:17 +00:00
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
*
|
2008-04-14 07:57:15 +00:00
|
|
|
* $FreeBSD$
|
1996-10-25 13:46:21 +00:00
|
|
|
*/
|
|
|
|
|
2003-06-02 16:32:55 +00:00
|
|
|
#include <sys/cdefs.h>
|
|
|
|
__FBSDID("$FreeBSD$");
|
|
|
|
|
2019-03-10 20:19:43 +00:00
|
|
|
#include "opt_acpi.h"
|
2002-01-30 12:41:12 +00:00
|
|
|
#include "opt_isa.h"
|
1996-01-04 21:13:23 +00:00
|
|
|
|
1994-08-13 03:50:34 +00:00
|
|
|
#include <sys/param.h>
|
|
|
|
#include <sys/systm.h>
|
2000-06-23 07:44:33 +00:00
|
|
|
#include <sys/bus.h>
|
2006-10-02 12:59:59 +00:00
|
|
|
#include <sys/clock.h>
|
2001-03-28 09:17:56 +00:00
|
|
|
#include <sys/lock.h>
|
2000-10-20 07:31:00 +00:00
|
|
|
#include <sys/mutex.h>
|
2013-02-21 15:35:48 +00:00
|
|
|
#include <sys/kdb.h>
|
1994-08-13 03:50:34 +00:00
|
|
|
#include <sys/kernel.h>
|
2004-05-30 17:57:46 +00:00
|
|
|
#include <sys/module.h>
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
#include <sys/proc.h>
|
|
|
|
#include <sys/rman.h>
|
|
|
|
#include <sys/timeet.h>
|
1996-05-01 08:39:02 +00:00
|
|
|
|
1999-05-31 18:36:14 +00:00
|
|
|
#include <isa/rtc.h>
|
2002-01-30 12:41:12 +00:00
|
|
|
#ifdef DEV_ISA
|
2005-05-14 09:10:02 +00:00
|
|
|
#include <isa/isareg.h>
|
2000-06-23 07:44:33 +00:00
|
|
|
#include <isa/isavar.h>
|
2002-01-30 12:41:12 +00:00
|
|
|
#endif
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
#include <machine/intr_machdep.h>
|
|
|
|
#include "clock_if.h"
|
2019-03-10 20:19:43 +00:00
|
|
|
#ifdef DEV_ACPI
|
2018-03-13 09:42:33 +00:00
|
|
|
#include <contrib/dev/acpica/include/acpi.h>
|
2019-03-10 20:19:43 +00:00
|
|
|
#include <contrib/dev/acpica/include/accommon.h>
|
|
|
|
#include <dev/acpica/acpivar.h>
|
2018-06-25 11:01:12 +00:00
|
|
|
#include <machine/md_var.h>
|
2019-03-10 20:19:43 +00:00
|
|
|
#endif
|
2018-03-13 09:42:33 +00:00
|
|
|
|
2017-07-12 02:42:57 +00:00
|
|
|
/*
|
2018-03-11 20:13:15 +00:00
|
|
|
* atrtc_lock protects low-level access to individual hardware registers.
|
|
|
|
* atrtc_time_lock protects the entire sequence of accessing multiple registers
|
|
|
|
* to read or write the date and time.
|
2017-07-12 02:42:57 +00:00
|
|
|
*/
|
2018-03-11 20:13:15 +00:00
|
|
|
static struct mtx atrtc_lock;
|
2018-03-11 19:56:07 +00:00
|
|
|
MTX_SYSINIT(atrtc_lock_init, &atrtc_lock, "atrtc", MTX_SPIN);
|
1994-11-05 23:55:07 +00:00
|
|
|
|
2018-03-13 09:42:33 +00:00
|
|
|
/* Force RTC enabled/disabled. */
|
|
|
|
static int atrtc_enabled = -1;
|
|
|
|
TUNABLE_INT("hw.atrtc.enabled", &atrtc_enabled);
|
|
|
|
|
2018-03-11 20:13:15 +00:00
|
|
|
struct mtx atrtc_time_lock;
|
2018-03-12 15:26:11 +00:00
|
|
|
MTX_SYSINIT(atrtc_time_lock_init, &atrtc_time_lock, "atrtc_time", MTX_DEF);
|
2018-03-11 20:13:15 +00:00
|
|
|
|
2010-06-21 19:53:47 +00:00
|
|
|
int atrtcclock_disable = 0;
|
|
|
|
|
2006-12-03 03:49:28 +00:00
|
|
|
static int rtc_reg = -1;
|
1994-11-05 23:55:07 +00:00
|
|
|
static u_char rtc_statusa = RTCSA_DIVIDER | RTCSA_NOPROF;
|
2005-03-24 21:34:16 +00:00
|
|
|
static u_char rtc_statusb = RTCSB_24HR;
|
1996-07-20 18:47:23 +00:00
|
|
|
|
2019-03-11 19:46:15 +00:00
|
|
|
#ifdef DEV_ACPI
|
|
|
|
#define _COMPONENT ACPI_TIMER
|
|
|
|
ACPI_MODULE_NAME("ATRTC")
|
|
|
|
#endif
|
|
|
|
|
1994-09-20 00:31:07 +00:00
|
|
|
/*
|
|
|
|
* RTC support routines
|
|
|
|
*/
|
|
|
|
|
2018-01-16 03:02:41 +00:00
|
|
|
static inline u_char
|
|
|
|
rtcin_locked(int reg)
|
1996-03-31 04:05:36 +00:00
|
|
|
{
|
|
|
|
|
2006-12-03 03:49:28 +00:00
|
|
|
if (rtc_reg != reg) {
|
|
|
|
inb(0x84);
|
|
|
|
outb(IO_RTC, reg);
|
|
|
|
rtc_reg = reg;
|
|
|
|
inb(0x84);
|
|
|
|
}
|
2018-01-16 03:02:41 +00:00
|
|
|
return (inb(IO_RTC + 1));
|
1996-03-31 04:05:36 +00:00
|
|
|
}
|
|
|
|
|
2018-01-16 03:02:41 +00:00
|
|
|
static inline void
|
|
|
|
rtcout_locked(int reg, u_char val)
|
1994-09-20 00:31:07 +00:00
|
|
|
{
|
1999-12-25 15:30:31 +00:00
|
|
|
|
2006-12-03 03:49:28 +00:00
|
|
|
if (rtc_reg != reg) {
|
|
|
|
inb(0x84);
|
|
|
|
outb(IO_RTC, reg);
|
|
|
|
rtc_reg = reg;
|
|
|
|
inb(0x84);
|
|
|
|
}
|
1994-12-30 12:43:35 +00:00
|
|
|
outb(IO_RTC + 1, val);
|
2006-12-03 03:49:28 +00:00
|
|
|
inb(0x84);
|
2018-01-16 03:02:41 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
rtcin(int reg)
|
|
|
|
{
|
|
|
|
u_char val;
|
|
|
|
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
2018-01-16 03:02:41 +00:00
|
|
|
val = rtcin_locked(reg);
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
2018-01-16 03:02:41 +00:00
|
|
|
return (val);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
writertc(int reg, u_char val)
|
|
|
|
{
|
|
|
|
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
2018-01-16 03:02:41 +00:00
|
|
|
rtcout_locked(reg, val);
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
1994-09-20 00:31:07 +00:00
|
|
|
}
|
|
|
|
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
static void
|
2008-04-14 07:57:15 +00:00
|
|
|
atrtc_start(void)
|
1993-11-25 01:38:01 +00:00
|
|
|
{
|
1996-05-01 08:39:02 +00:00
|
|
|
|
2018-03-11 18:54:45 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
|
|
|
rtcout_locked(RTC_STATUSA, rtc_statusa);
|
|
|
|
rtcout_locked(RTC_STATUSB, RTCSB_24HR);
|
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
1993-06-12 14:58:17 +00:00
|
|
|
}
|
|
|
|
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
static void
|
2008-04-14 07:57:15 +00:00
|
|
|
atrtc_rate(unsigned rate)
|
1993-06-12 14:58:17 +00:00
|
|
|
{
|
|
|
|
|
2008-04-14 07:57:15 +00:00
|
|
|
rtc_statusa = RTCSA_DIVIDER | rate;
|
1994-12-30 12:43:35 +00:00
|
|
|
writertc(RTC_STATUSA, rtc_statusa);
|
1998-03-14 03:11:50 +00:00
|
|
|
}
|
|
|
|
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
static void
|
2008-04-14 07:57:15 +00:00
|
|
|
atrtc_enable_intr(void)
|
1994-05-25 09:21:21 +00:00
|
|
|
{
|
2003-02-03 17:53:15 +00:00
|
|
|
|
2008-04-14 07:57:15 +00:00
|
|
|
rtc_statusb |= RTCSB_PINTR;
|
2018-03-11 18:54:45 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
|
|
|
rtcout_locked(RTC_STATUSB, rtc_statusb);
|
|
|
|
rtcin_locked(RTC_INTR);
|
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
2003-02-03 17:53:15 +00:00
|
|
|
}
|
|
|
|
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
static void
|
|
|
|
atrtc_disable_intr(void)
|
|
|
|
{
|
|
|
|
|
|
|
|
rtc_statusb &= ~RTCSB_PINTR;
|
2018-03-11 18:54:45 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
|
|
|
rtcout_locked(RTC_STATUSB, rtc_statusb);
|
|
|
|
rtcin_locked(RTC_INTR);
|
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
}
|
|
|
|
|
2003-02-03 17:53:15 +00:00
|
|
|
void
|
2008-04-14 07:57:15 +00:00
|
|
|
atrtc_restore(void)
|
2003-02-03 17:53:15 +00:00
|
|
|
{
|
|
|
|
|
2008-04-14 07:57:15 +00:00
|
|
|
/* Restore all of the RTC's "status" (actually, control) registers. */
|
2018-03-11 18:54:45 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
|
|
|
rtcin_locked(RTC_STATUSA); /* dummy to get rtc_reg set */
|
|
|
|
rtcout_locked(RTC_STATUSB, RTCSB_24HR);
|
|
|
|
rtcout_locked(RTC_STATUSA, rtc_statusa);
|
|
|
|
rtcout_locked(RTC_STATUSB, rtc_statusb);
|
|
|
|
rtcin_locked(RTC_INTR);
|
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
2000-06-23 07:44:33 +00:00
|
|
|
}
|
|
|
|
|
2008-04-12 20:46:06 +00:00
|
|
|
/**********************************************************************
|
|
|
|
* RTC driver for subr_rtc
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct atrtc_softc {
|
|
|
|
int port_rid, intr_rid;
|
|
|
|
struct resource *port_res;
|
|
|
|
struct resource *intr_res;
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
void *intr_handler;
|
|
|
|
struct eventtimer et;
|
2019-03-10 20:19:43 +00:00
|
|
|
#ifdef DEV_ACPI
|
|
|
|
ACPI_HANDLE acpi_handle;
|
|
|
|
#endif
|
2008-04-12 20:46:06 +00:00
|
|
|
};
|
|
|
|
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
static int
|
2013-02-28 13:46:03 +00:00
|
|
|
rtc_start(struct eventtimer *et, sbintime_t first, sbintime_t period)
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
{
|
|
|
|
|
2013-02-28 13:46:03 +00:00
|
|
|
atrtc_rate(max(fls(period + (period >> 1)) - 17, 1));
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
atrtc_enable_intr();
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
rtc_stop(struct eventtimer *et)
|
|
|
|
{
|
|
|
|
|
|
|
|
atrtc_disable_intr();
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This routine receives statistical clock interrupts from the RTC.
|
|
|
|
* As explained above, these occur at 128 interrupts per second.
|
|
|
|
* When profiling, we receive interrupts at a rate of 1024 Hz.
|
|
|
|
*
|
|
|
|
* This does not actually add as much overhead as it sounds, because
|
|
|
|
* when the statistical clock is active, the hardclock driver no longer
|
|
|
|
* needs to keep (inaccurate) statistics on its own. This decouples
|
|
|
|
* statistics gathering from scheduling interrupts.
|
|
|
|
*
|
|
|
|
* The RTC chip requires that we read status register C (RTC_INTR)
|
|
|
|
* to acknowledge an interrupt, before it will generate the next one.
|
|
|
|
* Under high interrupt load, rtcintr() can be indefinitely delayed and
|
|
|
|
* the clock can tick immediately after the read from RTC_INTR. In this
|
|
|
|
* case, the mc146818A interrupt signal will not drop for long enough
|
|
|
|
* to register with the 8259 PIC. If an interrupt is missed, the stat
|
|
|
|
* clock will halt, considerably degrading system performance. This is
|
|
|
|
* why we use 'while' rather than a more straightforward 'if' below.
|
|
|
|
* Stat clock ticks can still be lost, causing minor loss of accuracy
|
|
|
|
* in the statistics, but the stat clock will no longer stop.
|
|
|
|
*/
|
|
|
|
static int
|
|
|
|
rtc_intr(void *arg)
|
|
|
|
{
|
|
|
|
struct atrtc_softc *sc = (struct atrtc_softc *)arg;
|
|
|
|
int flag = 0;
|
|
|
|
|
|
|
|
while (rtcin(RTC_INTR) & RTCIR_PERIOD) {
|
|
|
|
flag = 1;
|
2010-07-13 12:46:06 +00:00
|
|
|
if (sc->et.et_active)
|
|
|
|
sc->et.et_event_cb(&sc->et, sc->et.et_arg);
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
}
|
|
|
|
return(flag ? FILTER_HANDLED : FILTER_STRAY);
|
|
|
|
}
|
|
|
|
|
2019-03-10 20:19:43 +00:00
|
|
|
#ifdef DEV_ACPI
|
|
|
|
/*
|
|
|
|
* ACPI RTC CMOS address space handler
|
|
|
|
*/
|
|
|
|
#define ATRTC_LAST_REG 0x40
|
|
|
|
|
|
|
|
static void
|
|
|
|
rtcin_region(int reg, void *buf, int len)
|
|
|
|
{
|
|
|
|
u_char *ptr = buf;
|
|
|
|
|
|
|
|
/* Drop lock after each IO as intr and settime have greater priority */
|
|
|
|
while (len-- > 0)
|
|
|
|
*ptr++ = rtcin(reg++) & 0xff;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
rtcout_region(int reg, const void *buf, int len)
|
|
|
|
{
|
|
|
|
const u_char *ptr = buf;
|
|
|
|
|
|
|
|
while (len-- > 0)
|
|
|
|
writertc(reg++, *ptr++);
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool
|
|
|
|
atrtc_check_cmos_access(bool is_read, ACPI_PHYSICAL_ADDRESS addr, UINT32 len)
|
|
|
|
{
|
|
|
|
|
|
|
|
/* Block address space wrapping on out-of-bound access */
|
|
|
|
if (addr >= ATRTC_LAST_REG || addr + len > ATRTC_LAST_REG)
|
|
|
|
return (false);
|
|
|
|
|
|
|
|
if (is_read) {
|
|
|
|
/* Reading 0x0C will muck with interrupts */
|
|
|
|
if (addr <= RTC_INTR && addr + len > RTC_INTR)
|
|
|
|
return (false);
|
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* Allow single-byte writes to alarm registers and
|
|
|
|
* multi-byte writes to addr >= 0x30, else deny.
|
|
|
|
*/
|
|
|
|
if (!((len == 1 && (addr == RTC_SECALRM ||
|
|
|
|
addr == RTC_MINALRM ||
|
|
|
|
addr == RTC_HRSALRM)) ||
|
|
|
|
addr >= 0x30))
|
|
|
|
return (false);
|
|
|
|
}
|
|
|
|
return (true);
|
|
|
|
}
|
|
|
|
|
|
|
|
static ACPI_STATUS
|
|
|
|
atrtc_acpi_cmos_handler(UINT32 func, ACPI_PHYSICAL_ADDRESS addr,
|
|
|
|
UINT32 bitwidth, UINT64 *value, void *context, void *region_context)
|
|
|
|
{
|
|
|
|
device_t dev = context;
|
|
|
|
UINT32 bytewidth = howmany(bitwidth, 8);
|
|
|
|
bool is_read = func == ACPI_READ;
|
|
|
|
|
|
|
|
/* ACPICA is very verbose on CMOS handler failures, so we, too */
|
|
|
|
#define CMOS_HANDLER_ERR(fmt, ...) \
|
|
|
|
device_printf(dev, "ACPI [SystemCMOS] handler: " fmt, ##__VA_ARGS__)
|
|
|
|
|
|
|
|
ACPI_FUNCTION_TRACE((char *)(uintptr_t)__func__);
|
|
|
|
|
|
|
|
if (value == NULL) {
|
|
|
|
CMOS_HANDLER_ERR("NULL parameter\n");
|
|
|
|
return (AE_BAD_PARAMETER);
|
|
|
|
}
|
|
|
|
if (bitwidth == 0 || (bitwidth & 0x07) != 0) {
|
|
|
|
CMOS_HANDLER_ERR("Invalid bitwidth: %u\n", bitwidth);
|
|
|
|
return (AE_BAD_PARAMETER);
|
|
|
|
}
|
|
|
|
if (!atrtc_check_cmos_access(is_read, addr, bytewidth)) {
|
|
|
|
CMOS_HANDLER_ERR("%s access rejected: addr=%#04jx, len=%u\n",
|
|
|
|
is_read ? "Read" : "Write", (uintmax_t)addr, bytewidth);
|
|
|
|
return (AE_BAD_PARAMETER);
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (func) {
|
|
|
|
case ACPI_READ:
|
|
|
|
rtcin_region(addr, value, bytewidth);
|
|
|
|
break;
|
|
|
|
case ACPI_WRITE:
|
|
|
|
rtcout_region(addr, value, bytewidth);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
CMOS_HANDLER_ERR("Invalid function: %u\n", func);
|
|
|
|
return (AE_BAD_PARAMETER);
|
|
|
|
}
|
|
|
|
|
|
|
|
ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev),
|
|
|
|
"ACPI RTC CMOS %s access: addr=%#04x, len=%u, val=%*D\n",
|
|
|
|
is_read ? "read" : "write", (unsigned)addr, bytewidth,
|
|
|
|
bytewidth, value, " ");
|
|
|
|
|
|
|
|
return (AE_OK);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
atrtc_reg_acpi_cmos_handler(device_t dev)
|
|
|
|
{
|
|
|
|
struct atrtc_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
|
|
|
|
|
|
|
|
/* Don't handle address space events if driver is disabled. */
|
|
|
|
if (acpi_disabled("atrtc"))
|
|
|
|
return (ENXIO);
|
|
|
|
|
|
|
|
sc->acpi_handle = acpi_get_handle(dev);
|
|
|
|
if (sc->acpi_handle == NULL ||
|
|
|
|
ACPI_FAILURE(AcpiInstallAddressSpaceHandler(sc->acpi_handle,
|
|
|
|
ACPI_ADR_SPACE_CMOS, atrtc_acpi_cmos_handler, NULL, dev))) {
|
|
|
|
sc->acpi_handle = NULL;
|
|
|
|
device_printf(dev,
|
|
|
|
"Can't register ACPI CMOS address space handler\n");
|
|
|
|
return (ENXIO);
|
|
|
|
}
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
atrtc_unreg_acpi_cmos_handler(device_t dev)
|
|
|
|
{
|
|
|
|
struct atrtc_softc *sc = device_get_softc(dev);
|
|
|
|
|
|
|
|
ACPI_FUNCTION_TRACE((char *)(uintptr_t) __func__);
|
|
|
|
|
|
|
|
if (sc->acpi_handle != NULL)
|
|
|
|
AcpiRemoveAddressSpaceHandler(sc->acpi_handle,
|
|
|
|
ACPI_ADR_SPACE_CMOS, atrtc_acpi_cmos_handler);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
#endif /* DEV_ACPI */
|
|
|
|
|
2008-04-12 20:46:06 +00:00
|
|
|
/*
|
|
|
|
* Attach to the ISA PnP descriptors for the timer and realtime clock.
|
|
|
|
*/
|
|
|
|
static struct isa_pnp_id atrtc_ids[] = {
|
|
|
|
{ 0x000bd041 /* PNP0B00 */, "AT realtime clock" },
|
|
|
|
{ 0 }
|
|
|
|
};
|
|
|
|
|
2018-03-13 09:42:33 +00:00
|
|
|
static bool
|
|
|
|
atrtc_acpi_disabled(void)
|
|
|
|
{
|
2019-03-10 20:19:43 +00:00
|
|
|
#ifdef DEV_ACPI
|
2018-03-13 09:42:33 +00:00
|
|
|
uint16_t flags;
|
|
|
|
|
2018-06-25 11:01:12 +00:00
|
|
|
if (!acpi_get_fadt_bootflags(&flags))
|
2018-03-13 09:42:33 +00:00
|
|
|
return (false);
|
2018-06-25 11:01:12 +00:00
|
|
|
return ((flags & ACPI_FADT_NO_CMOS_RTC) != 0);
|
2019-03-10 20:19:43 +00:00
|
|
|
#else
|
|
|
|
return (false);
|
|
|
|
#endif
|
2018-03-13 09:42:33 +00:00
|
|
|
}
|
|
|
|
|
2008-04-12 20:46:06 +00:00
|
|
|
static int
|
|
|
|
atrtc_probe(device_t dev)
|
|
|
|
{
|
|
|
|
int result;
|
2018-03-13 09:42:33 +00:00
|
|
|
|
|
|
|
if ((atrtc_enabled == -1 && atrtc_acpi_disabled()) ||
|
|
|
|
(atrtc_enabled == 0))
|
|
|
|
return (ENXIO);
|
|
|
|
|
2008-04-12 20:46:06 +00:00
|
|
|
result = ISA_PNP_PROBE(device_get_parent(dev), dev, atrtc_ids);
|
2010-07-01 18:59:05 +00:00
|
|
|
/* ENOENT means no PnP-ID, device is hinted. */
|
|
|
|
if (result == ENOENT) {
|
|
|
|
device_set_desc(dev, "AT realtime clock");
|
|
|
|
return (BUS_PROBE_LOW_PRIORITY);
|
|
|
|
}
|
|
|
|
return (result);
|
2008-04-12 20:46:06 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
atrtc_attach(device_t dev)
|
|
|
|
{
|
|
|
|
struct atrtc_softc *sc;
|
2016-01-27 02:23:54 +00:00
|
|
|
rman_res_t s;
|
2010-10-16 10:45:36 +00:00
|
|
|
int i;
|
2008-04-12 20:46:06 +00:00
|
|
|
|
|
|
|
sc = device_get_softc(dev);
|
2010-12-16 17:05:28 +00:00
|
|
|
sc->port_res = bus_alloc_resource(dev, SYS_RES_IOPORT, &sc->port_rid,
|
|
|
|
IO_RTC, IO_RTC + 1, 2, RF_ACTIVE);
|
|
|
|
if (sc->port_res == NULL)
|
|
|
|
device_printf(dev, "Warning: Couldn't map I/O.\n");
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
atrtc_start();
|
2008-04-12 20:46:06 +00:00
|
|
|
clock_register(dev, 1000000);
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
bzero(&sc->et, sizeof(struct eventtimer));
|
2010-06-22 19:42:27 +00:00
|
|
|
if (!atrtcclock_disable &&
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
(resource_int_value(device_get_name(dev), device_get_unit(dev),
|
|
|
|
"clock", &i) != 0 || i != 0)) {
|
2010-07-01 18:51:18 +00:00
|
|
|
sc->intr_rid = 0;
|
2010-07-12 06:46:17 +00:00
|
|
|
while (bus_get_resource(dev, SYS_RES_IRQ, sc->intr_rid,
|
|
|
|
&s, NULL) == 0 && s != 8)
|
|
|
|
sc->intr_rid++;
|
2010-12-16 17:05:28 +00:00
|
|
|
sc->intr_res = bus_alloc_resource(dev, SYS_RES_IRQ,
|
|
|
|
&sc->intr_rid, 8, 8, 1, RF_ACTIVE);
|
|
|
|
if (sc->intr_res == NULL) {
|
|
|
|
device_printf(dev, "Can't map interrupt.\n");
|
2010-06-22 19:42:27 +00:00
|
|
|
return (0);
|
2010-12-16 17:05:28 +00:00
|
|
|
} else if ((bus_setup_intr(dev, sc->intr_res, INTR_TYPE_CLK,
|
|
|
|
rtc_intr, NULL, sc, &sc->intr_handler))) {
|
2010-06-22 19:42:27 +00:00
|
|
|
device_printf(dev, "Can't setup interrupt.\n");
|
|
|
|
return (0);
|
|
|
|
} else {
|
|
|
|
/* Bind IRQ to BSP to avoid live migration. */
|
|
|
|
bus_bind_intr(dev, sc->intr_res, 0);
|
|
|
|
}
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
sc->et.et_name = "RTC";
|
2010-07-20 10:58:56 +00:00
|
|
|
sc->et.et_flags = ET_FLAGS_PERIODIC | ET_FLAGS_POW2DIV;
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
sc->et.et_quality = 0;
|
|
|
|
sc->et.et_frequency = 32768;
|
2013-02-28 13:46:03 +00:00
|
|
|
sc->et.et_min_period = 0x00080000;
|
|
|
|
sc->et.et_max_period = 0x80000000;
|
Implement new event timers infrastructure. It provides unified APIs for
writing event timer drivers, for choosing best possible drivers by machine
independent code and for operating them to supply kernel with hardclock(),
statclock() and profclock() events in unified fashion on various hardware.
Infrastructure provides support for both per-CPU (independent for every CPU
core) and global timers in periodic and one-shot modes. MI management code
at this moment uses only periodic mode, but one-shot mode use planned for
later, as part of tickless kernel project.
For this moment infrastructure used on i386 and amd64 architectures. Other
archs are welcome to follow, while their current operation should not be
affected.
This patch updates existing drivers (i8254, RTC and LAPIC) for the new
order, and adds event timers support into the HPET driver. These drivers
have different capabilities:
LAPIC - per-CPU timer, supports periodic and one-shot operation, may
freeze in C3 state, calibrated on first use, so may be not exactly precise.
HPET - depending on hardware can work as per-CPU or global, supports
periodic and one-shot operation, usually provides several event timers.
i8254 - global, limited to periodic mode, because same hardware used also
as time counter.
RTC - global, supports only periodic mode, set of frequencies in Hz
limited by powers of 2.
Depending on hardware capabilities, drivers preferred in following orders,
either LAPIC, HPETs, i8254, RTC or HPETs, LAPIC, i8254, RTC.
User may explicitly specify wanted timers via loader tunables or sysctls:
kern.eventtimer.timer1 and kern.eventtimer.timer2.
If requested driver is unavailable or unoperational, system will try to
replace it. If no more timers available or "NONE" specified for second,
system will operate using only one timer, multiplying it's frequency by few
times and uing respective dividers to honor hz, stathz and profhz values,
set during initial setup.
2010-06-20 21:33:29 +00:00
|
|
|
sc->et.et_start = rtc_start;
|
|
|
|
sc->et.et_stop = rtc_stop;
|
|
|
|
sc->et.et_priv = dev;
|
|
|
|
et_register(&sc->et);
|
|
|
|
}
|
2008-04-12 20:46:06 +00:00
|
|
|
return(0);
|
|
|
|
}
|
|
|
|
|
2019-03-10 20:19:43 +00:00
|
|
|
static int
|
|
|
|
atrtc_isa_attach(device_t dev)
|
|
|
|
{
|
|
|
|
|
|
|
|
return (atrtc_attach(dev));
|
|
|
|
}
|
|
|
|
|
|
|
|
#ifdef DEV_ACPI
|
|
|
|
static int
|
|
|
|
atrtc_acpi_attach(device_t dev)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
ret = atrtc_attach(dev);
|
|
|
|
if (ret)
|
|
|
|
return (ret);
|
|
|
|
|
|
|
|
(void)atrtc_reg_acpi_cmos_handler(dev);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
atrtc_acpi_detach(device_t dev)
|
|
|
|
{
|
|
|
|
|
|
|
|
(void)atrtc_unreg_acpi_cmos_handler(dev);
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
#endif /* DEV_ACPI */
|
|
|
|
|
2009-05-01 21:43:04 +00:00
|
|
|
static int
|
|
|
|
atrtc_resume(device_t dev)
|
|
|
|
{
|
|
|
|
|
|
|
|
atrtc_restore();
|
|
|
|
return(0);
|
|
|
|
}
|
2008-04-12 20:46:06 +00:00
|
|
|
|
|
|
|
static int
|
|
|
|
atrtc_settime(device_t dev __unused, struct timespec *ts)
|
|
|
|
{
|
2018-01-16 23:14:12 +00:00
|
|
|
struct bcd_clocktime bct;
|
|
|
|
|
|
|
|
clock_ts_to_bcd(ts, &bct, false);
|
2018-03-11 16:57:14 +00:00
|
|
|
clock_dbgprint_bcd(dev, CLOCK_DBG_WRITE, &bct);
|
2018-01-16 23:14:12 +00:00
|
|
|
|
2018-03-11 20:13:15 +00:00
|
|
|
mtx_lock(&atrtc_time_lock);
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
2018-01-16 23:14:12 +00:00
|
|
|
|
|
|
|
/* Disable RTC updates and interrupts. */
|
|
|
|
rtcout_locked(RTC_STATUSB, RTCSB_HALT | RTCSB_24HR);
|
|
|
|
|
|
|
|
/* Write all the time registers. */
|
|
|
|
rtcout_locked(RTC_SEC, bct.sec);
|
|
|
|
rtcout_locked(RTC_MIN, bct.min);
|
|
|
|
rtcout_locked(RTC_HRS, bct.hour);
|
|
|
|
rtcout_locked(RTC_WDAY, bct.dow + 1);
|
|
|
|
rtcout_locked(RTC_DAY, bct.day);
|
|
|
|
rtcout_locked(RTC_MONTH, bct.mon);
|
|
|
|
rtcout_locked(RTC_YEAR, bct.year & 0xff);
|
|
|
|
#ifdef USE_RTC_CENTURY
|
|
|
|
rtcout_locked(RTC_CENTURY, bct.year >> 8);
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Re-enable RTC updates and interrupts.
|
|
|
|
*/
|
|
|
|
rtcout_locked(RTC_STATUSB, rtc_statusb);
|
|
|
|
rtcin_locked(RTC_INTR);
|
|
|
|
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
2018-03-11 20:13:15 +00:00
|
|
|
mtx_unlock(&atrtc_time_lock);
|
2008-04-12 20:46:06 +00:00
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
atrtc_gettime(device_t dev, struct timespec *ts)
|
|
|
|
{
|
2018-01-16 23:14:12 +00:00
|
|
|
struct bcd_clocktime bct;
|
2008-04-12 20:46:06 +00:00
|
|
|
|
|
|
|
/* Look if we have a RTC present and the time is valid */
|
|
|
|
if (!(rtcin(RTC_STATUSD) & RTCSD_PWR)) {
|
|
|
|
device_printf(dev, "WARNING: Battery failure indication\n");
|
|
|
|
return (EINVAL);
|
|
|
|
}
|
|
|
|
|
2013-02-21 15:35:48 +00:00
|
|
|
/*
|
|
|
|
* wait for time update to complete
|
|
|
|
* If RTCSA_TUP is zero, we have at least 244us before next update.
|
|
|
|
* This is fast enough on most hardware, but a refinement would be
|
|
|
|
* to make sure that no more than 240us pass after we start reading,
|
|
|
|
* and try again if so.
|
|
|
|
*/
|
2018-03-11 20:13:15 +00:00
|
|
|
mtx_lock(&atrtc_time_lock);
|
2013-02-21 00:40:08 +00:00
|
|
|
while (rtcin(RTC_STATUSA) & RTCSA_TUP)
|
|
|
|
continue;
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_lock_spin(&atrtc_lock);
|
2018-01-16 23:14:12 +00:00
|
|
|
bct.sec = rtcin_locked(RTC_SEC);
|
|
|
|
bct.min = rtcin_locked(RTC_MIN);
|
|
|
|
bct.hour = rtcin_locked(RTC_HRS);
|
|
|
|
bct.day = rtcin_locked(RTC_DAY);
|
|
|
|
bct.mon = rtcin_locked(RTC_MONTH);
|
|
|
|
bct.year = rtcin_locked(RTC_YEAR);
|
2008-04-12 20:46:06 +00:00
|
|
|
#ifdef USE_RTC_CENTURY
|
2018-01-16 23:14:12 +00:00
|
|
|
bct.year |= rtcin_locked(RTC_CENTURY) << 8;
|
2008-04-12 20:46:06 +00:00
|
|
|
#endif
|
2018-03-11 18:20:49 +00:00
|
|
|
mtx_unlock_spin(&atrtc_lock);
|
2018-03-11 20:13:15 +00:00
|
|
|
mtx_unlock(&atrtc_time_lock);
|
2018-01-15 16:40:43 +00:00
|
|
|
/* dow is unused in timespec conversion and we have no nsec info. */
|
2018-01-16 23:14:12 +00:00
|
|
|
bct.dow = 0;
|
|
|
|
bct.nsec = 0;
|
2018-03-11 16:57:14 +00:00
|
|
|
clock_dbgprint_bcd(dev, CLOCK_DBG_READ, &bct);
|
2018-01-16 23:14:12 +00:00
|
|
|
return (clock_bcd_to_ts(&bct, ts, false));
|
2008-04-12 20:46:06 +00:00
|
|
|
}
|
|
|
|
|
2019-03-10 20:19:43 +00:00
|
|
|
static device_method_t atrtc_isa_methods[] = {
|
2008-04-12 20:46:06 +00:00
|
|
|
/* Device interface */
|
|
|
|
DEVMETHOD(device_probe, atrtc_probe),
|
2019-03-10 20:19:43 +00:00
|
|
|
DEVMETHOD(device_attach, atrtc_isa_attach),
|
2008-04-12 20:46:06 +00:00
|
|
|
DEVMETHOD(device_detach, bus_generic_detach),
|
|
|
|
DEVMETHOD(device_shutdown, bus_generic_shutdown),
|
|
|
|
DEVMETHOD(device_suspend, bus_generic_suspend),
|
|
|
|
/* XXX stop statclock? */
|
2009-05-01 21:43:04 +00:00
|
|
|
DEVMETHOD(device_resume, atrtc_resume),
|
2008-04-12 20:46:06 +00:00
|
|
|
|
|
|
|
/* clock interface */
|
|
|
|
DEVMETHOD(clock_gettime, atrtc_gettime),
|
|
|
|
DEVMETHOD(clock_settime, atrtc_settime),
|
|
|
|
|
|
|
|
{ 0, 0 }
|
|
|
|
};
|
|
|
|
|
2019-03-10 20:19:43 +00:00
|
|
|
static driver_t atrtc_isa_driver = {
|
|
|
|
"atrtc",
|
|
|
|
atrtc_isa_methods,
|
|
|
|
sizeof(struct atrtc_softc),
|
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef DEV_ACPI
|
|
|
|
static device_method_t atrtc_acpi_methods[] = {
|
|
|
|
/* Device interface */
|
|
|
|
DEVMETHOD(device_probe, atrtc_probe),
|
|
|
|
DEVMETHOD(device_attach, atrtc_acpi_attach),
|
|
|
|
DEVMETHOD(device_detach, atrtc_acpi_detach),
|
|
|
|
/* XXX stop statclock? */
|
|
|
|
DEVMETHOD(device_resume, atrtc_resume),
|
|
|
|
|
|
|
|
/* clock interface */
|
|
|
|
DEVMETHOD(clock_gettime, atrtc_gettime),
|
|
|
|
DEVMETHOD(clock_settime, atrtc_settime),
|
|
|
|
|
|
|
|
{ 0, 0 }
|
|
|
|
};
|
|
|
|
|
|
|
|
static driver_t atrtc_acpi_driver = {
|
2008-04-12 20:46:06 +00:00
|
|
|
"atrtc",
|
2019-03-10 20:19:43 +00:00
|
|
|
atrtc_acpi_methods,
|
2008-04-12 20:46:06 +00:00
|
|
|
sizeof(struct atrtc_softc),
|
|
|
|
};
|
2019-03-10 20:19:43 +00:00
|
|
|
#endif /* DEV_ACPI */
|
2008-04-12 20:46:06 +00:00
|
|
|
|
|
|
|
static devclass_t atrtc_devclass;
|
|
|
|
|
2019-03-10 20:19:43 +00:00
|
|
|
DRIVER_MODULE(atrtc, isa, atrtc_isa_driver, atrtc_devclass, 0, 0);
|
|
|
|
#ifdef DEV_ACPI
|
|
|
|
DRIVER_MODULE(atrtc, acpi, atrtc_acpi_driver, atrtc_devclass, 0, 0);
|
|
|
|
#endif
|
2018-01-29 00:22:30 +00:00
|
|
|
ISA_PNP_INFO(atrtc_ids);
|