2007-02-02 17:48:20 +01:00
|
|
|
/******************************************************************************
|
|
|
|
*
|
|
|
|
* Module Name: tbfadt - FADT table utilities
|
|
|
|
*
|
|
|
|
*****************************************************************************/
|
|
|
|
|
|
|
|
/*
|
2008-04-24 05:00:13 +02:00
|
|
|
* Copyright (C) 2000 - 2008, Intel Corp.
|
2007-02-02 17:48:20 +01:00
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions, and the following disclaimer,
|
|
|
|
* without modification.
|
|
|
|
* 2. Redistributions in binary form must reproduce at minimum a disclaimer
|
|
|
|
* substantially similar to the "NO WARRANTY" disclaimer below
|
|
|
|
* ("Disclaimer") and any redistribution must be conditioned upon
|
|
|
|
* including a substantially similar Disclaimer requirement for further
|
|
|
|
* binary redistribution.
|
|
|
|
* 3. Neither the names of the above-listed copyright holders nor the names
|
|
|
|
* of any contributors may be used to endorse or promote products derived
|
|
|
|
* from this software without specific prior written permission.
|
|
|
|
*
|
|
|
|
* Alternatively, this software may be distributed under the terms of the
|
|
|
|
* GNU General Public License ("GPL") version 2 as published by the Free
|
|
|
|
* Software Foundation.
|
|
|
|
*
|
|
|
|
* NO WARRANTY
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
* "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR
|
|
|
|
* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
|
|
* HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
|
|
|
* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
|
|
|
|
* IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
|
|
* POSSIBILITY OF SUCH DAMAGES.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <acpi/acpi.h>
|
|
|
|
#include <acpi/actables.h>
|
|
|
|
|
|
|
|
#define _COMPONENT ACPI_TABLES
|
|
|
|
ACPI_MODULE_NAME("tbfadt")
|
|
|
|
|
|
|
|
/* Local prototypes */
|
|
|
|
static void inline
|
2007-02-02 17:48:20 +01:00
|
|
|
acpi_tb_init_generic_address(struct acpi_generic_address *generic_address,
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
u8 byte_width, u64 address);
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
static void acpi_tb_convert_fadt(void);
|
|
|
|
|
|
|
|
static void acpi_tb_validate_fadt(void);
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/* Table for conversion of FADT to common internal format and FADT validation */
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
typedef struct acpi_fadt_info {
|
|
|
|
char *name;
|
2007-02-02 17:48:20 +01:00
|
|
|
u8 target;
|
|
|
|
u8 source;
|
|
|
|
u8 length;
|
2007-02-02 17:48:20 +01:00
|
|
|
u8 type;
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
} acpi_fadt_info;
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
#define ACPI_FADT_REQUIRED 1
|
|
|
|
#define ACPI_FADT_SEPARATE_LENGTH 2
|
|
|
|
|
|
|
|
static struct acpi_fadt_info fadt_info_table[] = {
|
|
|
|
{"Pm1aEventBlock", ACPI_FADT_OFFSET(xpm1a_event_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1a_event_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1_event_length), ACPI_FADT_REQUIRED},
|
|
|
|
|
|
|
|
{"Pm1bEventBlock", ACPI_FADT_OFFSET(xpm1b_event_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1b_event_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1_event_length), 0},
|
|
|
|
|
|
|
|
{"Pm1aControlBlock", ACPI_FADT_OFFSET(xpm1a_control_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1a_control_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1_control_length), ACPI_FADT_REQUIRED},
|
|
|
|
|
|
|
|
{"Pm1bControlBlock", ACPI_FADT_OFFSET(xpm1b_control_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1b_control_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm1_control_length), 0},
|
|
|
|
|
|
|
|
{"Pm2ControlBlock", ACPI_FADT_OFFSET(xpm2_control_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm2_control_block),
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_FADT_OFFSET(pm2_control_length), ACPI_FADT_SEPARATE_LENGTH},
|
|
|
|
|
|
|
|
{"PmTimerBlock", ACPI_FADT_OFFSET(xpm_timer_block),
|
|
|
|
ACPI_FADT_OFFSET(pm_timer_block),
|
|
|
|
ACPI_FADT_OFFSET(pm_timer_length), ACPI_FADT_REQUIRED},
|
|
|
|
|
|
|
|
{"Gpe0Block", ACPI_FADT_OFFSET(xgpe0_block),
|
|
|
|
ACPI_FADT_OFFSET(gpe0_block),
|
|
|
|
ACPI_FADT_OFFSET(gpe0_block_length), ACPI_FADT_SEPARATE_LENGTH},
|
|
|
|
|
|
|
|
{"Gpe1Block", ACPI_FADT_OFFSET(xgpe1_block),
|
|
|
|
ACPI_FADT_OFFSET(gpe1_block),
|
|
|
|
ACPI_FADT_OFFSET(gpe1_block_length), ACPI_FADT_SEPARATE_LENGTH}
|
2007-02-02 17:48:20 +01:00
|
|
|
};
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
#define ACPI_FADT_INFO_ENTRIES (sizeof (fadt_info_table) / sizeof (struct acpi_fadt_info))
|
2007-02-02 17:48:20 +01:00
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_tb_init_generic_address
|
|
|
|
*
|
2007-02-02 17:48:20 +01:00
|
|
|
* PARAMETERS: generic_address - GAS struct to be initialized
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
* byte_width - Width of this register
|
2007-02-02 17:48:20 +01:00
|
|
|
* Address - Address of the register
|
|
|
|
*
|
|
|
|
* RETURN: None
|
|
|
|
*
|
2007-02-02 17:48:20 +01:00
|
|
|
* DESCRIPTION: Initialize a Generic Address Structure (GAS)
|
|
|
|
* See the ACPI specification for a full description and
|
|
|
|
* definition of this structure.
|
2007-02-02 17:48:20 +01:00
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
|
|
|
static void inline
|
2007-02-02 17:48:20 +01:00
|
|
|
acpi_tb_init_generic_address(struct acpi_generic_address *generic_address,
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
u8 byte_width, u64 address)
|
2007-02-02 17:48:20 +01:00
|
|
|
{
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/*
|
|
|
|
* The 64-bit Address field is non-aligned in the byte packed
|
|
|
|
* GAS struct.
|
|
|
|
*/
|
|
|
|
ACPI_MOVE_64_TO_64(&generic_address->address, &address);
|
|
|
|
|
|
|
|
/* All other fields are byte-wide */
|
|
|
|
|
|
|
|
generic_address->space_id = ACPI_ADR_SPACE_SYSTEM_IO;
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
generic_address->bit_width = byte_width << 3;
|
2007-02-02 17:48:20 +01:00
|
|
|
generic_address->bit_offset = 0;
|
|
|
|
generic_address->access_width = 0;
|
2007-02-02 17:48:20 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_tb_parse_fadt
|
|
|
|
*
|
|
|
|
* PARAMETERS: table_index - Index for the FADT
|
|
|
|
* Flags - Flags
|
|
|
|
*
|
|
|
|
* RETURN: None
|
|
|
|
*
|
|
|
|
* DESCRIPTION: Initialize the FADT, DSDT and FACS tables
|
|
|
|
* (FADT contains the addresses of the DSDT and FACS)
|
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
2008-06-10 07:42:13 +02:00
|
|
|
void acpi_tb_parse_fadt(u32 table_index, u8 flags)
|
2007-02-02 17:48:20 +01:00
|
|
|
{
|
|
|
|
u32 length;
|
|
|
|
struct acpi_table_header *table;
|
|
|
|
|
|
|
|
/*
|
2007-02-02 17:48:20 +01:00
|
|
|
* The FADT has multiple versions with different lengths,
|
|
|
|
* and it contains pointers to both the DSDT and FACS tables.
|
2007-02-02 17:48:20 +01:00
|
|
|
*
|
|
|
|
* Get a local copy of the FADT and convert it to a common format
|
|
|
|
* Map entire FADT, assumed to be smaller than one page.
|
|
|
|
*/
|
|
|
|
length = acpi_gbl_root_table_list.tables[table_index].length;
|
|
|
|
|
|
|
|
table =
|
|
|
|
acpi_os_map_memory(acpi_gbl_root_table_list.tables[table_index].
|
|
|
|
address, length);
|
|
|
|
if (!table) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Validate the FADT checksum before we copy the table. Ignore
|
|
|
|
* checksum error as we want to try to get the DSDT and FACS.
|
|
|
|
*/
|
|
|
|
(void)acpi_tb_verify_checksum(table, length);
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/* Obtain a local copy of the FADT in common ACPI 2.0+ format */
|
|
|
|
|
|
|
|
acpi_tb_create_local_fadt(table, length);
|
|
|
|
|
|
|
|
/* All done with the real FADT, unmap it */
|
|
|
|
|
|
|
|
acpi_os_unmap_memory(table, length);
|
|
|
|
|
|
|
|
/* Obtain the DSDT and FACS tables via their addresses within the FADT */
|
|
|
|
|
|
|
|
acpi_tb_install_table((acpi_physical_address) acpi_gbl_FADT.Xdsdt,
|
|
|
|
flags, ACPI_SIG_DSDT, ACPI_TABLE_INDEX_DSDT);
|
|
|
|
|
|
|
|
acpi_tb_install_table((acpi_physical_address) acpi_gbl_FADT.Xfacs,
|
|
|
|
flags, ACPI_SIG_FACS, ACPI_TABLE_INDEX_FACS);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_tb_create_local_fadt
|
|
|
|
*
|
|
|
|
* PARAMETERS: Table - Pointer to BIOS FADT
|
|
|
|
* Length - Length of the table
|
|
|
|
*
|
|
|
|
* RETURN: None
|
|
|
|
*
|
|
|
|
* DESCRIPTION: Get a local copy of the FADT and convert it to a common format.
|
|
|
|
* Performs validation on some important FADT fields.
|
|
|
|
*
|
2007-05-02 21:51:37 +02:00
|
|
|
* NOTE: We create a local copy of the FADT regardless of the version.
|
|
|
|
*
|
2007-02-02 17:48:20 +01:00
|
|
|
******************************************************************************/
|
|
|
|
|
|
|
|
void acpi_tb_create_local_fadt(struct acpi_table_header *table, u32 length)
|
|
|
|
{
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/*
|
2007-05-02 21:51:37 +02:00
|
|
|
* Check if the FADT is larger than the largest table that we expect
|
|
|
|
* (the ACPI 2.0/3.0 version). If so, truncate the table, and issue
|
|
|
|
* a warning.
|
2007-02-02 17:48:20 +01:00
|
|
|
*/
|
|
|
|
if (length > sizeof(struct acpi_table_fadt)) {
|
|
|
|
ACPI_WARNING((AE_INFO,
|
2007-01-26 04:39:44 +01:00
|
|
|
"FADT (revision %u) is longer than ACPI 2.0 version, truncating length 0x%X to 0x%zX",
|
|
|
|
table->revision, (unsigned)length,
|
2007-02-02 17:48:20 +01:00
|
|
|
sizeof(struct acpi_table_fadt)));
|
|
|
|
}
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-05-02 21:51:37 +02:00
|
|
|
/* Clear the entire local FADT */
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_MEMSET(&acpi_gbl_FADT, 0, sizeof(struct acpi_table_fadt));
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-05-02 21:51:37 +02:00
|
|
|
/* Copy the original FADT, up to sizeof (struct acpi_table_fadt) */
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_MEMCPY(&acpi_gbl_FADT, table,
|
|
|
|
ACPI_MIN(length, sizeof(struct acpi_table_fadt)));
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/*
|
|
|
|
* 1) Convert the local copy of the FADT to the common internal format
|
|
|
|
* 2) Validate some of the important values within the FADT
|
|
|
|
*/
|
2007-02-02 17:48:20 +01:00
|
|
|
acpi_tb_convert_fadt();
|
2007-02-02 17:48:20 +01:00
|
|
|
acpi_tb_validate_fadt();
|
2007-02-02 17:48:20 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
/*******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_tb_convert_fadt
|
|
|
|
*
|
|
|
|
* PARAMETERS: None, uses acpi_gbl_FADT
|
|
|
|
*
|
|
|
|
* RETURN: None
|
|
|
|
*
|
|
|
|
* DESCRIPTION: Converts all versions of the FADT to a common internal format.
|
2007-05-02 21:51:37 +02:00
|
|
|
* Expand all 32-bit addresses to 64-bit.
|
2007-02-02 17:48:20 +01:00
|
|
|
*
|
2007-02-02 17:48:20 +01:00
|
|
|
* NOTE: acpi_gbl_FADT must be of size (struct acpi_table_fadt),
|
|
|
|
* and must contain a copy of the actual FADT.
|
2007-02-02 17:48:20 +01:00
|
|
|
*
|
|
|
|
* ACPICA will use the "X" fields of the FADT for all addresses.
|
|
|
|
*
|
|
|
|
* "X" fields are optional extensions to the original V1.0 fields. Even if
|
|
|
|
* they are present in the structure, they can be optionally not used by
|
|
|
|
* setting them to zero. Therefore, we must selectively expand V1.0 fields
|
|
|
|
* if the corresponding X field is zero.
|
|
|
|
*
|
|
|
|
* For ACPI 1.0 FADTs, all address fields are expanded to the corresponding
|
|
|
|
* "X" fields.
|
|
|
|
*
|
|
|
|
* For ACPI 2.0 FADTs, any "X" fields that are NULL are filled in by
|
|
|
|
* expanding the corresponding ACPI 1.0 field.
|
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
static void acpi_tb_convert_fadt(void)
|
2007-02-02 17:48:20 +01:00
|
|
|
{
|
|
|
|
u8 pm1_register_length;
|
|
|
|
struct acpi_generic_address *target;
|
2008-06-10 07:42:13 +02:00
|
|
|
u32 i;
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/* Update the local FADT table header length */
|
|
|
|
|
|
|
|
acpi_gbl_FADT.header.length = sizeof(struct acpi_table_fadt);
|
|
|
|
|
|
|
|
/* Expand the 32-bit FACS and DSDT addresses to 64-bit as necessary */
|
2007-02-02 17:48:20 +01:00
|
|
|
|
|
|
|
if (!acpi_gbl_FADT.Xfacs) {
|
|
|
|
acpi_gbl_FADT.Xfacs = (u64) acpi_gbl_FADT.facs;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!acpi_gbl_FADT.Xdsdt) {
|
|
|
|
acpi_gbl_FADT.Xdsdt = (u64) acpi_gbl_FADT.dsdt;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2007-05-02 21:51:37 +02:00
|
|
|
* For ACPI 1.0 FADTs (revision 1 or 2), ensure that reserved fields which
|
|
|
|
* should be zero are indeed zero. This will workaround BIOSs that
|
|
|
|
* inadvertently place values in these fields.
|
|
|
|
*
|
|
|
|
* The ACPI 1.0 reserved fields that will be zeroed are the bytes located at
|
|
|
|
* offset 45, 55, 95, and the word located at offset 109, 110.
|
|
|
|
*/
|
2008-10-29 22:13:22 +01:00
|
|
|
if (acpi_gbl_FADT.header.revision < FADT2_REVISION_ID) {
|
2007-05-02 21:51:37 +02:00
|
|
|
acpi_gbl_FADT.preferred_profile = 0;
|
|
|
|
acpi_gbl_FADT.pstate_control = 0;
|
|
|
|
acpi_gbl_FADT.cst_control = 0;
|
|
|
|
acpi_gbl_FADT.boot_flags = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Expand the ACPI 1.0 32-bit V1.0 addresses to the ACPI 2.0 64-bit "X"
|
|
|
|
* generic address structures as necessary.
|
2007-02-02 17:48:20 +01:00
|
|
|
*/
|
2007-02-02 17:48:20 +01:00
|
|
|
for (i = 0; i < ACPI_FADT_INFO_ENTRIES; i++) {
|
2007-02-02 17:48:20 +01:00
|
|
|
target =
|
|
|
|
ACPI_ADD_PTR(struct acpi_generic_address, &acpi_gbl_FADT,
|
2007-02-02 17:48:20 +01:00
|
|
|
fadt_info_table[i].target);
|
2007-02-02 17:48:20 +01:00
|
|
|
|
|
|
|
/* Expand only if the X target is null */
|
|
|
|
|
|
|
|
if (!target->address) {
|
|
|
|
acpi_tb_init_generic_address(target,
|
|
|
|
*ACPI_ADD_PTR(u8,
|
|
|
|
&acpi_gbl_FADT,
|
2007-02-02 17:48:20 +01:00
|
|
|
fadt_info_table
|
2007-02-02 17:48:20 +01:00
|
|
|
[i].length),
|
|
|
|
(u64) * ACPI_ADD_PTR(u32,
|
|
|
|
&acpi_gbl_FADT,
|
2007-02-02 17:48:20 +01:00
|
|
|
fadt_info_table
|
2007-02-02 17:48:20 +01:00
|
|
|
[i].
|
|
|
|
source));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Calculate separate GAS structs for the PM1 Enable registers.
|
|
|
|
* These addresses do not appear (directly) in the FADT, so it is
|
|
|
|
* useful to calculate them once, here.
|
|
|
|
*
|
|
|
|
* The PM event blocks are split into two register blocks, first is the
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
* PM Status Register block, followed immediately by the PM Enable
|
|
|
|
* Register block. Each is of length (xpm1x_event_block.bit_width/2).
|
|
|
|
*
|
|
|
|
* On various systems the v2 fields (and particularly the bit widths)
|
|
|
|
* cannot be relied upon, though. Hence resort to using the v1 length
|
|
|
|
* here (and warn about the inconsistency).
|
2007-02-02 17:48:20 +01:00
|
|
|
*/
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
if (acpi_gbl_FADT.xpm1a_event_block.bit_width
|
|
|
|
!= acpi_gbl_FADT.pm1_event_length * 8)
|
|
|
|
printk(KERN_WARNING "FADT: "
|
|
|
|
"X_PM1a_EVT_BLK.bit_width (%u) does not match"
|
|
|
|
" PM1_EVT_LEN (%u)\n",
|
|
|
|
acpi_gbl_FADT.xpm1a_event_block.bit_width,
|
|
|
|
acpi_gbl_FADT.pm1_event_length);
|
2008-07-18 01:42:20 +02:00
|
|
|
pm1_register_length = (u8) ACPI_DIV_2(acpi_gbl_FADT.pm1_event_length);
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/* The PM1A register block is required */
|
2007-02-02 17:48:20 +01:00
|
|
|
|
|
|
|
acpi_tb_init_generic_address(&acpi_gbl_xpm1a_enable,
|
|
|
|
pm1_register_length,
|
|
|
|
(acpi_gbl_FADT.xpm1a_event_block.address +
|
|
|
|
pm1_register_length));
|
2007-02-03 03:48:40 +01:00
|
|
|
/* Don't forget to copy space_id of the GAS */
|
2007-05-10 05:34:35 +02:00
|
|
|
acpi_gbl_xpm1a_enable.space_id =
|
|
|
|
acpi_gbl_FADT.xpm1a_event_block.space_id;
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/* The PM1B register block is optional, ignore if not present */
|
2007-02-02 17:48:20 +01:00
|
|
|
|
|
|
|
if (acpi_gbl_FADT.xpm1b_event_block.address) {
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
if (acpi_gbl_FADT.xpm1b_event_block.bit_width
|
|
|
|
!= acpi_gbl_FADT.pm1_event_length * 8)
|
|
|
|
printk(KERN_WARNING "FADT: "
|
|
|
|
"X_PM1b_EVT_BLK.bit_width (%u) does not match"
|
|
|
|
" PM1_EVT_LEN (%u)\n",
|
|
|
|
acpi_gbl_FADT.xpm1b_event_block.bit_width,
|
|
|
|
acpi_gbl_FADT.pm1_event_length);
|
2007-02-02 17:48:20 +01:00
|
|
|
acpi_tb_init_generic_address(&acpi_gbl_xpm1b_enable,
|
|
|
|
pm1_register_length,
|
|
|
|
(acpi_gbl_FADT.xpm1b_event_block.
|
|
|
|
address + pm1_register_length));
|
2007-02-03 03:48:40 +01:00
|
|
|
/* Don't forget to copy space_id of the GAS */
|
2007-05-10 05:34:35 +02:00
|
|
|
acpi_gbl_xpm1b_enable.space_id =
|
ACPI: fix FADT parsing
The (1.0 inherited) separate length fields in the FADT are byte granular.
Further, PM1a/b may have distinct lengths (if using the v2 fields was
okay) and may live in distinct address spaces. acpi_tb_convert_fadt()
should account for all of these conditions.
Apart from these changes I'm puzzled by the fact that, not just for
acpi_gbl_xpm1{a,b}_enable, acpi_hw_low_level_{read,write}() get an
explicit size passed rather than using the size found in the passed GAS.
What happens on a platform that defines PM1{a,b} wider than 16 bits? Of
course, acpi_hw_low_level_{read,write}() at present are entirely
un-prepared to deal with sizes other than 8, 16, or 32, not to speak of a
non-zero bit_offset or access_width...
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
2008-09-20 00:50:32 +02:00
|
|
|
acpi_gbl_FADT.xpm1b_event_block.space_id;
|
2008-07-18 01:42:20 +02:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/******************************************************************************
|
|
|
|
*
|
|
|
|
* FUNCTION: acpi_tb_validate_fadt
|
|
|
|
*
|
2007-02-02 17:48:20 +01:00
|
|
|
* PARAMETERS: Table - Pointer to the FADT to be validated
|
2007-02-02 17:48:20 +01:00
|
|
|
*
|
2007-02-02 17:48:20 +01:00
|
|
|
* RETURN: None
|
2007-02-02 17:48:20 +01:00
|
|
|
*
|
2007-02-02 17:48:20 +01:00
|
|
|
* DESCRIPTION: Validate various important fields within the FADT. If a problem
|
|
|
|
* is found, issue a message, but no status is returned.
|
|
|
|
* Used by both the table manager and the disassembler.
|
|
|
|
*
|
|
|
|
* Possible additional checks:
|
|
|
|
* (acpi_gbl_FADT.pm1_event_length >= 4)
|
|
|
|
* (acpi_gbl_FADT.pm1_control_length >= 2)
|
|
|
|
* (acpi_gbl_FADT.pm_timer_length >= 4)
|
|
|
|
* Gpe block lengths must be multiple of 2
|
2007-02-02 17:48:20 +01:00
|
|
|
*
|
|
|
|
******************************************************************************/
|
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
static void acpi_tb_validate_fadt(void)
|
2007-02-02 17:48:20 +01:00
|
|
|
{
|
2007-02-02 17:48:20 +01:00
|
|
|
u32 *address32;
|
|
|
|
struct acpi_generic_address *address64;
|
|
|
|
u8 length;
|
2008-06-10 07:42:13 +02:00
|
|
|
u32 i;
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/* Examine all of the 64-bit extended address fields (X fields) */
|
|
|
|
|
|
|
|
for (i = 0; i < ACPI_FADT_INFO_ENTRIES; i++) {
|
|
|
|
|
|
|
|
/* Generate pointers to the 32-bit and 64-bit addresses and get the length */
|
|
|
|
|
|
|
|
address64 =
|
2007-02-02 17:48:20 +01:00
|
|
|
ACPI_ADD_PTR(struct acpi_generic_address, &acpi_gbl_FADT,
|
2007-02-02 17:48:20 +01:00
|
|
|
fadt_info_table[i].target);
|
2007-02-02 17:48:20 +01:00
|
|
|
address32 =
|
|
|
|
ACPI_ADD_PTR(u32, &acpi_gbl_FADT,
|
|
|
|
fadt_info_table[i].source);
|
|
|
|
length =
|
|
|
|
*ACPI_ADD_PTR(u8, &acpi_gbl_FADT,
|
|
|
|
fadt_info_table[i].length);
|
2007-02-02 17:48:20 +01:00
|
|
|
|
|
|
|
if (fadt_info_table[i].type & ACPI_FADT_REQUIRED) {
|
|
|
|
/*
|
|
|
|
* Field is required (Pm1a_event, Pm1a_control, pm_timer).
|
|
|
|
* Both the address and length must be non-zero.
|
|
|
|
*/
|
|
|
|
if (!address64->address || !length) {
|
|
|
|
ACPI_ERROR((AE_INFO,
|
|
|
|
"Required field \"%s\" has zero address and/or length: %8.8X%8.8X/%X",
|
|
|
|
fadt_info_table[i].name,
|
|
|
|
ACPI_FORMAT_UINT64(address64->
|
|
|
|
address),
|
|
|
|
length));
|
|
|
|
}
|
|
|
|
} else if (fadt_info_table[i].type & ACPI_FADT_SEPARATE_LENGTH) {
|
|
|
|
/*
|
|
|
|
* Field is optional (PM2Control, GPE0, GPE1) AND has its own
|
|
|
|
* length field. If present, both the address and length must be valid.
|
|
|
|
*/
|
|
|
|
if ((address64->address && !length)
|
|
|
|
|| (!address64->address && length)) {
|
|
|
|
ACPI_WARNING((AE_INFO,
|
|
|
|
"Optional field \"%s\" has zero address or length: %8.8X%8.8X/%X",
|
|
|
|
fadt_info_table[i].name,
|
|
|
|
ACPI_FORMAT_UINT64(address64->
|
|
|
|
address),
|
|
|
|
length));
|
|
|
|
}
|
|
|
|
}
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
/* If both 32- and 64-bit addresses are valid (non-zero), they must match */
|
2007-02-02 17:48:20 +01:00
|
|
|
|
2007-02-02 17:48:20 +01:00
|
|
|
if (address64->address && *address32 &&
|
|
|
|
(address64->address != (u64) * address32)) {
|
|
|
|
ACPI_ERROR((AE_INFO,
|
|
|
|
"32/64X address mismatch in \"%s\": [%8.8X] [%8.8X%8.8X], using 64X",
|
|
|
|
fadt_info_table[i].name, *address32,
|
|
|
|
ACPI_FORMAT_UINT64(address64->address)));
|
|
|
|
}
|
2007-02-02 17:48:20 +01:00
|
|
|
}
|
|
|
|
}
|