2005-04-17 05:20:36 +07:00
|
|
|
/*
|
|
|
|
* acpi_osl.c - OS-dependent functions ($Revision: 83 $)
|
|
|
|
*
|
|
|
|
* Copyright (C) 2000 Andrew Henroid
|
|
|
|
* Copyright (C) 2001, 2002 Andy Grover <andrew.grover@intel.com>
|
|
|
|
* Copyright (C) 2001, 2002 Paul Diefenbaugh <paul.s.diefenbaugh@intel.com>
|
2008-03-15 00:43:13 +07:00
|
|
|
* Copyright (c) 2008 Intel Corporation
|
|
|
|
* Author: Matthew Wilcox <willy@linux.intel.com>
|
2005-04-17 05:20:36 +07:00
|
|
|
*
|
|
|
|
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program; if not, write to the Free Software
|
|
|
|
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
|
|
|
|
*
|
|
|
|
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/mm.h>
|
2012-01-21 09:13:30 +07:00
|
|
|
#include <linux/highmem.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
#include <linux/pci.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/kmod.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/workqueue.h>
|
|
|
|
#include <linux/nmi.h>
|
2007-02-02 23:48:19 +07:00
|
|
|
#include <linux/acpi.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
#include <linux/efi.h>
|
2008-02-05 14:31:22 +07:00
|
|
|
#include <linux/ioport.h>
|
|
|
|
#include <linux/list.h>
|
2008-03-15 00:43:13 +07:00
|
|
|
#include <linux/jiffies.h>
|
|
|
|
#include <linux/semaphore.h>
|
|
|
|
|
|
|
|
#include <asm/io.h>
|
|
|
|
#include <asm/uaccess.h>
|
|
|
|
|
2013-07-23 15:11:55 +07:00
|
|
|
#include "internal.h"
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
#define _COMPONENT ACPI_OS_SERVICES
|
2007-02-13 10:42:12 +07:00
|
|
|
ACPI_MODULE_NAME("osl");
|
2014-03-13 11:47:39 +07:00
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
struct acpi_os_dpc {
|
|
|
|
acpi_osd_exec_callback function;
|
|
|
|
void *context;
|
2006-11-22 21:55:48 +07:00
|
|
|
struct work_struct work;
|
2005-04-17 05:20:36 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef CONFIG_ACPI_CUSTOM_DSDT
|
|
|
|
#include CONFIG_ACPI_CUSTOM_DSDT_FILE
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#ifdef ENABLE_DEBUGGER
|
|
|
|
#include <linux/kdb.h>
|
|
|
|
|
|
|
|
/* stuff for debugger support */
|
|
|
|
int acpi_in_debugger;
|
|
|
|
EXPORT_SYMBOL(acpi_in_debugger);
|
|
|
|
|
|
|
|
extern char line_buf[80];
|
2005-08-05 11:44:28 +07:00
|
|
|
#endif /*ENABLE_DEBUGGER */
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2011-12-09 09:05:54 +07:00
|
|
|
static int (*__acpi_os_prepare_sleep)(u8 sleep_state, u32 pm1a_ctrl,
|
|
|
|
u32 pm1b_ctrl);
|
2013-07-30 19:24:52 +07:00
|
|
|
static int (*__acpi_os_prepare_extended_sleep)(u8 sleep_state, u32 val_a,
|
|
|
|
u32 val_b);
|
2011-12-09 09:05:54 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
static acpi_osd_handler acpi_irq_handler;
|
|
|
|
static void *acpi_irq_context;
|
|
|
|
static struct workqueue_struct *kacpid_wq;
|
ACPI: created a dedicated workqueue for notify() execution
HP nx6125/nx6325/... machines have a _GPE handler with an infinite
loop sending Notify() events to different ACPI subsystems.
Notify handler in ACPI driver is a C-routine, which may call ACPI
interpreter again to get access to some ACPI variables
(acpi_evaluate_xxx).
On these HP machines such an evaluation changes state of some variable
and lets the loop above break.
In the current ACPI implementation Notify requests are being deferred
to the same kacpid workqueue on which the above GPE handler with
infinite loop is executing. Thus we have a deadlock -- loop will
continue to spin, sending notify events, and at the same time
preventing these notify events from being run on a workqueue. All
notify events are deferred, thus we see increase in memory consumption
noticed by author of the thread. Also as GPE handling is bloked,
machines overheat. Eventually by external poll of the same
acpi_evaluate, kacpid is released and all the queued notify events are
free to run, thus 100% cpu utilization by kacpid for several seconds
or more.
To prevent all these horrors it's needed to not put notify events to
kacpid workqueue by either executing them immediately or putting them
on some other thread. It's dangerous to execute notify events in
place, as it will put several ACPI interpreter stacks on top of each
other (at least 4 in case of nx6125), thus causing kernel stack
overflow.
First attempt to create a new thread was done by Peter Wainwright
He created a bunch of threads, which were stealing work from a kacpid
workqueue.
This patch appeared in 2.6.15 kernel shipped with Ubuntu 6.06 LTS.
Second attempt was done by me, I created a new thread for each Notify
event. This worked OK on HP nx machines, but broke Linus' Compaq
n620c, by producing threads with a speed what they stopped the machine
completely. Thus this patch was reverted from 18-rc2 as I remember.
I re-made the patch to create second workqueue just for notify events,
thus hopping it will not break Linus' machine. Patch was tested on the
same HP nx machines in #5534 and #7122, but I did not received reply
from Linus on a test patch sent to him.
Patch went to 19-rc and was rejected with much fanfare again.
There was 4th patch, which inserted schedule_timeout(1) into deferred
execution of kacpid, if we had any notify requests pending, but Linus
decided that it was too complex (involved either changes to workqueue
to see if it's empty or atomic inc/dec).
Now you see last variant which adds yield() to every GPE execution.
http://bugzilla.kernel.org/show_bug.cgi?id=5534
http://bugzilla.kernel.org/show_bug.cgi?id=8385
Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2007-05-10 10:31:03 +07:00
|
|
|
static struct workqueue_struct *kacpi_notify_wq;
|
2013-01-22 04:20:47 +07:00
|
|
|
static struct workqueue_struct *kacpi_hotplug_wq;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2010-10-22 03:23:53 +07:00
|
|
|
/*
|
|
|
|
* This list of permanent mappings is for memory that may be accessed from
|
|
|
|
* interrupt context, where we can't do the ioremap().
|
|
|
|
*/
|
|
|
|
struct acpi_ioremap {
|
|
|
|
struct list_head list;
|
|
|
|
void __iomem *virt;
|
|
|
|
acpi_physical_address phys;
|
|
|
|
acpi_size size;
|
2011-02-09 05:38:15 +07:00
|
|
|
unsigned long refcount;
|
2010-10-22 03:23:53 +07:00
|
|
|
};
|
|
|
|
|
|
|
|
static LIST_HEAD(acpi_ioremaps);
|
2011-02-09 05:37:42 +07:00
|
|
|
static DEFINE_MUTEX(acpi_ioremap_lock);
|
2010-10-22 03:23:53 +07:00
|
|
|
|
2010-08-06 08:35:51 +07:00
|
|
|
static void __init acpi_osi_setup_late(void);
|
2007-05-30 05:43:33 +07:00
|
|
|
|
2008-01-24 08:50:56 +07:00
|
|
|
/*
|
2008-11-08 13:21:10 +07:00
|
|
|
* The story of _OSI(Linux)
|
2008-01-24 08:50:56 +07:00
|
|
|
*
|
2008-11-08 13:21:10 +07:00
|
|
|
* From pre-history through Linux-2.6.22,
|
|
|
|
* Linux responded TRUE upon a BIOS OSI(Linux) query.
|
2008-01-24 08:50:56 +07:00
|
|
|
*
|
2008-11-08 13:21:10 +07:00
|
|
|
* Unfortunately, reference BIOS writers got wind of this
|
|
|
|
* and put OSI(Linux) in their example code, quickly exposing
|
|
|
|
* this string as ill-conceived and opening the door to
|
|
|
|
* an un-bounded number of BIOS incompatibilities.
|
2008-01-24 08:50:56 +07:00
|
|
|
*
|
2008-11-08 13:21:10 +07:00
|
|
|
* For example, OSI(Linux) was used on resume to re-POST a
|
|
|
|
* video card on one system, because Linux at that time
|
|
|
|
* could not do a speedy restore in its native driver.
|
|
|
|
* But then upon gaining quick native restore capability,
|
|
|
|
* Linux has no way to tell the BIOS to skip the time-consuming
|
|
|
|
* POST -- putting Linux at a permanent performance disadvantage.
|
|
|
|
* On another system, the BIOS writer used OSI(Linux)
|
|
|
|
* to infer native OS support for IPMI! On other systems,
|
|
|
|
* OSI(Linux) simply got in the way of Linux claiming to
|
|
|
|
* be compatible with other operating systems, exposing
|
|
|
|
* BIOS issues such as skipped device initialization.
|
2008-01-24 08:50:56 +07:00
|
|
|
*
|
2008-11-08 13:21:10 +07:00
|
|
|
* So "Linux" turned out to be a really poor chose of
|
|
|
|
* OSI string, and from Linux-2.6.23 onward we respond FALSE.
|
2008-01-24 08:50:56 +07:00
|
|
|
*
|
|
|
|
* BIOS writers should NOT query _OSI(Linux) on future systems.
|
2008-11-08 13:21:10 +07:00
|
|
|
* Linux will complain on the console when it sees it, and return FALSE.
|
|
|
|
* To get Linux to return TRUE for your system will require
|
|
|
|
* a kernel source update to add a DMI entry,
|
|
|
|
* or boot with "acpi_osi=Linux"
|
2008-01-24 08:50:56 +07:00
|
|
|
*/
|
|
|
|
|
2008-01-29 05:10:15 +07:00
|
|
|
static struct osi_linux {
|
2008-01-24 08:50:56 +07:00
|
|
|
unsigned int enable:1;
|
|
|
|
unsigned int dmi:1;
|
|
|
|
unsigned int cmdline:1;
|
2013-07-22 15:08:25 +07:00
|
|
|
unsigned int default_disabling:1;
|
|
|
|
} osi_linux = {0, 0, 0, 0};
|
2007-05-30 11:10:38 +07:00
|
|
|
|
2010-08-06 08:35:51 +07:00
|
|
|
static u32 acpi_osi_handler(acpi_string interface, u32 supported)
|
|
|
|
{
|
|
|
|
if (!strcmp("Linux", interface)) {
|
|
|
|
|
2011-08-02 11:45:48 +07:00
|
|
|
printk_once(KERN_NOTICE FW_BUG PREFIX
|
2010-08-06 08:35:51 +07:00
|
|
|
"BIOS _OSI(Linux) query %s%s\n",
|
|
|
|
osi_linux.enable ? "honored" : "ignored",
|
|
|
|
osi_linux.cmdline ? " via cmdline" :
|
|
|
|
osi_linux.dmi ? " via DMI" : "");
|
|
|
|
}
|
|
|
|
|
ACPI: Support _OSI("Darwin") correctly
Apple hardware queries _OSI("Darwin") in order to determine whether the
system is running OS X, and changes firmware behaviour based on the
answer. The most obvious difference in behaviour is that Thunderbolt
hardware is forcibly powered down unless the system is running OS X. The
obvious solution would be to simply add Darwin to the list of supported
_OSI strings, but this causes problems.
Recent Apple hardware includes two separate methods for checking _OSI
strings. The first will check whether Darwin is supported, and if so
will exit. The second will check whether Darwin is supported, but will
then continue to check for further operating systems. If a further
operating system is found then later firmware code will assume that the
OS is not OS X. This results in the unfortunate situation where the
Thunderbolt controller is available at boot time but remains powered
down after suspend.
The easiest way to handle this is to special-case it in the
Linux-specific OSI handling code. If we see Darwin, we should answer
true and then disable all other _OSI vendor strings.
The next problem is that the Apple PCI _OSC method has the following
code:
if (LEqual (0x01, OSDW ()))
if (LAnd (LEqual (Arg0, GUID), NEXP)
(do stuff)
else
(fail)
NEXP is a value in high memory and is presumably under the control of
the firmware. No methods sets it. The methods that are called in the "do
stuff" path are dummies. Unless there's some additional firmware call in
early boot, there's no way for this call to succeed - and even if it
does, it doesn't do anything.
The easiest way to handle this is simply to ignore it. We know which
flags would be set, so just set them by hand if the platform is running
in Darwin mode.
Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
[andreas.noever@gmail.com: merged two patches, do not touch ACPICA]
Signed-off-by: Andreas Noever <andreas.noever@gmail.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2014-09-20 18:19:47 +07:00
|
|
|
if (!strcmp("Darwin", interface)) {
|
|
|
|
/*
|
|
|
|
* Apple firmware will behave poorly if it receives positive
|
|
|
|
* answers to "Darwin" and any other OS. Respond positively
|
|
|
|
* to Darwin and then disable all other vendor strings.
|
|
|
|
*/
|
|
|
|
acpi_update_interfaces(ACPI_DISABLE_ALL_VENDOR_STRINGS);
|
|
|
|
supported = ACPI_UINT32_MAX;
|
|
|
|
}
|
|
|
|
|
2010-08-06 08:35:51 +07:00
|
|
|
return supported;
|
|
|
|
}
|
|
|
|
|
2011-11-08 06:23:27 +07:00
|
|
|
static void __init acpi_request_region (struct acpi_generic_address *gas,
|
2007-01-19 06:42:55 +07:00
|
|
|
unsigned int length, char *desc)
|
|
|
|
{
|
2011-11-08 06:23:27 +07:00
|
|
|
u64 addr;
|
|
|
|
|
|
|
|
/* Handle possible alignment issues */
|
|
|
|
memcpy(&addr, &gas->address, sizeof(addr));
|
|
|
|
if (!addr || !length)
|
2007-01-19 06:42:55 +07:00
|
|
|
return;
|
|
|
|
|
2010-07-21 05:18:36 +07:00
|
|
|
/* Resources are never freed */
|
2011-11-08 06:23:27 +07:00
|
|
|
if (gas->space_id == ACPI_ADR_SPACE_SYSTEM_IO)
|
|
|
|
request_region(addr, length, desc);
|
|
|
|
else if (gas->space_id == ACPI_ADR_SPACE_SYSTEM_MEMORY)
|
|
|
|
request_mem_region(addr, length, desc);
|
2007-01-19 06:42:55 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
static int __init acpi_reserve_resources(void)
|
|
|
|
{
|
2007-02-03 13:38:16 +07:00
|
|
|
acpi_request_region(&acpi_gbl_FADT.xpm1a_event_block, acpi_gbl_FADT.pm1_event_length,
|
2007-01-19 06:42:55 +07:00
|
|
|
"ACPI PM1a_EVT_BLK");
|
|
|
|
|
2007-02-03 13:38:16 +07:00
|
|
|
acpi_request_region(&acpi_gbl_FADT.xpm1b_event_block, acpi_gbl_FADT.pm1_event_length,
|
2007-01-19 06:42:55 +07:00
|
|
|
"ACPI PM1b_EVT_BLK");
|
|
|
|
|
2007-02-03 13:38:16 +07:00
|
|
|
acpi_request_region(&acpi_gbl_FADT.xpm1a_control_block, acpi_gbl_FADT.pm1_control_length,
|
2007-01-19 06:42:55 +07:00
|
|
|
"ACPI PM1a_CNT_BLK");
|
|
|
|
|
2007-02-03 13:38:16 +07:00
|
|
|
acpi_request_region(&acpi_gbl_FADT.xpm1b_control_block, acpi_gbl_FADT.pm1_control_length,
|
2007-01-19 06:42:55 +07:00
|
|
|
"ACPI PM1b_CNT_BLK");
|
|
|
|
|
2007-02-03 13:38:16 +07:00
|
|
|
if (acpi_gbl_FADT.pm_timer_length == 4)
|
|
|
|
acpi_request_region(&acpi_gbl_FADT.xpm_timer_block, 4, "ACPI PM_TMR");
|
2007-01-19 06:42:55 +07:00
|
|
|
|
2007-02-03 13:38:16 +07:00
|
|
|
acpi_request_region(&acpi_gbl_FADT.xpm2_control_block, acpi_gbl_FADT.pm2_control_length,
|
2007-01-19 06:42:55 +07:00
|
|
|
"ACPI PM2_CNT_BLK");
|
|
|
|
|
|
|
|
/* Length of GPE blocks must be a non-negative multiple of 2 */
|
|
|
|
|
2007-02-03 13:38:16 +07:00
|
|
|
if (!(acpi_gbl_FADT.gpe0_block_length & 0x1))
|
|
|
|
acpi_request_region(&acpi_gbl_FADT.xgpe0_block,
|
|
|
|
acpi_gbl_FADT.gpe0_block_length, "ACPI GPE0_BLK");
|
2007-01-19 06:42:55 +07:00
|
|
|
|
2007-02-03 13:38:16 +07:00
|
|
|
if (!(acpi_gbl_FADT.gpe1_block_length & 0x1))
|
|
|
|
acpi_request_region(&acpi_gbl_FADT.xgpe1_block,
|
|
|
|
acpi_gbl_FADT.gpe1_block_length, "ACPI GPE1_BLK");
|
2007-01-19 06:42:55 +07:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
device_initcall(acpi_reserve_resources);
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
void acpi_os_printf(const char *fmt, ...)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
va_list args;
|
|
|
|
va_start(args, fmt);
|
|
|
|
acpi_os_vprintf(fmt, args);
|
|
|
|
va_end(args);
|
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
|
|
|
void acpi_os_vprintf(const char *fmt, va_list args)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
static char buffer[512];
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
vsprintf(buffer, fmt, args);
|
|
|
|
|
|
|
|
#ifdef ENABLE_DEBUGGER
|
|
|
|
if (acpi_in_debugger) {
|
|
|
|
kdb_printf("%s", buffer);
|
|
|
|
} else {
|
2009-02-04 23:03:07 +07:00
|
|
|
printk(KERN_CONT "%s", buffer);
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
#else
|
2009-02-04 23:03:07 +07:00
|
|
|
printk(KERN_CONT "%s", buffer);
|
2005-04-17 05:20:36 +07:00
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
2011-07-15 05:05:21 +07:00
|
|
|
#ifdef CONFIG_KEXEC
|
|
|
|
static unsigned long acpi_rsdp;
|
|
|
|
static int __init setup_acpi_rsdp(char *arg)
|
|
|
|
{
|
2014-06-14 02:49:58 +07:00
|
|
|
if (kstrtoul(arg, 16, &acpi_rsdp))
|
|
|
|
return -EINVAL;
|
2011-07-15 05:05:21 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
early_param("acpi_rsdp", setup_acpi_rsdp);
|
|
|
|
#endif
|
|
|
|
|
2007-02-02 23:48:19 +07:00
|
|
|
acpi_physical_address __init acpi_os_get_root_pointer(void)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2011-07-15 05:05:21 +07:00
|
|
|
#ifdef CONFIG_KEXEC
|
|
|
|
if (acpi_rsdp)
|
|
|
|
return acpi_rsdp;
|
|
|
|
#endif
|
|
|
|
|
2012-11-14 16:42:35 +07:00
|
|
|
if (efi_enabled(EFI_CONFIG_TABLES)) {
|
2006-03-26 16:37:08 +07:00
|
|
|
if (efi.acpi20 != EFI_INVALID_TABLE_ADDR)
|
2007-02-02 23:48:19 +07:00
|
|
|
return efi.acpi20;
|
2006-03-26 16:37:08 +07:00
|
|
|
else if (efi.acpi != EFI_INVALID_TABLE_ADDR)
|
2007-02-02 23:48:19 +07:00
|
|
|
return efi.acpi;
|
2005-04-17 05:20:36 +07:00
|
|
|
else {
|
2005-08-05 11:44:28 +07:00
|
|
|
printk(KERN_ERR PREFIX
|
|
|
|
"System description tables not found\n");
|
2007-02-02 23:48:19 +07:00
|
|
|
return 0;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2014-07-18 17:02:52 +07:00
|
|
|
} else if (IS_ENABLED(CONFIG_ACPI_LEGACY_TABLES_LOOKUP)) {
|
2007-11-24 08:08:02 +07:00
|
|
|
acpi_physical_address pa = 0;
|
|
|
|
|
|
|
|
acpi_find_root_pointer(&pa);
|
|
|
|
return pa;
|
|
|
|
}
|
2014-07-18 17:02:52 +07:00
|
|
|
|
|
|
|
return 0;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
2010-10-22 03:24:09 +07:00
|
|
|
/* Must be called with 'acpi_ioremap_lock' or RCU read lock held. */
|
2010-10-22 03:24:14 +07:00
|
|
|
static struct acpi_ioremap *
|
|
|
|
acpi_map_lookup(acpi_physical_address phys, acpi_size size)
|
2010-10-22 03:23:53 +07:00
|
|
|
{
|
|
|
|
struct acpi_ioremap *map;
|
|
|
|
|
2010-10-22 03:24:09 +07:00
|
|
|
list_for_each_entry_rcu(map, &acpi_ioremaps, list)
|
2010-10-22 03:23:53 +07:00
|
|
|
if (map->phys <= phys &&
|
|
|
|
phys + size <= map->phys + map->size)
|
2010-10-22 03:24:14 +07:00
|
|
|
return map;
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Must be called with 'acpi_ioremap_lock' or RCU read lock held. */
|
|
|
|
static void __iomem *
|
|
|
|
acpi_map_vaddr_lookup(acpi_physical_address phys, unsigned int size)
|
|
|
|
{
|
|
|
|
struct acpi_ioremap *map;
|
|
|
|
|
|
|
|
map = acpi_map_lookup(phys, size);
|
|
|
|
if (map)
|
|
|
|
return map->virt + (phys - map->phys);
|
2010-10-22 03:23:53 +07:00
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2011-02-09 05:38:25 +07:00
|
|
|
void __iomem *acpi_os_get_iomem(acpi_physical_address phys, unsigned int size)
|
|
|
|
{
|
|
|
|
struct acpi_ioremap *map;
|
|
|
|
void __iomem *virt = NULL;
|
|
|
|
|
|
|
|
mutex_lock(&acpi_ioremap_lock);
|
|
|
|
map = acpi_map_lookup(phys, size);
|
|
|
|
if (map) {
|
|
|
|
virt = map->virt + (phys - map->phys);
|
|
|
|
map->refcount++;
|
|
|
|
}
|
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
|
|
|
return virt;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(acpi_os_get_iomem);
|
|
|
|
|
2010-10-22 03:24:09 +07:00
|
|
|
/* Must be called with 'acpi_ioremap_lock' or RCU read lock held. */
|
2010-10-22 03:23:53 +07:00
|
|
|
static struct acpi_ioremap *
|
|
|
|
acpi_map_lookup_virt(void __iomem *virt, acpi_size size)
|
|
|
|
{
|
|
|
|
struct acpi_ioremap *map;
|
|
|
|
|
2010-10-22 03:24:09 +07:00
|
|
|
list_for_each_entry_rcu(map, &acpi_ioremaps, list)
|
2010-10-22 03:24:14 +07:00
|
|
|
if (map->virt <= virt &&
|
|
|
|
virt + size <= map->virt + map->size)
|
2010-10-22 03:23:53 +07:00
|
|
|
return map;
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2012-01-21 09:13:30 +07:00
|
|
|
#ifndef CONFIG_IA64
|
|
|
|
#define should_use_kmap(pfn) page_is_ram(pfn)
|
|
|
|
#else
|
|
|
|
/* ioremap will take care of cache attributes */
|
|
|
|
#define should_use_kmap(pfn) 0
|
|
|
|
#endif
|
|
|
|
|
|
|
|
static void __iomem *acpi_map(acpi_physical_address pg_off, unsigned long pg_sz)
|
|
|
|
{
|
|
|
|
unsigned long pfn;
|
|
|
|
|
|
|
|
pfn = pg_off >> PAGE_SHIFT;
|
|
|
|
if (should_use_kmap(pfn)) {
|
|
|
|
if (pg_sz > PAGE_SIZE)
|
|
|
|
return NULL;
|
|
|
|
return (void __iomem __force *)kmap(pfn_to_page(pfn));
|
|
|
|
} else
|
|
|
|
return acpi_os_ioremap(pg_off, pg_sz);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void acpi_unmap(acpi_physical_address pg_off, void __iomem *vaddr)
|
|
|
|
{
|
|
|
|
unsigned long pfn;
|
|
|
|
|
|
|
|
pfn = pg_off >> PAGE_SHIFT;
|
2012-02-24 18:41:53 +07:00
|
|
|
if (should_use_kmap(pfn))
|
2012-01-21 09:13:30 +07:00
|
|
|
kunmap(pfn_to_page(pfn));
|
|
|
|
else
|
|
|
|
iounmap(vaddr);
|
|
|
|
}
|
|
|
|
|
2007-12-13 15:33:59 +07:00
|
|
|
void __iomem *__init_refok
|
2014-05-20 14:39:41 +07:00
|
|
|
acpi_os_map_iomem(acpi_physical_address phys, acpi_size size)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2011-02-09 05:38:05 +07:00
|
|
|
struct acpi_ioremap *map;
|
2010-10-22 03:23:53 +07:00
|
|
|
void __iomem *virt;
|
2011-01-20 04:27:14 +07:00
|
|
|
acpi_physical_address pg_off;
|
|
|
|
acpi_size pg_sz;
|
2010-10-22 03:23:53 +07:00
|
|
|
|
2006-03-26 16:37:10 +07:00
|
|
|
if (phys > ULONG_MAX) {
|
|
|
|
printk(KERN_ERR PREFIX "Cannot map memory that high\n");
|
2007-02-14 07:11:36 +07:00
|
|
|
return NULL;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2010-10-22 03:23:53 +07:00
|
|
|
|
|
|
|
if (!acpi_gbl_permanent_mmap)
|
2007-02-02 23:48:19 +07:00
|
|
|
return __acpi_map_table((unsigned long)phys, size);
|
2010-10-22 03:23:53 +07:00
|
|
|
|
2011-02-09 05:38:05 +07:00
|
|
|
mutex_lock(&acpi_ioremap_lock);
|
|
|
|
/* Check if there's a suitable mapping already. */
|
|
|
|
map = acpi_map_lookup(phys, size);
|
|
|
|
if (map) {
|
2011-02-09 05:38:15 +07:00
|
|
|
map->refcount++;
|
2011-02-09 05:38:05 +07:00
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
2010-10-22 03:23:53 +07:00
|
|
|
map = kzalloc(sizeof(*map), GFP_KERNEL);
|
2011-02-09 05:38:05 +07:00
|
|
|
if (!map) {
|
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
2010-10-22 03:23:53 +07:00
|
|
|
return NULL;
|
2011-02-09 05:38:05 +07:00
|
|
|
}
|
2010-10-22 03:23:53 +07:00
|
|
|
|
2010-10-22 03:24:14 +07:00
|
|
|
pg_off = round_down(phys, PAGE_SIZE);
|
|
|
|
pg_sz = round_up(phys + size, PAGE_SIZE) - pg_off;
|
2012-01-21 09:13:30 +07:00
|
|
|
virt = acpi_map(pg_off, pg_sz);
|
2010-10-22 03:23:53 +07:00
|
|
|
if (!virt) {
|
2011-02-09 05:38:05 +07:00
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
2010-10-22 03:23:53 +07:00
|
|
|
kfree(map);
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
INIT_LIST_HEAD(&map->list);
|
|
|
|
map->virt = virt;
|
2010-10-22 03:24:14 +07:00
|
|
|
map->phys = pg_off;
|
|
|
|
map->size = pg_sz;
|
2011-02-09 05:38:15 +07:00
|
|
|
map->refcount = 1;
|
2010-10-22 03:23:53 +07:00
|
|
|
|
2010-10-22 03:24:09 +07:00
|
|
|
list_add_tail_rcu(&map->list, &acpi_ioremaps);
|
2010-10-22 03:23:53 +07:00
|
|
|
|
2014-05-20 14:39:41 +07:00
|
|
|
out:
|
2011-02-09 05:38:05 +07:00
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
2010-10-22 03:24:14 +07:00
|
|
|
return map->virt + (phys - map->phys);
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2014-05-20 14:39:41 +07:00
|
|
|
EXPORT_SYMBOL_GPL(acpi_os_map_iomem);
|
|
|
|
|
|
|
|
void *__init_refok
|
|
|
|
acpi_os_map_memory(acpi_physical_address phys, acpi_size size)
|
|
|
|
{
|
|
|
|
return (void *)acpi_os_map_iomem(phys, size);
|
|
|
|
}
|
2006-01-08 16:03:15 +07:00
|
|
|
EXPORT_SYMBOL_GPL(acpi_os_map_memory);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2011-02-09 05:38:15 +07:00
|
|
|
static void acpi_os_drop_map_ref(struct acpi_ioremap *map)
|
2010-10-22 03:24:14 +07:00
|
|
|
{
|
2011-02-09 05:38:15 +07:00
|
|
|
if (!--map->refcount)
|
|
|
|
list_del_rcu(&map->list);
|
2010-10-22 03:24:14 +07:00
|
|
|
}
|
|
|
|
|
2011-02-09 05:38:15 +07:00
|
|
|
static void acpi_os_map_cleanup(struct acpi_ioremap *map)
|
2011-02-09 05:37:53 +07:00
|
|
|
{
|
2011-02-09 05:38:15 +07:00
|
|
|
if (!map->refcount) {
|
|
|
|
synchronize_rcu();
|
2012-01-21 09:13:30 +07:00
|
|
|
acpi_unmap(map->phys, map->virt);
|
2011-02-09 05:38:15 +07:00
|
|
|
kfree(map);
|
|
|
|
}
|
2010-10-22 03:24:14 +07:00
|
|
|
}
|
|
|
|
|
2014-05-20 14:39:41 +07:00
|
|
|
void __ref acpi_os_unmap_iomem(void __iomem *virt, acpi_size size)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2010-10-22 03:23:53 +07:00
|
|
|
struct acpi_ioremap *map;
|
|
|
|
|
|
|
|
if (!acpi_gbl_permanent_mmap) {
|
2009-02-08 06:39:41 +07:00
|
|
|
__acpi_unmap_table(virt, size);
|
2010-10-22 03:23:53 +07:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2011-02-09 05:37:42 +07:00
|
|
|
mutex_lock(&acpi_ioremap_lock);
|
2010-10-22 03:23:53 +07:00
|
|
|
map = acpi_map_lookup_virt(virt, size);
|
|
|
|
if (!map) {
|
2011-02-09 05:37:42 +07:00
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
2011-02-09 05:37:53 +07:00
|
|
|
WARN(true, PREFIX "%s: bad address %p\n", __func__, virt);
|
2010-10-22 03:23:53 +07:00
|
|
|
return;
|
|
|
|
}
|
2011-02-09 05:38:15 +07:00
|
|
|
acpi_os_drop_map_ref(map);
|
2011-02-09 05:37:42 +07:00
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
2010-10-22 03:23:53 +07:00
|
|
|
|
2011-02-09 05:38:15 +07:00
|
|
|
acpi_os_map_cleanup(map);
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2014-05-20 14:39:41 +07:00
|
|
|
EXPORT_SYMBOL_GPL(acpi_os_unmap_iomem);
|
|
|
|
|
|
|
|
void __ref acpi_os_unmap_memory(void *virt, acpi_size size)
|
|
|
|
{
|
|
|
|
return acpi_os_unmap_iomem((void __iomem *)virt, size);
|
|
|
|
}
|
2006-01-08 16:03:15 +07:00
|
|
|
EXPORT_SYMBOL_GPL(acpi_os_unmap_memory);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2009-02-23 05:58:56 +07:00
|
|
|
void __init early_acpi_os_unmap_memory(void __iomem *virt, acpi_size size)
|
2009-02-08 06:39:41 +07:00
|
|
|
{
|
|
|
|
if (!acpi_gbl_permanent_mmap)
|
|
|
|
__acpi_unmap_table(virt, size);
|
|
|
|
}
|
|
|
|
|
2011-11-08 06:23:34 +07:00
|
|
|
int acpi_os_map_generic_address(struct acpi_generic_address *gas)
|
2010-10-22 03:23:59 +07:00
|
|
|
{
|
2011-11-08 06:23:27 +07:00
|
|
|
u64 addr;
|
2010-10-22 03:23:59 +07:00
|
|
|
void __iomem *virt;
|
|
|
|
|
2011-11-08 06:23:27 +07:00
|
|
|
if (gas->space_id != ACPI_ADR_SPACE_SYSTEM_MEMORY)
|
2010-10-22 03:23:59 +07:00
|
|
|
return 0;
|
|
|
|
|
2011-11-08 06:23:27 +07:00
|
|
|
/* Handle possible alignment issues */
|
|
|
|
memcpy(&addr, &gas->address, sizeof(addr));
|
|
|
|
if (!addr || !gas->bit_width)
|
2010-10-22 03:23:59 +07:00
|
|
|
return -EINVAL;
|
|
|
|
|
2014-05-20 14:39:41 +07:00
|
|
|
virt = acpi_os_map_iomem(addr, gas->bit_width / 8);
|
2010-10-22 03:23:59 +07:00
|
|
|
if (!virt)
|
|
|
|
return -EIO;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2011-11-08 06:23:34 +07:00
|
|
|
EXPORT_SYMBOL(acpi_os_map_generic_address);
|
2010-10-22 03:23:59 +07:00
|
|
|
|
2011-11-08 06:23:34 +07:00
|
|
|
void acpi_os_unmap_generic_address(struct acpi_generic_address *gas)
|
2010-10-22 03:23:59 +07:00
|
|
|
{
|
2011-11-08 06:23:27 +07:00
|
|
|
u64 addr;
|
2011-02-09 05:37:53 +07:00
|
|
|
struct acpi_ioremap *map;
|
2010-10-22 03:23:59 +07:00
|
|
|
|
2011-11-08 06:23:27 +07:00
|
|
|
if (gas->space_id != ACPI_ADR_SPACE_SYSTEM_MEMORY)
|
2010-10-22 03:23:59 +07:00
|
|
|
return;
|
|
|
|
|
2011-11-08 06:23:27 +07:00
|
|
|
/* Handle possible alignment issues */
|
|
|
|
memcpy(&addr, &gas->address, sizeof(addr));
|
|
|
|
if (!addr || !gas->bit_width)
|
2010-10-22 03:23:59 +07:00
|
|
|
return;
|
|
|
|
|
2011-02-09 05:37:42 +07:00
|
|
|
mutex_lock(&acpi_ioremap_lock);
|
2011-11-08 06:23:27 +07:00
|
|
|
map = acpi_map_lookup(addr, gas->bit_width / 8);
|
2011-02-09 05:37:53 +07:00
|
|
|
if (!map) {
|
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
|
|
|
return;
|
|
|
|
}
|
2011-02-09 05:38:15 +07:00
|
|
|
acpi_os_drop_map_ref(map);
|
2011-02-09 05:37:42 +07:00
|
|
|
mutex_unlock(&acpi_ioremap_lock);
|
2010-10-22 03:23:59 +07:00
|
|
|
|
2011-02-09 05:38:15 +07:00
|
|
|
acpi_os_map_cleanup(map);
|
2010-10-22 03:23:59 +07:00
|
|
|
}
|
2011-11-08 06:23:34 +07:00
|
|
|
EXPORT_SYMBOL(acpi_os_unmap_generic_address);
|
2010-10-22 03:23:59 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
#ifdef ACPI_FUTURE_USAGE
|
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_get_physical_address(void *virt, acpi_physical_address * phys)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
if (!phys || !virt)
|
2005-04-17 05:20:36 +07:00
|
|
|
return AE_BAD_PARAMETER;
|
|
|
|
|
|
|
|
*phys = virt_to_phys(virt);
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#define ACPI_MAX_OVERRIDE_LEN 100
|
|
|
|
|
|
|
|
static char acpi_os_name[ACPI_MAX_OVERRIDE_LEN];
|
|
|
|
|
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_predefined_override(const struct acpi_predefined_names *init_val,
|
|
|
|
acpi_string * new_val)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
if (!init_val || !new_val)
|
|
|
|
return AE_BAD_PARAMETER;
|
|
|
|
|
|
|
|
*new_val = NULL;
|
2005-08-05 11:44:28 +07:00
|
|
|
if (!memcmp(init_val->name, "_OS_", 4) && strlen(acpi_os_name)) {
|
2005-04-17 05:20:36 +07:00
|
|
|
printk(KERN_INFO PREFIX "Overriding _OS definition to '%s'\n",
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_name);
|
2005-04-17 05:20:36 +07:00
|
|
|
*new_val = acpi_os_name;
|
|
|
|
}
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
2012-10-01 05:23:54 +07:00
|
|
|
#ifdef CONFIG_ACPI_INITRD_TABLE_OVERRIDE
|
|
|
|
#include <linux/earlycpio.h>
|
|
|
|
#include <linux/memblock.h>
|
|
|
|
|
|
|
|
static u64 acpi_tables_addr;
|
|
|
|
static int all_tables_size;
|
|
|
|
|
|
|
|
/* Copied from acpica/tbutils.c:acpi_tb_checksum() */
|
2013-12-17 16:13:05 +07:00
|
|
|
static u8 __init acpi_table_checksum(u8 *buffer, u32 length)
|
2012-10-01 05:23:54 +07:00
|
|
|
{
|
|
|
|
u8 sum = 0;
|
|
|
|
u8 *end = buffer + length;
|
|
|
|
|
|
|
|
while (buffer < end)
|
|
|
|
sum = (u8) (sum + *(buffer++));
|
|
|
|
return sum;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* All but ACPI_SIG_RSDP and ACPI_SIG_FACS: */
|
|
|
|
static const char * const table_sigs[] = {
|
|
|
|
ACPI_SIG_BERT, ACPI_SIG_CPEP, ACPI_SIG_ECDT, ACPI_SIG_EINJ,
|
|
|
|
ACPI_SIG_ERST, ACPI_SIG_HEST, ACPI_SIG_MADT, ACPI_SIG_MSCT,
|
|
|
|
ACPI_SIG_SBST, ACPI_SIG_SLIT, ACPI_SIG_SRAT, ACPI_SIG_ASF,
|
|
|
|
ACPI_SIG_BOOT, ACPI_SIG_DBGP, ACPI_SIG_DMAR, ACPI_SIG_HPET,
|
|
|
|
ACPI_SIG_IBFT, ACPI_SIG_IVRS, ACPI_SIG_MCFG, ACPI_SIG_MCHI,
|
|
|
|
ACPI_SIG_SLIC, ACPI_SIG_SPCR, ACPI_SIG_SPMI, ACPI_SIG_TCPA,
|
|
|
|
ACPI_SIG_UEFI, ACPI_SIG_WAET, ACPI_SIG_WDAT, ACPI_SIG_WDDT,
|
|
|
|
ACPI_SIG_WDRT, ACPI_SIG_DSDT, ACPI_SIG_FADT, ACPI_SIG_PSDT,
|
|
|
|
ACPI_SIG_RSDT, ACPI_SIG_XSDT, ACPI_SIG_SSDT, NULL };
|
|
|
|
|
|
|
|
#define ACPI_HEADER_SIZE sizeof(struct acpi_table_header)
|
|
|
|
|
2013-09-07 09:08:00 +07:00
|
|
|
#define ACPI_OVERRIDE_TABLES 64
|
|
|
|
static struct cpio_data __initdata acpi_initrd_files[ACPI_OVERRIDE_TABLES];
|
|
|
|
|
|
|
|
#define MAP_CHUNK_SIZE (NR_FIX_BTMAPS << PAGE_SHIFT)
|
2012-10-01 05:23:54 +07:00
|
|
|
|
|
|
|
void __init acpi_initrd_override(void *data, size_t size)
|
|
|
|
{
|
|
|
|
int sig, no, table_nr = 0, total_offset = 0;
|
|
|
|
long offset = 0;
|
|
|
|
struct acpi_table_header *table;
|
|
|
|
char cpio_path[32] = "kernel/firmware/acpi/";
|
|
|
|
struct cpio_data file;
|
|
|
|
|
|
|
|
if (data == NULL || size == 0)
|
|
|
|
return;
|
|
|
|
|
|
|
|
for (no = 0; no < ACPI_OVERRIDE_TABLES; no++) {
|
|
|
|
file = find_cpio_data(cpio_path, data, size, &offset);
|
|
|
|
if (!file.data)
|
|
|
|
break;
|
|
|
|
|
|
|
|
data += offset;
|
|
|
|
size -= offset;
|
|
|
|
|
2013-08-14 16:37:08 +07:00
|
|
|
if (file.size < sizeof(struct acpi_table_header)) {
|
|
|
|
pr_err("ACPI OVERRIDE: Table smaller than ACPI header [%s%s]\n",
|
|
|
|
cpio_path, file.name);
|
|
|
|
continue;
|
|
|
|
}
|
2012-10-01 05:23:54 +07:00
|
|
|
|
|
|
|
table = file.data;
|
|
|
|
|
|
|
|
for (sig = 0; table_sigs[sig]; sig++)
|
|
|
|
if (!memcmp(table->signature, table_sigs[sig], 4))
|
|
|
|
break;
|
|
|
|
|
2013-08-14 16:37:08 +07:00
|
|
|
if (!table_sigs[sig]) {
|
|
|
|
pr_err("ACPI OVERRIDE: Unknown signature [%s%s]\n",
|
|
|
|
cpio_path, file.name);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
if (file.size != table->length) {
|
|
|
|
pr_err("ACPI OVERRIDE: File length does not match table length [%s%s]\n",
|
|
|
|
cpio_path, file.name);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
if (acpi_table_checksum(file.data, table->length)) {
|
|
|
|
pr_err("ACPI OVERRIDE: Bad table checksum [%s%s]\n",
|
|
|
|
cpio_path, file.name);
|
|
|
|
continue;
|
|
|
|
}
|
2012-10-01 05:23:54 +07:00
|
|
|
|
|
|
|
pr_info("%4.4s ACPI table found in initrd [%s%s][0x%x]\n",
|
|
|
|
table->signature, cpio_path, file.name, table->length);
|
|
|
|
|
|
|
|
all_tables_size += table->length;
|
2013-09-07 09:08:00 +07:00
|
|
|
acpi_initrd_files[table_nr].data = file.data;
|
|
|
|
acpi_initrd_files[table_nr].size = file.size;
|
2012-10-01 05:23:54 +07:00
|
|
|
table_nr++;
|
|
|
|
}
|
|
|
|
if (table_nr == 0)
|
|
|
|
return;
|
|
|
|
|
|
|
|
acpi_tables_addr =
|
|
|
|
memblock_find_in_range(0, max_low_pfn_mapped << PAGE_SHIFT,
|
|
|
|
all_tables_size, PAGE_SIZE);
|
|
|
|
if (!acpi_tables_addr) {
|
|
|
|
WARN_ON(1);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
* Only calling e820_add_reserve does not work and the
|
|
|
|
* tables are invalid (memory got used) later.
|
|
|
|
* memblock_reserve works as expected and the tables won't get modified.
|
|
|
|
* But it's not enough on X86 because ioremap will
|
|
|
|
* complain later (used by acpi_os_map_memory) that the pages
|
|
|
|
* that should get mapped are not marked "reserved".
|
|
|
|
* Both memblock_reserve and e820_add_region (via arch_reserve_mem_area)
|
|
|
|
* works fine.
|
|
|
|
*/
|
2013-04-23 06:19:19 +07:00
|
|
|
memblock_reserve(acpi_tables_addr, all_tables_size);
|
2012-10-01 05:23:54 +07:00
|
|
|
arch_reserve_mem_area(acpi_tables_addr, all_tables_size);
|
|
|
|
|
2013-09-07 09:08:00 +07:00
|
|
|
/*
|
|
|
|
* early_ioremap only can remap 256k one time. If we map all
|
|
|
|
* tables one time, we will hit the limit. Need to map chunks
|
|
|
|
* one by one during copying the same as that in relocate_initrd().
|
|
|
|
*/
|
2012-10-01 05:23:54 +07:00
|
|
|
for (no = 0; no < table_nr; no++) {
|
2013-09-07 09:08:00 +07:00
|
|
|
unsigned char *src_p = acpi_initrd_files[no].data;
|
|
|
|
phys_addr_t size = acpi_initrd_files[no].size;
|
|
|
|
phys_addr_t dest_addr = acpi_tables_addr + total_offset;
|
|
|
|
phys_addr_t slop, clen;
|
|
|
|
char *dest_p;
|
|
|
|
|
|
|
|
total_offset += size;
|
|
|
|
|
|
|
|
while (size) {
|
|
|
|
slop = dest_addr & ~PAGE_MASK;
|
|
|
|
clen = size;
|
|
|
|
if (clen > MAP_CHUNK_SIZE - slop)
|
|
|
|
clen = MAP_CHUNK_SIZE - slop;
|
|
|
|
dest_p = early_ioremap(dest_addr & PAGE_MASK,
|
|
|
|
clen + slop);
|
|
|
|
memcpy(dest_p + slop, src_p, clen);
|
|
|
|
early_iounmap(dest_p, clen + slop);
|
|
|
|
src_p += clen;
|
|
|
|
dest_addr += clen;
|
|
|
|
size -= clen;
|
|
|
|
}
|
2012-10-01 05:23:54 +07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif /* CONFIG_ACPI_INITRD_TABLE_OVERRIDE */
|
|
|
|
|
2012-10-01 05:23:56 +07:00
|
|
|
static void acpi_table_taint(struct acpi_table_header *table)
|
|
|
|
{
|
|
|
|
pr_warn(PREFIX
|
|
|
|
"Override [%4.4s-%8.8s], this is unsafe: tainting kernel\n",
|
|
|
|
table->signature, table->oem_table_id);
|
2013-01-21 13:47:39 +07:00
|
|
|
add_taint(TAINT_OVERRIDDEN_ACPI_TABLE, LOCKDEP_NOW_UNRELIABLE);
|
2012-10-01 05:23:56 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_table_override(struct acpi_table_header * existing_table,
|
|
|
|
struct acpi_table_header ** new_table)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
if (!existing_table || !new_table)
|
|
|
|
return AE_BAD_PARAMETER;
|
|
|
|
|
2008-02-05 06:04:06 +07:00
|
|
|
*new_table = NULL;
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
#ifdef CONFIG_ACPI_CUSTOM_DSDT
|
|
|
|
if (strncmp(existing_table->signature, "DSDT", 4) == 0)
|
2005-08-05 11:44:28 +07:00
|
|
|
*new_table = (struct acpi_table_header *)AmlCode;
|
2005-04-17 05:20:36 +07:00
|
|
|
#endif
|
2012-10-01 05:23:56 +07:00
|
|
|
if (*new_table != NULL)
|
|
|
|
acpi_table_taint(existing_table);
|
2005-04-17 05:20:36 +07:00
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
2012-02-14 17:31:56 +07:00
|
|
|
acpi_status
|
|
|
|
acpi_os_physical_table_override(struct acpi_table_header *existing_table,
|
2012-10-01 05:23:55 +07:00
|
|
|
acpi_physical_address *address,
|
|
|
|
u32 *table_length)
|
2012-02-14 17:31:56 +07:00
|
|
|
{
|
2012-10-01 05:23:55 +07:00
|
|
|
#ifndef CONFIG_ACPI_INITRD_TABLE_OVERRIDE
|
|
|
|
*table_length = 0;
|
|
|
|
*address = 0;
|
|
|
|
return AE_OK;
|
|
|
|
#else
|
|
|
|
int table_offset = 0;
|
|
|
|
struct acpi_table_header *table;
|
|
|
|
|
|
|
|
*table_length = 0;
|
|
|
|
*address = 0;
|
|
|
|
|
|
|
|
if (!acpi_tables_addr)
|
|
|
|
return AE_OK;
|
|
|
|
|
|
|
|
do {
|
|
|
|
if (table_offset + ACPI_HEADER_SIZE > all_tables_size) {
|
|
|
|
WARN_ON(1);
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
table = acpi_os_map_memory(acpi_tables_addr + table_offset,
|
|
|
|
ACPI_HEADER_SIZE);
|
2012-02-14 17:31:56 +07:00
|
|
|
|
2012-10-01 05:23:55 +07:00
|
|
|
if (table_offset + table->length > all_tables_size) {
|
|
|
|
acpi_os_unmap_memory(table, ACPI_HEADER_SIZE);
|
|
|
|
WARN_ON(1);
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
table_offset += table->length;
|
|
|
|
|
|
|
|
if (memcmp(existing_table->signature, table->signature, 4)) {
|
|
|
|
acpi_os_unmap_memory(table,
|
|
|
|
ACPI_HEADER_SIZE);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Only override tables with matching oem id */
|
|
|
|
if (memcmp(table->oem_table_id, existing_table->oem_table_id,
|
|
|
|
ACPI_OEM_TABLE_ID_SIZE)) {
|
|
|
|
acpi_os_unmap_memory(table,
|
|
|
|
ACPI_HEADER_SIZE);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
table_offset -= table->length;
|
|
|
|
*table_length = table->length;
|
|
|
|
acpi_os_unmap_memory(table, ACPI_HEADER_SIZE);
|
|
|
|
*address = acpi_tables_addr + table_offset;
|
|
|
|
break;
|
|
|
|
} while (table_offset + ACPI_HEADER_SIZE < all_tables_size);
|
2012-02-14 17:31:56 +07:00
|
|
|
|
2012-10-01 05:23:56 +07:00
|
|
|
if (*address != 0)
|
|
|
|
acpi_table_taint(existing_table);
|
2012-10-01 05:23:55 +07:00
|
|
|
return AE_OK;
|
|
|
|
#endif
|
|
|
|
}
|
2012-02-14 17:31:56 +07:00
|
|
|
|
IRQ: Maintain regs pointer globally rather than passing to IRQ handlers
Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.
The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around. On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).
Where appropriate, an arch may override the generic storage facility and do
something different with the variable. On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.
Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions. Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller. A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.
I've build this code with allyesconfig for x86_64 and i386. I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.
This will affect all archs. Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
struct pt_regs *old_regs = set_irq_regs(regs);
And put the old one back at the end:
set_irq_regs(old_regs);
Don't pass regs through to generic_handle_irq() or __do_IRQ().
In timer_interrupt(), this sort of change will be necessary:
- update_process_times(user_mode(regs));
- profile_tick(CPU_PROFILING, regs);
+ update_process_times(user_mode(get_irq_regs()));
+ profile_tick(CPU_PROFILING);
I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().
Some notes on the interrupt handling in the drivers:
(*) input_dev() is now gone entirely. The regs pointer is no longer stored in
the input_dev struct.
(*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
something different depending on whether it's been supplied with a regs
pointer or not.
(*) Various IRQ handler function pointers have been moved to type
irq_handler_t.
Signed-Off-By: David Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
2006-10-05 20:55:46 +07:00
|
|
|
static irqreturn_t acpi_irq(int irq, void *dev_id)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2008-02-06 13:26:55 +07:00
|
|
|
u32 handled;
|
|
|
|
|
|
|
|
handled = (*acpi_irq_handler) (acpi_irq_context);
|
|
|
|
|
|
|
|
if (handled) {
|
|
|
|
acpi_irq_handled++;
|
|
|
|
return IRQ_HANDLED;
|
2009-04-21 11:35:47 +07:00
|
|
|
} else {
|
|
|
|
acpi_irq_not_handled++;
|
2008-02-06 13:26:55 +07:00
|
|
|
return IRQ_NONE;
|
2009-04-21 11:35:47 +07:00
|
|
|
}
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_install_interrupt_handler(u32 gsi, acpi_osd_handler handler,
|
|
|
|
void *context)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
unsigned int irq;
|
|
|
|
|
2008-02-06 13:26:55 +07:00
|
|
|
acpi_irq_stats_init();
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
/*
|
2011-02-09 05:48:16 +07:00
|
|
|
* ACPI interrupts different from the SCI in our copy of the FADT are
|
|
|
|
* not supported.
|
2005-04-17 05:20:36 +07:00
|
|
|
*/
|
2011-02-09 05:48:16 +07:00
|
|
|
if (gsi != acpi_gbl_FADT.sci_interrupt)
|
|
|
|
return AE_BAD_PARAMETER;
|
|
|
|
|
|
|
|
if (acpi_irq_handler)
|
|
|
|
return AE_ALREADY_ACQUIRED;
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
if (acpi_gsi_to_irq(gsi, &irq) < 0) {
|
|
|
|
printk(KERN_ERR PREFIX "SCI (ACPI GSI %d) not registered\n",
|
|
|
|
gsi);
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
acpi_irq_handler = handler;
|
|
|
|
acpi_irq_context = context;
|
2014-09-30 07:29:01 +07:00
|
|
|
if (request_irq(irq, acpi_irq, IRQF_SHARED, "acpi", acpi_irq)) {
|
2005-04-17 05:20:36 +07:00
|
|
|
printk(KERN_ERR PREFIX "SCI (IRQ%d) allocation failed\n", irq);
|
2011-02-09 05:48:16 +07:00
|
|
|
acpi_irq_handler = NULL;
|
2005-04-17 05:20:36 +07:00
|
|
|
return AE_NOT_ACQUIRED;
|
|
|
|
}
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_remove_interrupt_handler(u32 irq, acpi_osd_handler handler)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2011-02-09 05:48:16 +07:00
|
|
|
if (irq != acpi_gbl_FADT.sci_interrupt)
|
|
|
|
return AE_BAD_PARAMETER;
|
|
|
|
|
|
|
|
free_irq(irq, acpi_irq);
|
|
|
|
acpi_irq_handler = NULL;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Running in interpreter thread context, safe to sleep
|
|
|
|
*/
|
|
|
|
|
2010-01-28 09:53:19 +07:00
|
|
|
void acpi_os_sleep(u64 ms)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2013-09-12 00:42:57 +07:00
|
|
|
msleep(ms);
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
|
|
|
void acpi_os_stall(u32 us)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
while (us) {
|
|
|
|
u32 delay = 1000;
|
|
|
|
|
|
|
|
if (delay > us)
|
|
|
|
delay = us;
|
|
|
|
udelay(delay);
|
|
|
|
touch_nmi_watchdog();
|
|
|
|
us -= delay;
|
|
|
|
}
|
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
/*
|
|
|
|
* Support ACPI 3.0 AML Timer operand
|
|
|
|
* Returns 64-bit free-running, monotonically increasing timer
|
|
|
|
* with 100ns granularity
|
|
|
|
*/
|
2005-08-05 11:44:28 +07:00
|
|
|
u64 acpi_os_get_timer(void)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
ACPI: implement acpi_os_get_timer() according the spec
ACPI Timer() opcode should return monotonically increasing clock with 100ns
granularity according the ACPI 5.0 spec.
Testing the current Timer() implementation with following ASL code (and an
additional debug print in acpi_os_sleep() to get the sleep times dumped out
to dmesg):
// Test: 10ms
Store(Timer, Local1)
Sleep(10)
Divide(Subtract(Timer, Local1), 10000,, Local1)
Sleep(Local1)
// Test: 200ms
Store(Timer, Local1)
Sleep(200)
Divide(Subtract(Timer, Local1), 10000,, Local1)
Sleep(Local1)
// Test 1300ms
Store(Timer, Local1)
Sleep(1300)
Divide(Subtract(Timer, Local1), 10000,, Local1)
Sleep(Local1)
The second sleep value is calculated using Timer(). If the implementation
is good enough we should be able to get the second value pretty close to
the first.
However, the current Timer() gives pretty bad sleep times:
[ 11.488100] ACPI: acpi_os_get_timer() TBD
[ 11.492150] ACPI: Sleep(10)
[ 11.502993] ACPI: Sleep(0)
[ 11.506315] ACPI: Sleep(200)
[ 11.706237] ACPI: Sleep(0)
[ 11.709550] ACPI: Sleep(1300)
[ 13.008929] ACPI: Sleep(0)
Fix this with the help of ktime_get(). Once the fix is applied and run
against the same ASL code we get:
[ 11.486786] ACPI: Sleep(10)
[ 11.499029] ACPI: Sleep(12)
[ 11.512350] ACPI: Sleep(200)
[ 11.712282] ACPI: Sleep(200)
[ 11.912170] ACPI: Sleep(1300)
[ 13.211577] ACPI: Sleep(1300)
That is much more closer to the values we expected.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
2013-05-23 14:27:46 +07:00
|
|
|
u64 time_ns = ktime_to_ns(ktime_get());
|
|
|
|
do_div(time_ns, 100);
|
|
|
|
return time_ns;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_read_port(acpi_io_address port, u32 * value, u32 width)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
u32 dummy;
|
|
|
|
|
|
|
|
if (!value)
|
|
|
|
value = &dummy;
|
|
|
|
|
2007-11-15 16:01:06 +07:00
|
|
|
*value = 0;
|
|
|
|
if (width <= 8) {
|
2005-08-05 11:44:28 +07:00
|
|
|
*(u8 *) value = inb(port);
|
2007-11-15 16:01:06 +07:00
|
|
|
} else if (width <= 16) {
|
2005-08-05 11:44:28 +07:00
|
|
|
*(u16 *) value = inw(port);
|
2007-11-15 16:01:06 +07:00
|
|
|
} else if (width <= 32) {
|
2005-08-05 11:44:28 +07:00
|
|
|
*(u32 *) value = inl(port);
|
2007-11-15 16:01:06 +07:00
|
|
|
} else {
|
2005-04-17 05:20:36 +07:00
|
|
|
BUG();
|
|
|
|
}
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
EXPORT_SYMBOL(acpi_os_read_port);
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_write_port(acpi_io_address port, u32 value, u32 width)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2007-11-15 16:01:06 +07:00
|
|
|
if (width <= 8) {
|
2005-04-17 05:20:36 +07:00
|
|
|
outb(value, port);
|
2007-11-15 16:01:06 +07:00
|
|
|
} else if (width <= 16) {
|
2005-04-17 05:20:36 +07:00
|
|
|
outw(value, port);
|
2007-11-15 16:01:06 +07:00
|
|
|
} else if (width <= 32) {
|
2005-04-17 05:20:36 +07:00
|
|
|
outl(value, port);
|
2007-11-15 16:01:06 +07:00
|
|
|
} else {
|
2005-04-17 05:20:36 +07:00
|
|
|
BUG();
|
|
|
|
}
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
EXPORT_SYMBOL(acpi_os_write_port);
|
|
|
|
|
2012-01-21 09:13:24 +07:00
|
|
|
#ifdef readq
|
|
|
|
static inline u64 read64(const volatile void __iomem *addr)
|
|
|
|
{
|
|
|
|
return readq(addr);
|
|
|
|
}
|
|
|
|
#else
|
|
|
|
static inline u64 read64(const volatile void __iomem *addr)
|
|
|
|
{
|
|
|
|
u64 l, h;
|
|
|
|
l = readl(addr);
|
|
|
|
h = readl(addr+4);
|
|
|
|
return l | (h << 32);
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
acpi_status
|
2012-02-14 17:29:55 +07:00
|
|
|
acpi_os_read_memory(acpi_physical_address phys_addr, u64 *value, u32 width)
|
2012-01-21 09:13:24 +07:00
|
|
|
{
|
|
|
|
void __iomem *virt_addr;
|
|
|
|
unsigned int size = width / 8;
|
|
|
|
bool unmap = false;
|
|
|
|
u64 dummy;
|
|
|
|
|
|
|
|
rcu_read_lock();
|
|
|
|
virt_addr = acpi_map_vaddr_lookup(phys_addr, size);
|
|
|
|
if (!virt_addr) {
|
|
|
|
rcu_read_unlock();
|
|
|
|
virt_addr = acpi_os_ioremap(phys_addr, size);
|
|
|
|
if (!virt_addr)
|
|
|
|
return AE_BAD_ADDRESS;
|
|
|
|
unmap = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!value)
|
|
|
|
value = &dummy;
|
|
|
|
|
|
|
|
switch (width) {
|
|
|
|
case 8:
|
|
|
|
*(u8 *) value = readb(virt_addr);
|
|
|
|
break;
|
|
|
|
case 16:
|
|
|
|
*(u16 *) value = readw(virt_addr);
|
|
|
|
break;
|
|
|
|
case 32:
|
|
|
|
*(u32 *) value = readl(virt_addr);
|
|
|
|
break;
|
|
|
|
case 64:
|
|
|
|
*(u64 *) value = read64(virt_addr);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
BUG();
|
|
|
|
}
|
|
|
|
|
|
|
|
if (unmap)
|
|
|
|
iounmap(virt_addr);
|
|
|
|
else
|
|
|
|
rcu_read_unlock();
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
#ifdef writeq
|
|
|
|
static inline void write64(u64 val, volatile void __iomem *addr)
|
|
|
|
{
|
|
|
|
writeq(val, addr);
|
|
|
|
}
|
|
|
|
#else
|
|
|
|
static inline void write64(u64 val, volatile void __iomem *addr)
|
|
|
|
{
|
|
|
|
writel(val, addr);
|
|
|
|
writel(val>>32, addr+4);
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
acpi_status
|
2012-02-14 17:29:55 +07:00
|
|
|
acpi_os_write_memory(acpi_physical_address phys_addr, u64 value, u32 width)
|
2012-01-21 09:13:24 +07:00
|
|
|
{
|
|
|
|
void __iomem *virt_addr;
|
|
|
|
unsigned int size = width / 8;
|
|
|
|
bool unmap = false;
|
|
|
|
|
|
|
|
rcu_read_lock();
|
|
|
|
virt_addr = acpi_map_vaddr_lookup(phys_addr, size);
|
|
|
|
if (!virt_addr) {
|
|
|
|
rcu_read_unlock();
|
|
|
|
virt_addr = acpi_os_ioremap(phys_addr, size);
|
|
|
|
if (!virt_addr)
|
|
|
|
return AE_BAD_ADDRESS;
|
|
|
|
unmap = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (width) {
|
|
|
|
case 8:
|
|
|
|
writeb(value, virt_addr);
|
|
|
|
break;
|
|
|
|
case 16:
|
|
|
|
writew(value, virt_addr);
|
|
|
|
break;
|
|
|
|
case 32:
|
|
|
|
writel(value, virt_addr);
|
|
|
|
break;
|
|
|
|
case 64:
|
|
|
|
write64(value, virt_addr);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
BUG();
|
|
|
|
}
|
|
|
|
|
|
|
|
if (unmap)
|
|
|
|
iounmap(virt_addr);
|
|
|
|
else
|
|
|
|
rcu_read_unlock();
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_read_pci_configuration(struct acpi_pci_id * pci_id, u32 reg,
|
2010-08-06 07:57:53 +07:00
|
|
|
u64 *value, u32 width)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
int result, size;
|
2010-08-06 07:57:53 +07:00
|
|
|
u32 value32;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (!value)
|
|
|
|
return AE_BAD_PARAMETER;
|
|
|
|
|
|
|
|
switch (width) {
|
|
|
|
case 8:
|
|
|
|
size = 1;
|
|
|
|
break;
|
|
|
|
case 16:
|
|
|
|
size = 2;
|
|
|
|
break;
|
|
|
|
case 32:
|
|
|
|
size = 4;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
return AE_ERROR;
|
|
|
|
}
|
|
|
|
|
2008-02-10 21:45:28 +07:00
|
|
|
result = raw_pci_read(pci_id->segment, pci_id->bus,
|
|
|
|
PCI_DEVFN(pci_id->device, pci_id->function),
|
2010-08-06 07:57:53 +07:00
|
|
|
reg, size, &value32);
|
|
|
|
*value = value32;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
return (result ? AE_ERROR : AE_OK);
|
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_write_pci_configuration(struct acpi_pci_id * pci_id, u32 reg,
|
2010-01-28 09:53:19 +07:00
|
|
|
u64 value, u32 width)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
int result, size;
|
|
|
|
|
|
|
|
switch (width) {
|
|
|
|
case 8:
|
|
|
|
size = 1;
|
|
|
|
break;
|
|
|
|
case 16:
|
|
|
|
size = 2;
|
|
|
|
break;
|
|
|
|
case 32:
|
|
|
|
size = 4;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
return AE_ERROR;
|
|
|
|
}
|
|
|
|
|
2008-02-10 21:45:28 +07:00
|
|
|
result = raw_pci_write(pci_id->segment, pci_id->bus,
|
|
|
|
PCI_DEVFN(pci_id->device, pci_id->function),
|
|
|
|
reg, size, value);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
return (result ? AE_ERROR : AE_OK);
|
|
|
|
}
|
|
|
|
|
2006-11-22 21:55:48 +07:00
|
|
|
static void acpi_os_execute_deferred(struct work_struct *work)
|
ACPI: created a dedicated workqueue for notify() execution
HP nx6125/nx6325/... machines have a _GPE handler with an infinite
loop sending Notify() events to different ACPI subsystems.
Notify handler in ACPI driver is a C-routine, which may call ACPI
interpreter again to get access to some ACPI variables
(acpi_evaluate_xxx).
On these HP machines such an evaluation changes state of some variable
and lets the loop above break.
In the current ACPI implementation Notify requests are being deferred
to the same kacpid workqueue on which the above GPE handler with
infinite loop is executing. Thus we have a deadlock -- loop will
continue to spin, sending notify events, and at the same time
preventing these notify events from being run on a workqueue. All
notify events are deferred, thus we see increase in memory consumption
noticed by author of the thread. Also as GPE handling is bloked,
machines overheat. Eventually by external poll of the same
acpi_evaluate, kacpid is released and all the queued notify events are
free to run, thus 100% cpu utilization by kacpid for several seconds
or more.
To prevent all these horrors it's needed to not put notify events to
kacpid workqueue by either executing them immediately or putting them
on some other thread. It's dangerous to execute notify events in
place, as it will put several ACPI interpreter stacks on top of each
other (at least 4 in case of nx6125), thus causing kernel stack
overflow.
First attempt to create a new thread was done by Peter Wainwright
He created a bunch of threads, which were stealing work from a kacpid
workqueue.
This patch appeared in 2.6.15 kernel shipped with Ubuntu 6.06 LTS.
Second attempt was done by me, I created a new thread for each Notify
event. This worked OK on HP nx machines, but broke Linus' Compaq
n620c, by producing threads with a speed what they stopped the machine
completely. Thus this patch was reverted from 18-rc2 as I remember.
I re-made the patch to create second workqueue just for notify events,
thus hopping it will not break Linus' machine. Patch was tested on the
same HP nx machines in #5534 and #7122, but I did not received reply
from Linus on a test patch sent to him.
Patch went to 19-rc and was rejected with much fanfare again.
There was 4th patch, which inserted schedule_timeout(1) into deferred
execution of kacpid, if we had any notify requests pending, but Linus
decided that it was too complex (involved either changes to workqueue
to see if it's empty or atomic inc/dec).
Now you see last variant which adds yield() to every GPE execution.
http://bugzilla.kernel.org/show_bug.cgi?id=5534
http://bugzilla.kernel.org/show_bug.cgi?id=8385
Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2007-05-10 10:31:03 +07:00
|
|
|
{
|
|
|
|
struct acpi_os_dpc *dpc = container_of(work, struct acpi_os_dpc, work);
|
|
|
|
|
2008-08-28 09:05:06 +07:00
|
|
|
dpc->function(dpc->context);
|
|
|
|
kfree(dpc);
|
|
|
|
}
|
|
|
|
|
2006-05-05 14:23:00 +07:00
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_os_execute
|
|
|
|
*
|
|
|
|
* PARAMETERS: Type - Type of the callback
|
|
|
|
* Function - Function to be executed
|
|
|
|
* Context - Function parameters
|
|
|
|
*
|
|
|
|
* RETURN: Status
|
|
|
|
*
|
|
|
|
* DESCRIPTION: Depending on type, either queues function for deferred execution or
|
|
|
|
* immediately executes function on a separate thread.
|
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
acpi_status acpi_os_execute(acpi_execute_type type,
|
|
|
|
acpi_osd_exec_callback function, void *context)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status status = AE_OK;
|
|
|
|
struct acpi_os_dpc *dpc;
|
2007-11-13 17:05:45 +07:00
|
|
|
struct workqueue_struct *queue;
|
2008-08-28 09:05:06 +07:00
|
|
|
int ret;
|
2006-07-13 09:46:42 +07:00
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_EXEC,
|
|
|
|
"Scheduling function [%p(%p)] for deferred execution.\n",
|
|
|
|
function, context));
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Allocate/initialize DPC structure. Note that this memory will be
|
2006-11-22 21:55:48 +07:00
|
|
|
* freed by the callee. The kernel handles the work_struct list in a
|
2005-04-17 05:20:36 +07:00
|
|
|
* way that allows us to also free its memory inside the callee.
|
|
|
|
* Because we may want to schedule several tasks with different
|
|
|
|
* parameters we can't use the approach some kernel code uses of
|
2006-11-22 21:55:48 +07:00
|
|
|
* having a static work_struct.
|
2005-04-17 05:20:36 +07:00
|
|
|
*/
|
2006-07-13 09:46:42 +07:00
|
|
|
|
2012-11-02 19:09:08 +07:00
|
|
|
dpc = kzalloc(sizeof(struct acpi_os_dpc), GFP_ATOMIC);
|
2005-04-17 05:20:36 +07:00
|
|
|
if (!dpc)
|
2008-12-31 08:23:57 +07:00
|
|
|
return AE_NO_MEMORY;
|
2006-11-18 10:31:09 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
dpc->function = function;
|
|
|
|
dpc->context = context;
|
2006-11-18 10:31:09 +07:00
|
|
|
|
2009-06-23 09:20:29 +07:00
|
|
|
/*
|
2012-11-02 19:09:08 +07:00
|
|
|
* To prevent lockdep from complaining unnecessarily, make sure that
|
|
|
|
* there is a different static lockdep key for each workqueue by using
|
|
|
|
* INIT_WORK() for each of them separately.
|
2009-06-23 09:20:29 +07:00
|
|
|
*/
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
if (type == OSL_NOTIFY_HANDLER) {
|
2012-11-02 19:09:08 +07:00
|
|
|
queue = kacpi_notify_wq;
|
2010-03-22 14:48:54 +07:00
|
|
|
INIT_WORK(&dpc->work, acpi_os_execute_deferred);
|
2012-11-02 19:09:08 +07:00
|
|
|
} else {
|
|
|
|
queue = kacpid_wq;
|
2010-03-22 14:48:54 +07:00
|
|
|
INIT_WORK(&dpc->work, acpi_os_execute_deferred);
|
2012-11-02 19:09:08 +07:00
|
|
|
}
|
2010-03-22 14:48:54 +07:00
|
|
|
|
2010-06-29 15:07:09 +07:00
|
|
|
/*
|
|
|
|
* On some machines, a software-initiated SMI causes corruption unless
|
|
|
|
* the SMI runs on CPU 0. An SMI can be initiated by any AML, but
|
|
|
|
* typically it's done in GPE-related methods that are run via
|
|
|
|
* workqueues, so we can avoid the known corruption cases by always
|
|
|
|
* queueing on CPU 0.
|
|
|
|
*/
|
|
|
|
ret = queue_work_on(0, queue, &dpc->work);
|
2008-08-28 09:05:06 +07:00
|
|
|
|
|
|
|
if (!ret) {
|
2008-09-28 13:51:56 +07:00
|
|
|
printk(KERN_ERR PREFIX
|
|
|
|
"Call to queue_work() failed.\n");
|
2007-11-13 17:05:45 +07:00
|
|
|
status = AE_ERROR;
|
|
|
|
kfree(dpc);
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2008-12-31 08:23:57 +07:00
|
|
|
return status;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
EXPORT_SYMBOL(acpi_os_execute);
|
2005-08-05 11:44:28 +07:00
|
|
|
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
void acpi_os_wait_events_complete(void)
|
2008-08-28 09:05:06 +07:00
|
|
|
{
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
flush_workqueue(kacpid_wq);
|
|
|
|
flush_workqueue(kacpi_notify_wq);
|
2008-08-28 09:05:06 +07:00
|
|
|
}
|
2005-04-17 05:20:36 +07:00
|
|
|
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
struct acpi_hp_work {
|
|
|
|
struct work_struct work;
|
2014-03-03 06:40:38 +07:00
|
|
|
struct acpi_device *adev;
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
u32 src;
|
|
|
|
};
|
|
|
|
|
|
|
|
static void acpi_hotplug_work_fn(struct work_struct *work)
|
2008-08-28 09:05:06 +07:00
|
|
|
{
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
struct acpi_hp_work *hpw = container_of(work, struct acpi_hp_work, work);
|
|
|
|
|
|
|
|
acpi_os_wait_events_complete();
|
2014-03-03 06:40:38 +07:00
|
|
|
acpi_device_hotplug(hpw->adev, hpw->src);
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
kfree(hpw);
|
2008-08-28 09:05:06 +07:00
|
|
|
}
|
|
|
|
|
2014-03-03 06:40:38 +07:00
|
|
|
acpi_status acpi_hotplug_schedule(struct acpi_device *adev, u32 src)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
struct acpi_hp_work *hpw;
|
|
|
|
|
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_EXEC,
|
2014-03-03 06:40:38 +07:00
|
|
|
"Scheduling hotplug event (%p, %u) for deferred execution.\n",
|
|
|
|
adev, src));
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
|
|
|
|
hpw = kmalloc(sizeof(*hpw), GFP_KERNEL);
|
|
|
|
if (!hpw)
|
|
|
|
return AE_NO_MEMORY;
|
|
|
|
|
|
|
|
INIT_WORK(&hpw->work, acpi_hotplug_work_fn);
|
2014-03-03 06:40:38 +07:00
|
|
|
hpw->adev = adev;
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 07:45:40 +07:00
|
|
|
hpw->src = src;
|
|
|
|
/*
|
|
|
|
* We can't run hotplug code in kacpid_wq/kacpid_notify_wq etc., because
|
|
|
|
* the hotplug code may call driver .remove() functions, which may
|
|
|
|
* invoke flush_scheduled_work()/acpi_os_wait_events_complete() to flush
|
|
|
|
* these workqueues.
|
|
|
|
*/
|
|
|
|
if (!queue_work(kacpi_hotplug_wq, &hpw->work)) {
|
|
|
|
kfree(hpw);
|
|
|
|
return AE_ERROR;
|
|
|
|
}
|
|
|
|
return AE_OK;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2013-11-23 03:52:12 +07:00
|
|
|
bool acpi_queue_hotplug_work(struct work_struct *work)
|
|
|
|
{
|
|
|
|
return queue_work(kacpi_hotplug_wq, work);
|
|
|
|
}
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_create_semaphore(u32 max_units, u32 initial_units, acpi_handle * handle)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
struct semaphore *sem = NULL;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2014-03-20 14:35:56 +07:00
|
|
|
sem = acpi_os_allocate_zeroed(sizeof(struct semaphore));
|
2005-04-17 05:20:36 +07:00
|
|
|
if (!sem)
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_NO_MEMORY;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
sema_init(sem, initial_units);
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
*handle = (acpi_handle *) sem;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_MUTEX, "Creating semaphore[%p|%d].\n",
|
|
|
|
*handle, initial_units));
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_OK;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* TODO: A better way to delete semaphores? Linux doesn't have a
|
|
|
|
* 'delete_semaphore()' function -- may result in an invalid
|
|
|
|
* pointer dereference for non-synchronized consumers. Should
|
|
|
|
* we at least check for blocked threads and signal/cancel them?
|
|
|
|
*/
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_delete_semaphore(acpi_handle handle)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
struct semaphore *sem = (struct semaphore *)handle;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (!sem)
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_BAD_PARAMETER;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_MUTEX, "Deleting semaphore[%p].\n", handle));
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2008-03-15 00:43:13 +07:00
|
|
|
BUG_ON(!list_empty(&sem->wait_list));
|
2006-06-30 14:19:10 +07:00
|
|
|
kfree(sem);
|
2005-08-05 11:44:28 +07:00
|
|
|
sem = NULL;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_OK;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* TODO: Support for units > 1?
|
|
|
|
*/
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_wait_semaphore(acpi_handle handle, u32 units, u16 timeout)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status status = AE_OK;
|
|
|
|
struct semaphore *sem = (struct semaphore *)handle;
|
2008-03-15 00:43:13 +07:00
|
|
|
long jiffies;
|
2005-08-05 11:44:28 +07:00
|
|
|
int ret = 0;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (!sem || (units < 1))
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_BAD_PARAMETER;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (units > 1)
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_SUPPORT;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_MUTEX, "Waiting for semaphore[%p|%d|%d]\n",
|
|
|
|
handle, units, timeout));
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2008-03-15 00:43:13 +07:00
|
|
|
if (timeout == ACPI_WAIT_FOREVER)
|
|
|
|
jiffies = MAX_SCHEDULE_TIMEOUT;
|
|
|
|
else
|
|
|
|
jiffies = msecs_to_jiffies(timeout);
|
2013-12-05 02:59:11 +07:00
|
|
|
|
2008-03-15 00:43:13 +07:00
|
|
|
ret = down_timeout(sem, jiffies);
|
|
|
|
if (ret)
|
|
|
|
status = AE_TIME;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (ACPI_FAILURE(status)) {
|
2006-04-27 16:25:00 +07:00
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_MUTEX,
|
2006-06-27 10:58:43 +07:00
|
|
|
"Failed to acquire semaphore[%p|%d|%d], %s",
|
2005-08-05 11:44:28 +07:00
|
|
|
handle, units, timeout,
|
|
|
|
acpi_format_exception(status)));
|
|
|
|
} else {
|
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_MUTEX,
|
2006-06-27 10:58:43 +07:00
|
|
|
"Acquired semaphore[%p|%d|%d]", handle,
|
2005-08-05 11:44:28 +07:00
|
|
|
units, timeout));
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
2006-06-27 11:41:40 +07:00
|
|
|
return status;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* TODO: Support for units > 1?
|
|
|
|
*/
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_signal_semaphore(acpi_handle handle, u32 units)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
struct semaphore *sem = (struct semaphore *)handle;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (!sem || (units < 1))
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_BAD_PARAMETER;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (units > 1)
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_SUPPORT;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
ACPI_DEBUG_PRINT((ACPI_DB_MUTEX, "Signaling semaphore[%p|%d]\n", handle,
|
|
|
|
units));
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
up(sem);
|
|
|
|
|
2006-06-27 11:41:40 +07:00
|
|
|
return AE_OK;
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
#ifdef ACPI_FUTURE_USAGE
|
2005-08-05 11:44:28 +07:00
|
|
|
u32 acpi_os_get_line(char *buffer)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
|
|
|
|
#ifdef ENABLE_DEBUGGER
|
|
|
|
if (acpi_in_debugger) {
|
|
|
|
u32 chars;
|
|
|
|
|
|
|
|
kdb_read(buffer, sizeof(line_buf));
|
|
|
|
|
|
|
|
/* remove the CR kdb includes */
|
|
|
|
chars = strlen(buffer) - 1;
|
|
|
|
buffer[chars] = '\0';
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
#endif /* ACPI_FUTURE_USAGE */
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_signal(u32 function, void *info)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
switch (function) {
|
2005-04-17 05:20:36 +07:00
|
|
|
case ACPI_SIGNAL_FATAL:
|
|
|
|
printk(KERN_ERR PREFIX "Fatal opcode executed\n");
|
|
|
|
break;
|
|
|
|
case ACPI_SIGNAL_BREAKPOINT:
|
|
|
|
/*
|
|
|
|
* AML Breakpoint
|
|
|
|
* ACPI spec. says to treat it as a NOP unless
|
|
|
|
* you are debugging. So if/when we integrate
|
|
|
|
* AML debugger into the kernel debugger its
|
|
|
|
* hook will go here. But until then it is
|
|
|
|
* not useful to print anything on breakpoints.
|
|
|
|
*/
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
2005-08-05 11:44:28 +07:00
|
|
|
|
|
|
|
static int __init acpi_os_name_setup(char *str)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
|
|
|
char *p = acpi_os_name;
|
2005-08-05 11:44:28 +07:00
|
|
|
int count = ACPI_MAX_OVERRIDE_LEN - 1;
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
if (!str || !*str)
|
|
|
|
return 0;
|
|
|
|
|
2013-10-18 16:01:43 +07:00
|
|
|
for (; count-- && *str; str++) {
|
2005-04-17 05:20:36 +07:00
|
|
|
if (isalnum(*str) || *str == ' ' || *str == ':')
|
|
|
|
*p++ = *str;
|
|
|
|
else if (*str == '\'' || *str == '"')
|
|
|
|
continue;
|
|
|
|
else
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
*p = 0;
|
|
|
|
|
|
|
|
return 1;
|
2005-08-05 11:44:28 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
__setup("acpi_os_name=", acpi_os_name_setup);
|
|
|
|
|
2010-12-09 15:51:06 +07:00
|
|
|
#define OSI_STRING_LENGTH_MAX 64 /* arbitrary */
|
|
|
|
#define OSI_STRING_ENTRIES_MAX 16 /* arbitrary */
|
|
|
|
|
|
|
|
struct osi_setup_entry {
|
|
|
|
char string[OSI_STRING_LENGTH_MAX];
|
|
|
|
bool enable;
|
|
|
|
};
|
|
|
|
|
2013-08-13 17:31:15 +07:00
|
|
|
static struct osi_setup_entry
|
|
|
|
osi_setup_entries[OSI_STRING_ENTRIES_MAX] __initdata = {
|
2011-07-29 03:48:43 +07:00
|
|
|
{"Module Device", true},
|
|
|
|
{"Processor Device", true},
|
|
|
|
{"3.0 _SCP Extensions", true},
|
|
|
|
{"Processor Aggregator Device", true},
|
|
|
|
};
|
2010-12-09 15:51:06 +07:00
|
|
|
|
2010-12-09 15:50:52 +07:00
|
|
|
void __init acpi_osi_setup(char *str)
|
|
|
|
{
|
2010-12-09 15:51:06 +07:00
|
|
|
struct osi_setup_entry *osi;
|
|
|
|
bool enable = true;
|
|
|
|
int i;
|
|
|
|
|
2010-12-09 15:50:52 +07:00
|
|
|
if (!acpi_gbl_create_osi_method)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (str == NULL || *str == '\0') {
|
|
|
|
printk(KERN_INFO PREFIX "_OSI method disabled\n");
|
|
|
|
acpi_gbl_create_osi_method = FALSE;
|
2010-12-09 15:51:06 +07:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (*str == '!') {
|
|
|
|
str++;
|
2013-07-22 15:08:25 +07:00
|
|
|
if (*str == '\0') {
|
|
|
|
osi_linux.default_disabling = 1;
|
|
|
|
return;
|
2013-07-22 15:08:36 +07:00
|
|
|
} else if (*str == '*') {
|
|
|
|
acpi_update_interfaces(ACPI_DISABLE_ALL_STRINGS);
|
|
|
|
for (i = 0; i < OSI_STRING_ENTRIES_MAX; i++) {
|
|
|
|
osi = &osi_setup_entries[i];
|
|
|
|
osi->enable = false;
|
|
|
|
}
|
|
|
|
return;
|
2013-07-22 15:08:25 +07:00
|
|
|
}
|
2010-12-09 15:51:06 +07:00
|
|
|
enable = false;
|
|
|
|
}
|
|
|
|
|
|
|
|
for (i = 0; i < OSI_STRING_ENTRIES_MAX; i++) {
|
|
|
|
osi = &osi_setup_entries[i];
|
|
|
|
if (!strcmp(osi->string, str)) {
|
|
|
|
osi->enable = enable;
|
|
|
|
break;
|
|
|
|
} else if (osi->string[0] == '\0') {
|
|
|
|
osi->enable = enable;
|
|
|
|
strncpy(osi->string, str, OSI_STRING_LENGTH_MAX);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
2010-12-09 15:50:52 +07:00
|
|
|
}
|
|
|
|
|
2008-01-24 08:50:56 +07:00
|
|
|
static void __init set_osi_linux(unsigned int enable)
|
|
|
|
{
|
2010-12-09 15:50:52 +07:00
|
|
|
if (osi_linux.enable != enable)
|
2008-01-24 08:50:56 +07:00
|
|
|
osi_linux.enable = enable;
|
2010-08-06 08:35:51 +07:00
|
|
|
|
|
|
|
if (osi_linux.enable)
|
|
|
|
acpi_osi_setup("Linux");
|
|
|
|
else
|
|
|
|
acpi_osi_setup("!Linux");
|
|
|
|
|
2008-01-24 08:50:56 +07:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void __init acpi_cmdline_osi_linux(unsigned int enable)
|
|
|
|
{
|
2010-12-09 15:50:52 +07:00
|
|
|
osi_linux.cmdline = 1; /* cmdline set the default and override DMI */
|
|
|
|
osi_linux.dmi = 0;
|
2008-01-24 08:50:56 +07:00
|
|
|
set_osi_linux(enable);
|
|
|
|
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
void __init acpi_dmi_osi_linux(int enable, const struct dmi_system_id *d)
|
|
|
|
{
|
|
|
|
printk(KERN_NOTICE PREFIX "DMI detected: %s\n", d->ident);
|
|
|
|
|
|
|
|
if (enable == -1)
|
|
|
|
return;
|
|
|
|
|
2010-12-09 15:50:52 +07:00
|
|
|
osi_linux.dmi = 1; /* DMI knows that this box asks OSI(Linux) */
|
2008-01-24 08:50:56 +07:00
|
|
|
set_osi_linux(enable);
|
2007-05-30 11:10:38 +07:00
|
|
|
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
/*
|
2007-05-30 05:43:33 +07:00
|
|
|
* Modify the list of "OS Interfaces" reported to BIOS via _OSI
|
|
|
|
*
|
2005-04-17 05:20:36 +07:00
|
|
|
* empty string disables _OSI
|
2007-05-30 05:43:33 +07:00
|
|
|
* string starting with '!' disables that string
|
|
|
|
* otherwise string is added to list, augmenting built-in strings
|
2005-04-17 05:20:36 +07:00
|
|
|
*/
|
2010-08-06 08:35:51 +07:00
|
|
|
static void __init acpi_osi_setup_late(void)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2010-12-09 15:51:06 +07:00
|
|
|
struct osi_setup_entry *osi;
|
|
|
|
char *str;
|
|
|
|
int i;
|
2010-12-09 15:50:52 +07:00
|
|
|
acpi_status status;
|
2010-08-06 08:35:51 +07:00
|
|
|
|
2013-07-22 15:08:25 +07:00
|
|
|
if (osi_linux.default_disabling) {
|
|
|
|
status = acpi_update_interfaces(ACPI_DISABLE_ALL_VENDOR_STRINGS);
|
|
|
|
|
|
|
|
if (ACPI_SUCCESS(status))
|
|
|
|
printk(KERN_INFO PREFIX "Disabled all _OSI OS vendors\n");
|
|
|
|
}
|
|
|
|
|
2010-12-09 15:51:06 +07:00
|
|
|
for (i = 0; i < OSI_STRING_ENTRIES_MAX; i++) {
|
|
|
|
osi = &osi_setup_entries[i];
|
|
|
|
str = osi->string;
|
2010-08-06 08:35:51 +07:00
|
|
|
|
2010-12-09 15:51:06 +07:00
|
|
|
if (*str == '\0')
|
|
|
|
break;
|
|
|
|
if (osi->enable) {
|
|
|
|
status = acpi_install_interface(str);
|
2010-12-09 15:50:52 +07:00
|
|
|
|
2010-12-09 15:51:06 +07:00
|
|
|
if (ACPI_SUCCESS(status))
|
|
|
|
printk(KERN_INFO PREFIX "Added _OSI(%s)\n", str);
|
|
|
|
} else {
|
|
|
|
status = acpi_remove_interface(str);
|
2010-12-09 15:50:52 +07:00
|
|
|
|
2010-12-09 15:51:06 +07:00
|
|
|
if (ACPI_SUCCESS(status))
|
|
|
|
printk(KERN_INFO PREFIX "Deleted _OSI(%s)\n", str);
|
|
|
|
}
|
2010-08-06 08:35:51 +07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2010-12-09 15:50:52 +07:00
|
|
|
static int __init osi_setup(char *str)
|
2010-08-06 08:35:51 +07:00
|
|
|
{
|
2010-12-09 15:50:52 +07:00
|
|
|
if (str && !strcmp("Linux", str))
|
|
|
|
acpi_cmdline_osi_linux(1);
|
|
|
|
else if (str && !strcmp("!Linux", str))
|
|
|
|
acpi_cmdline_osi_linux(0);
|
|
|
|
else
|
|
|
|
acpi_osi_setup(str);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2010-12-09 15:50:52 +07:00
|
|
|
__setup("acpi_osi=", osi_setup);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2014-03-24 13:49:00 +07:00
|
|
|
/*
|
2014-03-24 13:49:22 +07:00
|
|
|
* Disable the auto-serialization of named objects creation methods.
|
2014-03-24 13:49:00 +07:00
|
|
|
*
|
2014-03-24 13:49:22 +07:00
|
|
|
* This feature is enabled by default. It marks the AML control methods
|
2014-03-24 13:49:00 +07:00
|
|
|
* that contain the opcodes to create named objects as "Serialized".
|
|
|
|
*/
|
2014-03-24 13:49:22 +07:00
|
|
|
static int __init acpi_no_auto_serialize_setup(char *str)
|
2005-04-17 05:20:36 +07:00
|
|
|
{
|
2014-03-24 13:49:22 +07:00
|
|
|
acpi_gbl_auto_serialize_methods = FALSE;
|
|
|
|
pr_info("ACPI: auto-serialization disabled\n");
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2014-03-24 13:49:22 +07:00
|
|
|
__setup("acpi_no_auto_serialize", acpi_no_auto_serialize_setup);
|
2005-04-17 05:20:36 +07:00
|
|
|
|
2008-02-05 14:31:22 +07:00
|
|
|
/* Check of resource interference between native drivers and ACPI
|
|
|
|
* OperationRegions (SystemIO and System Memory only).
|
|
|
|
* IO ports and memory declared in ACPI might be used by the ACPI subsystem
|
|
|
|
* in arbitrary AML code and can interfere with legacy drivers.
|
|
|
|
* acpi_enforce_resources= can be set to:
|
|
|
|
*
|
2009-03-30 05:01:27 +07:00
|
|
|
* - strict (default) (2)
|
2008-02-05 14:31:22 +07:00
|
|
|
* -> further driver trying to access the resources will not load
|
2009-03-30 05:01:27 +07:00
|
|
|
* - lax (1)
|
2008-02-05 14:31:22 +07:00
|
|
|
* -> further driver trying to access the resources will load, but you
|
|
|
|
* get a system message that something might go wrong...
|
|
|
|
*
|
|
|
|
* - no (0)
|
|
|
|
* -> ACPI Operation Region resources will not be registered
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
#define ENFORCE_RESOURCES_STRICT 2
|
|
|
|
#define ENFORCE_RESOURCES_LAX 1
|
|
|
|
#define ENFORCE_RESOURCES_NO 0
|
|
|
|
|
2009-03-30 05:01:27 +07:00
|
|
|
static unsigned int acpi_enforce_resources = ENFORCE_RESOURCES_STRICT;
|
2008-02-05 14:31:22 +07:00
|
|
|
|
|
|
|
static int __init acpi_enforce_resources_setup(char *str)
|
|
|
|
{
|
|
|
|
if (str == NULL || *str == '\0')
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (!strcmp("strict", str))
|
|
|
|
acpi_enforce_resources = ENFORCE_RESOURCES_STRICT;
|
|
|
|
else if (!strcmp("lax", str))
|
|
|
|
acpi_enforce_resources = ENFORCE_RESOURCES_LAX;
|
|
|
|
else if (!strcmp("no", str))
|
|
|
|
acpi_enforce_resources = ENFORCE_RESOURCES_NO;
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
__setup("acpi_enforce_resources=", acpi_enforce_resources_setup);
|
|
|
|
|
|
|
|
/* Check for resource conflicts between ACPI OperationRegions and native
|
|
|
|
* drivers */
|
2009-11-11 21:22:15 +07:00
|
|
|
int acpi_check_resource_conflict(const struct resource *res)
|
2008-02-05 14:31:22 +07:00
|
|
|
{
|
2012-01-12 12:10:32 +07:00
|
|
|
acpi_adr_space_type space_id;
|
|
|
|
acpi_size length;
|
|
|
|
u8 warn = 0;
|
|
|
|
int clash = 0;
|
2008-02-05 14:31:22 +07:00
|
|
|
|
|
|
|
if (acpi_enforce_resources == ENFORCE_RESOURCES_NO)
|
|
|
|
return 0;
|
|
|
|
if (!(res->flags & IORESOURCE_IO) && !(res->flags & IORESOURCE_MEM))
|
|
|
|
return 0;
|
|
|
|
|
2012-01-12 12:10:32 +07:00
|
|
|
if (res->flags & IORESOURCE_IO)
|
|
|
|
space_id = ACPI_ADR_SPACE_SYSTEM_IO;
|
|
|
|
else
|
|
|
|
space_id = ACPI_ADR_SPACE_SYSTEM_MEMORY;
|
2008-02-05 14:31:22 +07:00
|
|
|
|
2013-03-12 15:53:02 +07:00
|
|
|
length = resource_size(res);
|
2012-01-12 12:10:32 +07:00
|
|
|
if (acpi_enforce_resources != ENFORCE_RESOURCES_NO)
|
|
|
|
warn = 1;
|
|
|
|
clash = acpi_check_address_range(space_id, res->start, length, warn);
|
2008-02-05 14:31:22 +07:00
|
|
|
|
|
|
|
if (clash) {
|
|
|
|
if (acpi_enforce_resources != ENFORCE_RESOURCES_NO) {
|
2009-09-08 20:31:46 +07:00
|
|
|
if (acpi_enforce_resources == ENFORCE_RESOURCES_LAX)
|
|
|
|
printk(KERN_NOTICE "ACPI: This conflict may"
|
|
|
|
" cause random problems and system"
|
|
|
|
" instability\n");
|
|
|
|
printk(KERN_INFO "ACPI: If an ACPI driver is available"
|
|
|
|
" for this device, you should use it instead of"
|
|
|
|
" the native driver\n");
|
2008-02-05 14:31:22 +07:00
|
|
|
}
|
|
|
|
if (acpi_enforce_resources == ENFORCE_RESOURCES_STRICT)
|
|
|
|
return -EBUSY;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
2008-02-05 14:31:23 +07:00
|
|
|
EXPORT_SYMBOL(acpi_check_resource_conflict);
|
2008-02-05 14:31:22 +07:00
|
|
|
|
|
|
|
int acpi_check_region(resource_size_t start, resource_size_t n,
|
|
|
|
const char *name)
|
|
|
|
{
|
|
|
|
struct resource res = {
|
|
|
|
.start = start,
|
|
|
|
.end = start + n - 1,
|
|
|
|
.name = name,
|
|
|
|
.flags = IORESOURCE_IO,
|
|
|
|
};
|
|
|
|
|
|
|
|
return acpi_check_resource_conflict(&res);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_check_region);
|
|
|
|
|
2010-05-28 00:58:37 +07:00
|
|
|
/*
|
|
|
|
* Let drivers know whether the resource checks are effective
|
|
|
|
*/
|
|
|
|
int acpi_resources_are_enforced(void)
|
|
|
|
{
|
|
|
|
return acpi_enforce_resources == ENFORCE_RESOURCES_STRICT;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(acpi_resources_are_enforced);
|
|
|
|
|
2011-03-23 16:26:34 +07:00
|
|
|
/*
|
|
|
|
* Deallocate the memory for a spinlock.
|
|
|
|
*/
|
|
|
|
void acpi_os_delete_lock(acpi_spinlock handle)
|
|
|
|
{
|
|
|
|
ACPI_FREE(handle);
|
|
|
|
}
|
|
|
|
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
/*
|
|
|
|
* Acquire a spinlock.
|
|
|
|
*
|
|
|
|
* handle is a pointer to the spinlock_t.
|
|
|
|
*/
|
|
|
|
|
2006-06-24 04:04:00 +07:00
|
|
|
acpi_cpu_flags acpi_os_acquire_lock(acpi_spinlock lockp)
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
{
|
2006-01-28 04:43:00 +07:00
|
|
|
acpi_cpu_flags flags;
|
2006-06-24 04:04:00 +07:00
|
|
|
spin_lock_irqsave(lockp, flags);
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
return flags;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Release a spinlock. See above.
|
|
|
|
*/
|
|
|
|
|
2006-06-24 04:04:00 +07:00
|
|
|
void acpi_os_release_lock(acpi_spinlock lockp, acpi_cpu_flags flags)
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
{
|
2006-06-24 04:04:00 +07:00
|
|
|
spin_unlock_irqrestore(lockp, flags);
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
#ifndef ACPI_USE_LOCAL_CACHE
|
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_os_create_cache
|
|
|
|
*
|
ACPI: ACPICA 20060421
Removed a device initialization optimization introduced in
20051216 where the _STA method was not run unless an _INI
was also present for the same device. This optimization
could cause problems because it could allow _INI methods
to be run within a not-present device subtree (If a
not-present device had no _INI, _STA would not be run,
the not-present status would not be discovered, and the
children of the device would be incorrectly traversed.)
Implemented a new _STA optimization where namespace
subtrees that do not contain _INI are identified and
ignored during device initialization. Selectively running
_STA can significantly improve boot time on large machines
(with assistance from Len Brown.)
Implemented support for the device initialization case
where the returned _STA flags indicate a device not-present
but functioning. In this case, _INI is not run, but the
device children are examined for presence, as per the
ACPI specification.
Implemented an additional change to the IndexField support
in order to conform to MS behavior. The value written to
the Index Register is not simply a byte offset, it is a
byte offset in units of the access width of the parent
Index Field. (Fiodor Suietov)
Defined and deployed a new OSL interface,
acpi_os_validate_address(). This interface is called during
the creation of all AML operation regions, and allows
the host OS to exert control over what addresses it will
allow the AML code to access. Operation Regions whose
addresses are disallowed will cause a runtime exception
when they are actually accessed (will not affect or abort
table loading.)
Defined and deployed a new OSL interface,
acpi_os_validate_interface(). This interface allows the host OS
to match the various "optional" interface/behavior strings
for the _OSI predefined control method as appropriate
(with assistance from Bjorn Helgaas.)
Restructured and corrected various problems in the
exception handling code paths within DsCallControlMethod
and DsTerminateControlMethod in dsmethod (with assistance
from Takayoshi Kochi.)
Modified the Linux source converter to ignore quoted string
literals while converting identifiers from mixed to lower
case. This will correct problems with the disassembler
and other areas where such strings must not be modified.
The ACPI_FUNCTION_* macros no longer require quotes around
the function name. This allows the Linux source converter
to convert the names, now that the converter ignores
quoted strings.
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2006-04-22 04:15:00 +07:00
|
|
|
* PARAMETERS: name - Ascii name for the cache
|
|
|
|
* size - Size of each cached object
|
|
|
|
* depth - Maximum depth of the cache (in objects) <ignored>
|
|
|
|
* cache - Where the new cache object is returned
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
*
|
ACPI: ACPICA 20060421
Removed a device initialization optimization introduced in
20051216 where the _STA method was not run unless an _INI
was also present for the same device. This optimization
could cause problems because it could allow _INI methods
to be run within a not-present device subtree (If a
not-present device had no _INI, _STA would not be run,
the not-present status would not be discovered, and the
children of the device would be incorrectly traversed.)
Implemented a new _STA optimization where namespace
subtrees that do not contain _INI are identified and
ignored during device initialization. Selectively running
_STA can significantly improve boot time on large machines
(with assistance from Len Brown.)
Implemented support for the device initialization case
where the returned _STA flags indicate a device not-present
but functioning. In this case, _INI is not run, but the
device children are examined for presence, as per the
ACPI specification.
Implemented an additional change to the IndexField support
in order to conform to MS behavior. The value written to
the Index Register is not simply a byte offset, it is a
byte offset in units of the access width of the parent
Index Field. (Fiodor Suietov)
Defined and deployed a new OSL interface,
acpi_os_validate_address(). This interface is called during
the creation of all AML operation regions, and allows
the host OS to exert control over what addresses it will
allow the AML code to access. Operation Regions whose
addresses are disallowed will cause a runtime exception
when they are actually accessed (will not affect or abort
table loading.)
Defined and deployed a new OSL interface,
acpi_os_validate_interface(). This interface allows the host OS
to match the various "optional" interface/behavior strings
for the _OSI predefined control method as appropriate
(with assistance from Bjorn Helgaas.)
Restructured and corrected various problems in the
exception handling code paths within DsCallControlMethod
and DsTerminateControlMethod in dsmethod (with assistance
from Takayoshi Kochi.)
Modified the Linux source converter to ignore quoted string
literals while converting identifiers from mixed to lower
case. This will correct problems with the disassembler
and other areas where such strings must not be modified.
The ACPI_FUNCTION_* macros no longer require quotes around
the function name. This allows the Linux source converter
to convert the names, now that the converter ignores
quoted strings.
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2006-04-22 04:15:00 +07:00
|
|
|
* RETURN: status
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
*
|
|
|
|
* DESCRIPTION: Create a cache object
|
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
|
|
|
acpi_status
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_os_create_cache(char *name, u16 size, u16 depth, acpi_cache_t ** cache)
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
{
|
2007-07-20 08:11:58 +07:00
|
|
|
*cache = kmem_cache_create(name, size, 0, 0, NULL);
|
2006-12-20 03:56:13 +07:00
|
|
|
if (*cache == NULL)
|
ACPI: ACPICA 20060421
Removed a device initialization optimization introduced in
20051216 where the _STA method was not run unless an _INI
was also present for the same device. This optimization
could cause problems because it could allow _INI methods
to be run within a not-present device subtree (If a
not-present device had no _INI, _STA would not be run,
the not-present status would not be discovered, and the
children of the device would be incorrectly traversed.)
Implemented a new _STA optimization where namespace
subtrees that do not contain _INI are identified and
ignored during device initialization. Selectively running
_STA can significantly improve boot time on large machines
(with assistance from Len Brown.)
Implemented support for the device initialization case
where the returned _STA flags indicate a device not-present
but functioning. In this case, _INI is not run, but the
device children are examined for presence, as per the
ACPI specification.
Implemented an additional change to the IndexField support
in order to conform to MS behavior. The value written to
the Index Register is not simply a byte offset, it is a
byte offset in units of the access width of the parent
Index Field. (Fiodor Suietov)
Defined and deployed a new OSL interface,
acpi_os_validate_address(). This interface is called during
the creation of all AML operation regions, and allows
the host OS to exert control over what addresses it will
allow the AML code to access. Operation Regions whose
addresses are disallowed will cause a runtime exception
when they are actually accessed (will not affect or abort
table loading.)
Defined and deployed a new OSL interface,
acpi_os_validate_interface(). This interface allows the host OS
to match the various "optional" interface/behavior strings
for the _OSI predefined control method as appropriate
(with assistance from Bjorn Helgaas.)
Restructured and corrected various problems in the
exception handling code paths within DsCallControlMethod
and DsTerminateControlMethod in dsmethod (with assistance
from Takayoshi Kochi.)
Modified the Linux source converter to ignore quoted string
literals while converting identifiers from mixed to lower
case. This will correct problems with the disassembler
and other areas where such strings must not be modified.
The ACPI_FUNCTION_* macros no longer require quotes around
the function name. This allows the Linux source converter
to convert the names, now that the converter ignores
quoted strings.
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2006-04-22 04:15:00 +07:00
|
|
|
return AE_ERROR;
|
|
|
|
else
|
|
|
|
return AE_OK;
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_os_purge_cache
|
|
|
|
*
|
|
|
|
* PARAMETERS: Cache - Handle to cache object
|
|
|
|
*
|
|
|
|
* RETURN: Status
|
|
|
|
*
|
|
|
|
* DESCRIPTION: Free all objects within the requested cache.
|
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_purge_cache(acpi_cache_t * cache)
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
{
|
2006-10-01 05:28:50 +07:00
|
|
|
kmem_cache_shrink(cache);
|
2005-08-05 11:44:28 +07:00
|
|
|
return (AE_OK);
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_os_delete_cache
|
|
|
|
*
|
|
|
|
* PARAMETERS: Cache - Handle to cache object
|
|
|
|
*
|
|
|
|
* RETURN: Status
|
|
|
|
*
|
|
|
|
* DESCRIPTION: Free all objects within the requested cache and delete the
|
|
|
|
* cache object.
|
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_delete_cache(acpi_cache_t * cache)
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
{
|
2006-09-27 15:49:40 +07:00
|
|
|
kmem_cache_destroy(cache);
|
2005-08-05 11:44:28 +07:00
|
|
|
return (AE_OK);
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_os_release_object
|
|
|
|
*
|
|
|
|
* PARAMETERS: Cache - Handle to cache object
|
|
|
|
* Object - The object to be released
|
|
|
|
*
|
|
|
|
* RETURN: None
|
|
|
|
*
|
|
|
|
* DESCRIPTION: Release an object to the specified cache. If cache is full,
|
|
|
|
* the object is deleted.
|
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
2005-08-05 11:44:28 +07:00
|
|
|
acpi_status acpi_os_release_object(acpi_cache_t * cache, void *object)
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
{
|
2005-08-05 11:44:28 +07:00
|
|
|
kmem_cache_free(cache, object);
|
|
|
|
return (AE_OK);
|
ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com>
ACPICA 20050617:
Moved the object cache operations into the OS interface
layer (OSL) to allow the host OS to handle these operations
if desired (for example, the Linux OSL will invoke the
slab allocator). This support is optional; the compile
time define ACPI_USE_LOCAL_CACHE may be used to utilize
the original cache code in the ACPI CA core. The new OSL
interfaces are shown below. See utalloc.c for an example
implementation, and acpiosxf.h for the exact interface
definitions. Thanks to Alexey Starikovskiy.
acpi_os_create_cache
acpi_os_delete_cache
acpi_os_purge_cache
acpi_os_acquire_object
acpi_os_release_object
Modified the interfaces to acpi_os_acquire_lock and
acpi_os_release_lock to return and restore a flags
parameter. This fits better with many OS lock models.
Note: the current execution state (interrupt handler
or not) is no longer passed to these interfaces. If
necessary, the OSL must determine this state by itself, a
simple and fast operation. Thanks to Alexey Starikovskiy.
Fixed a problem in the ACPI table handling where a valid
XSDT was assumed present if the revision of the RSDP
was 2 or greater. According to the ACPI specification,
the XSDT is optional in all cases, and the table manager
therefore now checks for both an RSDP >=2 and a valid
XSDT pointer. Otherwise, the RSDT pointer is used.
Some ACPI 2.0 compliant BIOSs contain only the RSDT.
Fixed an interpreter problem with the Mid() operator in the
case of an input string where the resulting output string
is of zero length. It now correctly returns a valid,
null terminated string object instead of a string object
with a null pointer.
Fixed a problem with the control method argument handling
to allow a store to an Arg object that already contains an
object of type Device. The Device object is now correctly
overwritten. Previously, an error was returned.
ACPICA 20050624:
Modified the new OSL cache interfaces to use ACPI_CACHE_T
as the type for the host-defined cache object. This allows
the OSL implementation to define and type this object in
any manner desired, simplifying the OSL implementation.
For example, ACPI_CACHE_T is defined as kmem_cache_t for
Linux, and should be defined in the OS-specific header
file for other operating systems as required.
Changed the interface to AcpiOsAcquireObject to directly
return the requested object as the function return (instead
of ACPI_STATUS.) This change was made for performance
reasons, since this is the purpose of the interface in the
first place. acpi_os_acquire_object is now similar to the
acpi_os_allocate interface. Thanks to Alexey Starikovskiy.
Modified the initialization sequence in
acpi_initialize_subsystem to call the OSL interface
acpi_osl_initialize first, before any local initialization.
This change was required because the global initialization
now calls OSL interfaces.
Restructured the code base to split some files because
of size and/or because the code logically belonged in a
separate file. New files are listed below.
utilities/utcache.c /* Local cache interfaces */
utilities/utmutex.c /* Local mutex support */
utilities/utstate.c /* State object support */
parser/psloop.c /* Main AML parse loop */
Signed-off-by: Len Brown <len.brown@intel.com>
2005-06-24 11:00:00 +07:00
|
|
|
}
|
|
|
|
#endif
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
|
2014-04-04 11:39:11 +07:00
|
|
|
static int __init acpi_no_static_ssdt_setup(char *s)
|
2013-06-08 07:58:48 +07:00
|
|
|
{
|
2014-04-04 11:39:11 +07:00
|
|
|
acpi_gbl_disable_ssdt_table_install = TRUE;
|
|
|
|
pr_info("ACPI: static SSDT installation disabled\n");
|
2013-06-08 07:58:48 +07:00
|
|
|
|
2014-04-04 11:39:11 +07:00
|
|
|
return 0;
|
2013-06-08 07:58:48 +07:00
|
|
|
}
|
|
|
|
|
2014-04-04 11:39:11 +07:00
|
|
|
early_param("acpi_no_static_ssdt", acpi_no_static_ssdt_setup);
|
2013-06-08 07:58:48 +07:00
|
|
|
|
2014-02-11 10:01:52 +07:00
|
|
|
static int __init acpi_disable_return_repair(char *s)
|
|
|
|
{
|
|
|
|
printk(KERN_NOTICE PREFIX
|
|
|
|
"ACPI: Predefined validation mechanism disabled\n");
|
|
|
|
acpi_gbl_disable_auto_repair = TRUE;
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
__setup("acpica_no_return_repair", acpi_disable_return_repair);
|
|
|
|
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
acpi_status __init acpi_os_initialize(void)
|
|
|
|
{
|
|
|
|
acpi_os_map_generic_address(&acpi_gbl_FADT.xpm1a_event_block);
|
|
|
|
acpi_os_map_generic_address(&acpi_gbl_FADT.xpm1b_event_block);
|
|
|
|
acpi_os_map_generic_address(&acpi_gbl_FADT.xgpe0_block);
|
|
|
|
acpi_os_map_generic_address(&acpi_gbl_FADT.xgpe1_block);
|
2014-06-04 22:55:59 +07:00
|
|
|
if (acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER) {
|
|
|
|
/*
|
|
|
|
* Use acpi_os_map_generic_address to pre-map the reset
|
|
|
|
* register if it's in system memory.
|
|
|
|
*/
|
|
|
|
int rv;
|
|
|
|
|
|
|
|
rv = acpi_os_map_generic_address(&acpi_gbl_FADT.reset_register);
|
|
|
|
pr_debug(PREFIX "%s: map reset_reg status %d\n", __func__, rv);
|
|
|
|
}
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
2010-12-08 09:40:36 +07:00
|
|
|
acpi_status __init acpi_os_initialize1(void)
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
{
|
2011-02-01 17:42:42 +07:00
|
|
|
kacpid_wq = alloc_workqueue("kacpid", 0, 1);
|
|
|
|
kacpi_notify_wq = alloc_workqueue("kacpi_notify", 0, 1);
|
2013-11-23 03:52:12 +07:00
|
|
|
kacpi_hotplug_wq = alloc_ordered_workqueue("kacpi_hotplug", 0);
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
BUG_ON(!kacpid_wq);
|
|
|
|
BUG_ON(!kacpi_notify_wq);
|
|
|
|
BUG_ON(!kacpi_hotplug_wq);
|
2010-10-27 01:50:56 +07:00
|
|
|
acpi_install_interface_handler(acpi_osi_handler);
|
|
|
|
acpi_osi_setup_late();
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
acpi_status acpi_os_terminate(void)
|
|
|
|
{
|
|
|
|
if (acpi_irq_handler) {
|
2011-02-09 05:48:16 +07:00
|
|
|
acpi_os_remove_interrupt_handler(acpi_gbl_FADT.sci_interrupt,
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
acpi_irq_handler);
|
|
|
|
}
|
|
|
|
|
|
|
|
acpi_os_unmap_generic_address(&acpi_gbl_FADT.xgpe1_block);
|
|
|
|
acpi_os_unmap_generic_address(&acpi_gbl_FADT.xgpe0_block);
|
|
|
|
acpi_os_unmap_generic_address(&acpi_gbl_FADT.xpm1b_event_block);
|
|
|
|
acpi_os_unmap_generic_address(&acpi_gbl_FADT.xpm1a_event_block);
|
2014-06-04 22:55:59 +07:00
|
|
|
if (acpi_gbl_FADT.flags & ACPI_FADT_RESET_REGISTER)
|
|
|
|
acpi_os_unmap_generic_address(&acpi_gbl_FADT.reset_register);
|
ACPI: Pre-map 'system event' related register blocks
During ACPI initialization, pre-map fixed hardware registers that are
accessed during ACPI's 'system event' related IRQ handing.
ACPI's 'system event' handing accesses specific fixed hardware
registers; namely PM1a event, PM1b event, GPE0, and GPE1 register
blocks which are declared within the FADT. If these registers are
backed by MMIO, as opposed to I/O port space, accessing them within
interrupt context will cause a panic as acpi_os_read_memory()
depends on ioremap() in such cases - BZ 18012.
By utilizing the functionality provided in the previous two patches -
ACPI: Maintain a list of ACPI memory mapped I/O remappings, and, ACPI:
Add interfaces for ioremapping/iounmapping ACPI registers - accesses
to ACPI MMIO areas will now be safe from within interrupt contexts (IRQ
and/or NMI) provided the area was pre-mapped. This solves BZ 18012.
ACPI "System Event" reference(s):
ACPI Specification, Revision 4.0, Section 3 "ACPI Overview",
3.8 "System Events", 5.6 "ACPI Event Programming Model".
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=18012
Reported-by: <bjorn.helgaas@hp.com>
Signed-off-by: Myron Stowe <myron.stowe@hp.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-10-22 03:24:04 +07:00
|
|
|
|
|
|
|
destroy_workqueue(kacpid_wq);
|
|
|
|
destroy_workqueue(kacpi_notify_wq);
|
|
|
|
destroy_workqueue(kacpi_hotplug_wq);
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
2011-12-09 09:05:54 +07:00
|
|
|
|
|
|
|
acpi_status acpi_os_prepare_sleep(u8 sleep_state, u32 pm1a_control,
|
|
|
|
u32 pm1b_control)
|
|
|
|
{
|
|
|
|
int rc = 0;
|
|
|
|
if (__acpi_os_prepare_sleep)
|
|
|
|
rc = __acpi_os_prepare_sleep(sleep_state,
|
|
|
|
pm1a_control, pm1b_control);
|
|
|
|
if (rc < 0)
|
|
|
|
return AE_ERROR;
|
|
|
|
else if (rc > 0)
|
|
|
|
return AE_CTRL_SKIP;
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
void acpi_os_set_prepare_sleep(int (*func)(u8 sleep_state,
|
|
|
|
u32 pm1a_ctrl, u32 pm1b_ctrl))
|
|
|
|
{
|
|
|
|
__acpi_os_prepare_sleep = func;
|
|
|
|
}
|
2013-01-22 04:20:47 +07:00
|
|
|
|
2013-07-30 19:24:52 +07:00
|
|
|
acpi_status acpi_os_prepare_extended_sleep(u8 sleep_state, u32 val_a,
|
|
|
|
u32 val_b)
|
|
|
|
{
|
|
|
|
int rc = 0;
|
|
|
|
if (__acpi_os_prepare_extended_sleep)
|
|
|
|
rc = __acpi_os_prepare_extended_sleep(sleep_state,
|
|
|
|
val_a, val_b);
|
|
|
|
if (rc < 0)
|
|
|
|
return AE_ERROR;
|
|
|
|
else if (rc > 0)
|
|
|
|
return AE_CTRL_SKIP;
|
|
|
|
|
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
void acpi_os_set_prepare_extended_sleep(int (*func)(u8 sleep_state,
|
|
|
|
u32 val_a, u32 val_b))
|
|
|
|
{
|
|
|
|
__acpi_os_prepare_extended_sleep = func;
|
|
|
|
}
|