Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
/*
|
|
|
|
* This file is subject to the terms and conditions of the GNU General Public
|
|
|
|
* License. See the file "COPYING" in the main directory of this archive
|
|
|
|
* for more details.
|
|
|
|
*
|
|
|
|
* Copyright (C) 2006 Silicon Graphics, Inc. All rights reserved.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <asm/sn/types.h>
|
|
|
|
#include <asm/sn/addrs.h>
|
|
|
|
#include <asm/sn/pcidev.h>
|
|
|
|
#include <asm/sn/pcibus_provider_defs.h>
|
|
|
|
#include <asm/sn/sn_sal.h>
|
|
|
|
#include "xtalk/hubdev.h"
|
|
|
|
#include <linux/acpi.h>
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The code in this file will only be executed when running with
|
|
|
|
* a PROM that has ACPI IO support. (i.e., SN_ACPI_BASE_SUPPORT() == 1)
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This value must match the UUID the PROM uses
|
|
|
|
* (io/acpi/defblk.c) when building a vendor descriptor.
|
|
|
|
*/
|
|
|
|
struct acpi_vendor_uuid sn_uuid = {
|
|
|
|
.subtype = 0,
|
|
|
|
.data = { 0x2c, 0xc6, 0xa6, 0xfe, 0x9c, 0x44, 0xda, 0x11,
|
|
|
|
0xa2, 0x7c, 0x08, 0x00, 0x69, 0x13, 0xea, 0x51 },
|
|
|
|
};
|
|
|
|
|
2007-01-30 06:17:37 +00:00
|
|
|
struct sn_pcidev_match {
|
|
|
|
u8 bus;
|
|
|
|
unsigned int devfn;
|
|
|
|
acpi_handle handle;
|
|
|
|
};
|
|
|
|
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
/*
|
|
|
|
* Perform the early IO init in PROM.
|
|
|
|
*/
|
2009-05-22 20:49:49 +00:00
|
|
|
static long
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
sal_ioif_init(u64 *result)
|
|
|
|
{
|
|
|
|
struct ia64_sal_retval isrv = {0,0,0,0};
|
|
|
|
|
|
|
|
SAL_CALL_NOLOCK(isrv,
|
|
|
|
SN_SAL_IOIF_INIT, 0, 0, 0, 0, 0, 0, 0);
|
|
|
|
*result = isrv.v0;
|
|
|
|
return isrv.status;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2007-02-23 22:24:16 +00:00
|
|
|
* sn_acpi_hubdev_init() - This function is called by acpi_ns_get_device_callback()
|
|
|
|
* for all SGIHUB and SGITIO acpi devices defined in the
|
|
|
|
* DSDT. It obtains the hubdev_info pointer from the
|
|
|
|
* ACPI vendor resource, which the PROM setup, and sets up the
|
|
|
|
* hubdev_info in the pda.
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
*/
|
2007-02-23 22:24:16 +00:00
|
|
|
|
|
|
|
static acpi_status __init
|
|
|
|
sn_acpi_hubdev_init(acpi_handle handle, u32 depth, void *context, void **ret)
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
{
|
|
|
|
struct acpi_buffer buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
2008-12-16 09:07:01 +00:00
|
|
|
struct acpi_buffer name_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
u64 addr;
|
|
|
|
struct hubdev_info *hubdev;
|
|
|
|
struct hubdev_info *hubdev_ptr;
|
|
|
|
int i;
|
|
|
|
u64 nasid;
|
|
|
|
struct acpi_resource *resource;
|
|
|
|
acpi_status status;
|
|
|
|
struct acpi_resource_vendor_typed *vendor;
|
|
|
|
extern void sn_common_hubdev_init(struct hubdev_info *);
|
|
|
|
|
2007-02-23 22:24:16 +00:00
|
|
|
status = acpi_get_vendor_resource(handle, METHOD_NAME__CRS,
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
&sn_uuid, &buffer);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(handle, ACPI_FULL_PATHNAME, &name_buffer);
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
printk(KERN_ERR
|
2007-02-23 22:24:16 +00:00
|
|
|
"sn_acpi_hubdev_init: acpi_get_vendor_resource() "
|
2008-12-16 09:07:01 +00:00
|
|
|
"(0x%x) failed for: %s\n", status,
|
|
|
|
(char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
2007-02-23 22:24:16 +00:00
|
|
|
return AE_OK; /* Continue walking namespace */
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
resource = buffer.pointer;
|
|
|
|
vendor = &resource->data.vendor_typed;
|
|
|
|
if ((vendor->byte_length - sizeof(struct acpi_vendor_uuid)) !=
|
|
|
|
sizeof(struct hubdev_info *)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(handle, ACPI_FULL_PATHNAME, &name_buffer);
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
printk(KERN_ERR
|
2008-12-16 09:07:01 +00:00
|
|
|
"sn_acpi_hubdev_init: Invalid vendor data length: "
|
|
|
|
"%d for: %s\n",
|
|
|
|
vendor->byte_length, (char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
memcpy(&addr, vendor->byte_data, sizeof(struct hubdev_info *));
|
|
|
|
hubdev_ptr = __va((struct hubdev_info *) addr);
|
|
|
|
|
|
|
|
nasid = hubdev_ptr->hdi_nasid;
|
|
|
|
i = nasid_to_cnodeid(nasid);
|
|
|
|
hubdev = (struct hubdev_info *)(NODEPDA(i)->pdinfo);
|
|
|
|
*hubdev = *hubdev_ptr;
|
|
|
|
sn_common_hubdev_init(hubdev);
|
|
|
|
|
|
|
|
exit:
|
|
|
|
kfree(buffer.pointer);
|
2007-02-23 22:24:16 +00:00
|
|
|
return AE_OK; /* Continue walking namespace */
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* sn_get_bussoft_ptr() - The pcibus_bussoft pointer is found in
|
|
|
|
* the ACPI Vendor resource for this bus.
|
|
|
|
*/
|
|
|
|
static struct pcibus_bussoft *
|
|
|
|
sn_get_bussoft_ptr(struct pci_bus *bus)
|
|
|
|
{
|
|
|
|
u64 addr;
|
|
|
|
struct acpi_buffer buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
2008-12-16 09:07:01 +00:00
|
|
|
struct acpi_buffer name_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
acpi_handle handle;
|
|
|
|
struct pcibus_bussoft *prom_bussoft_ptr;
|
|
|
|
struct acpi_resource *resource;
|
|
|
|
acpi_status status;
|
|
|
|
struct acpi_resource_vendor_typed *vendor;
|
|
|
|
|
|
|
|
|
|
|
|
handle = PCI_CONTROLLER(bus)->acpi_handle;
|
|
|
|
status = acpi_get_vendor_resource(handle, METHOD_NAME__CRS,
|
|
|
|
&sn_uuid, &buffer);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(handle, ACPI_FULL_PATHNAME, &name_buffer);
|
2007-01-30 06:17:37 +00:00
|
|
|
printk(KERN_ERR "%s: "
|
2008-12-16 09:07:01 +00:00
|
|
|
"acpi_get_vendor_resource() failed (0x%x) for: %s\n",
|
|
|
|
__func__, status, (char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
resource = buffer.pointer;
|
|
|
|
vendor = &resource->data.vendor_typed;
|
|
|
|
|
|
|
|
if ((vendor->byte_length - sizeof(struct acpi_vendor_uuid)) !=
|
|
|
|
sizeof(struct pcibus_bussoft *)) {
|
|
|
|
printk(KERN_ERR
|
2007-01-30 06:17:37 +00:00
|
|
|
"%s: Invalid vendor data length %d\n",
|
2008-03-04 23:15:00 +00:00
|
|
|
__func__, vendor->byte_length);
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
kfree(buffer.pointer);
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
memcpy(&addr, vendor->byte_data, sizeof(struct pcibus_bussoft *));
|
|
|
|
prom_bussoft_ptr = __va((struct pcibus_bussoft *) addr);
|
|
|
|
kfree(buffer.pointer);
|
|
|
|
|
|
|
|
return prom_bussoft_ptr;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2007-01-30 06:17:37 +00:00
|
|
|
* sn_extract_device_info - Extract the pcidev_info and the sn_irq_info
|
|
|
|
* pointers from the vendor resource using the
|
|
|
|
* provided acpi handle, and copy the structures
|
|
|
|
* into the argument buffers.
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
*/
|
2007-01-30 06:17:37 +00:00
|
|
|
static int
|
|
|
|
sn_extract_device_info(acpi_handle handle, struct pcidev_info **pcidev_info,
|
|
|
|
struct sn_irq_info **sn_irq_info)
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
{
|
2007-01-30 06:17:37 +00:00
|
|
|
u64 addr;
|
|
|
|
struct acpi_buffer buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
2008-12-16 09:07:01 +00:00
|
|
|
struct acpi_buffer name_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
2007-01-30 06:17:37 +00:00
|
|
|
struct sn_irq_info *irq_info, *irq_info_prom;
|
|
|
|
struct pcidev_info *pcidev_ptr, *pcidev_prom_ptr;
|
|
|
|
struct acpi_resource *resource;
|
|
|
|
int ret = 0;
|
|
|
|
acpi_status status;
|
|
|
|
struct acpi_resource_vendor_typed *vendor;
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
|
2007-01-30 06:17:37 +00:00
|
|
|
/*
|
|
|
|
* The pointer to this device's pcidev_info structure in
|
|
|
|
* the PROM, is in the vendor resource.
|
|
|
|
*/
|
|
|
|
status = acpi_get_vendor_resource(handle, METHOD_NAME__CRS,
|
|
|
|
&sn_uuid, &buffer);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(handle, ACPI_FULL_PATHNAME, &name_buffer);
|
2007-01-30 06:17:37 +00:00
|
|
|
printk(KERN_ERR
|
2008-12-16 09:07:01 +00:00
|
|
|
"%s: acpi_get_vendor_resource() failed (0x%x) for: %s\n",
|
|
|
|
__func__, status, (char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
2007-01-30 06:17:37 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
resource = buffer.pointer;
|
|
|
|
vendor = &resource->data.vendor_typed;
|
|
|
|
if ((vendor->byte_length - sizeof(struct acpi_vendor_uuid)) !=
|
|
|
|
sizeof(struct pci_devdev_info *)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(handle, ACPI_FULL_PATHNAME, &name_buffer);
|
2007-01-30 06:17:37 +00:00
|
|
|
printk(KERN_ERR
|
2008-12-16 09:07:01 +00:00
|
|
|
"%s: Invalid vendor data length: %d for: %s\n",
|
|
|
|
__func__, vendor->byte_length,
|
|
|
|
(char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
2007-01-30 06:17:37 +00:00
|
|
|
ret = 1;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
pcidev_ptr = kzalloc(sizeof(struct pcidev_info), GFP_KERNEL);
|
|
|
|
if (!pcidev_ptr)
|
2008-03-04 23:15:00 +00:00
|
|
|
panic("%s: Unable to alloc memory for pcidev_info", __func__);
|
2007-01-30 06:17:37 +00:00
|
|
|
|
|
|
|
memcpy(&addr, vendor->byte_data, sizeof(struct pcidev_info *));
|
|
|
|
pcidev_prom_ptr = __va(addr);
|
|
|
|
memcpy(pcidev_ptr, pcidev_prom_ptr, sizeof(struct pcidev_info));
|
|
|
|
|
|
|
|
/* Get the IRQ info */
|
|
|
|
irq_info = kzalloc(sizeof(struct sn_irq_info), GFP_KERNEL);
|
|
|
|
if (!irq_info)
|
2008-03-04 23:15:00 +00:00
|
|
|
panic("%s: Unable to alloc memory for sn_irq_info", __func__);
|
2007-01-30 06:17:37 +00:00
|
|
|
|
|
|
|
if (pcidev_ptr->pdi_sn_irq_info) {
|
|
|
|
irq_info_prom = __va(pcidev_ptr->pdi_sn_irq_info);
|
|
|
|
memcpy(irq_info, irq_info_prom, sizeof(struct sn_irq_info));
|
|
|
|
}
|
|
|
|
|
|
|
|
*pcidev_info = pcidev_ptr;
|
|
|
|
*sn_irq_info = irq_info;
|
|
|
|
|
|
|
|
exit:
|
|
|
|
kfree(buffer.pointer);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static unsigned int
|
|
|
|
get_host_devfn(acpi_handle device_handle, acpi_handle rootbus_handle)
|
|
|
|
{
|
2008-10-10 06:22:59 +00:00
|
|
|
unsigned long long adr;
|
2007-01-30 06:17:37 +00:00
|
|
|
acpi_handle child;
|
|
|
|
unsigned int devfn;
|
|
|
|
int function;
|
|
|
|
acpi_handle parent;
|
|
|
|
int slot;
|
|
|
|
acpi_status status;
|
2008-12-16 09:07:01 +00:00
|
|
|
struct acpi_buffer name_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
|
|
|
|
|
|
|
acpi_get_name(device_handle, ACPI_FULL_PATHNAME, &name_buffer);
|
2007-01-30 06:17:37 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Do an upward search to find the root bus device, and
|
|
|
|
* obtain the host devfn from the previous child device.
|
|
|
|
*/
|
|
|
|
child = device_handle;
|
|
|
|
while (child) {
|
|
|
|
status = acpi_get_parent(child, &parent);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
|
|
|
printk(KERN_ERR "%s: acpi_get_parent() failed "
|
2008-12-16 09:07:01 +00:00
|
|
|
"(0x%x) for: %s\n", __func__, status,
|
|
|
|
(char *)name_buffer.pointer);
|
2008-03-04 23:15:00 +00:00
|
|
|
panic("%s: Unable to find host devfn\n", __func__);
|
2007-01-30 06:17:37 +00:00
|
|
|
}
|
|
|
|
if (parent == rootbus_handle)
|
|
|
|
break;
|
|
|
|
child = parent;
|
|
|
|
}
|
|
|
|
if (!child) {
|
2008-12-16 09:07:01 +00:00
|
|
|
printk(KERN_ERR "%s: Unable to find root bus for: %s\n",
|
|
|
|
__func__, (char *)name_buffer.pointer);
|
2007-01-30 06:17:37 +00:00
|
|
|
BUG();
|
|
|
|
}
|
|
|
|
|
|
|
|
status = acpi_evaluate_integer(child, METHOD_NAME__ADR, NULL, &adr);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
printk(KERN_ERR "%s: Unable to get _ADR (0x%x) for: %s\n",
|
|
|
|
__func__, status, (char *)name_buffer.pointer);
|
2008-03-04 23:15:00 +00:00
|
|
|
panic("%s: Unable to find host devfn\n", __func__);
|
2007-01-30 06:17:37 +00:00
|
|
|
}
|
|
|
|
|
2008-12-16 09:07:01 +00:00
|
|
|
kfree(name_buffer.pointer);
|
|
|
|
|
2007-01-30 06:17:37 +00:00
|
|
|
slot = (adr >> 16) & 0xffff;
|
|
|
|
function = adr & 0xffff;
|
|
|
|
devfn = PCI_DEVFN(slot, function);
|
|
|
|
return devfn;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* find_matching_device - Callback routine to find the ACPI device
|
|
|
|
* that matches up with our pci_dev device.
|
|
|
|
* Matching is done on bus number and devfn.
|
|
|
|
* To find the bus number for a particular
|
|
|
|
* ACPI device, we must look at the _BBN method
|
|
|
|
* of its parent.
|
|
|
|
*/
|
|
|
|
static acpi_status
|
|
|
|
find_matching_device(acpi_handle handle, u32 lvl, void *context, void **rv)
|
|
|
|
{
|
2008-10-10 06:22:59 +00:00
|
|
|
unsigned long long bbn = -1;
|
|
|
|
unsigned long long adr;
|
2007-01-30 06:17:37 +00:00
|
|
|
acpi_handle parent = NULL;
|
|
|
|
acpi_status status;
|
|
|
|
unsigned int devfn;
|
|
|
|
int function;
|
|
|
|
int slot;
|
|
|
|
struct sn_pcidev_match *info = context;
|
2008-12-16 09:07:01 +00:00
|
|
|
struct acpi_buffer name_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
2007-01-30 06:17:37 +00:00
|
|
|
|
|
|
|
status = acpi_evaluate_integer(handle, METHOD_NAME__ADR, NULL,
|
|
|
|
&adr);
|
|
|
|
if (ACPI_SUCCESS(status)) {
|
|
|
|
status = acpi_get_parent(handle, &parent);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(handle, ACPI_FULL_PATHNAME, &name_buffer);
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
printk(KERN_ERR
|
2008-12-16 09:07:01 +00:00
|
|
|
"%s: acpi_get_parent() failed (0x%x) for: %s\n",
|
|
|
|
__func__, status, (char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
2007-01-30 06:17:37 +00:00
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
status = acpi_evaluate_integer(parent, METHOD_NAME__BBN,
|
|
|
|
NULL, &bbn);
|
|
|
|
if (ACPI_FAILURE(status)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(handle, ACPI_FULL_PATHNAME, &name_buffer);
|
2007-01-30 06:17:37 +00:00
|
|
|
printk(KERN_ERR
|
2008-12-16 09:07:01 +00:00
|
|
|
"%s: Failed to find _BBN in parent of: %s\n",
|
|
|
|
__func__, (char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
2007-01-30 06:17:37 +00:00
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
slot = (adr >> 16) & 0xffff;
|
|
|
|
function = adr & 0xffff;
|
|
|
|
devfn = PCI_DEVFN(slot, function);
|
|
|
|
if ((info->devfn == devfn) && (info->bus == bbn)) {
|
|
|
|
/* We have a match! */
|
|
|
|
info->handle = handle;
|
|
|
|
return 1;
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
}
|
|
|
|
}
|
2007-01-30 06:17:37 +00:00
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* sn_acpi_get_pcidev_info - Search ACPI namespace for the acpi
|
|
|
|
* device matching the specified pci_dev,
|
|
|
|
* and return the pcidev info and irq info.
|
|
|
|
*/
|
|
|
|
int
|
|
|
|
sn_acpi_get_pcidev_info(struct pci_dev *dev, struct pcidev_info **pcidev_info,
|
|
|
|
struct sn_irq_info **sn_irq_info)
|
|
|
|
{
|
|
|
|
unsigned int host_devfn;
|
|
|
|
struct sn_pcidev_match pcidev_match;
|
|
|
|
acpi_handle rootbus_handle;
|
2008-10-10 06:22:59 +00:00
|
|
|
unsigned long long segment;
|
2007-01-30 06:17:37 +00:00
|
|
|
acpi_status status;
|
2008-12-16 09:07:01 +00:00
|
|
|
struct acpi_buffer name_buffer = { ACPI_ALLOCATE_BUFFER, NULL };
|
2007-01-30 06:17:37 +00:00
|
|
|
|
|
|
|
rootbus_handle = PCI_CONTROLLER(dev)->acpi_handle;
|
|
|
|
status = acpi_evaluate_integer(rootbus_handle, METHOD_NAME__SEG, NULL,
|
|
|
|
&segment);
|
|
|
|
if (ACPI_SUCCESS(status)) {
|
|
|
|
if (segment != pci_domain_nr(dev)) {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(rootbus_handle, ACPI_FULL_PATHNAME,
|
|
|
|
&name_buffer);
|
2007-01-30 06:17:37 +00:00
|
|
|
printk(KERN_ERR
|
2008-12-16 09:07:01 +00:00
|
|
|
"%s: Segment number mismatch, 0x%llx vs 0x%x for: %s\n",
|
|
|
|
__func__, segment, pci_domain_nr(dev),
|
|
|
|
(char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
2007-01-30 06:17:37 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
} else {
|
2008-12-16 09:07:01 +00:00
|
|
|
acpi_get_name(rootbus_handle, ACPI_FULL_PATHNAME, &name_buffer);
|
|
|
|
printk(KERN_ERR "%s: Unable to get __SEG from: %s\n",
|
|
|
|
__func__, (char *)name_buffer.pointer);
|
|
|
|
kfree(name_buffer.pointer);
|
2007-01-30 06:17:37 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We want to search all devices in this segment/domain
|
|
|
|
* of the ACPI namespace for the matching ACPI device,
|
|
|
|
* which holds the pcidev_info pointer in its vendor resource.
|
|
|
|
*/
|
|
|
|
pcidev_match.bus = dev->bus->number;
|
|
|
|
pcidev_match.devfn = dev->devfn;
|
|
|
|
pcidev_match.handle = NULL;
|
|
|
|
|
|
|
|
acpi_walk_namespace(ACPI_TYPE_DEVICE, rootbus_handle, ACPI_UINT32_MAX,
|
|
|
|
find_matching_device, &pcidev_match, NULL);
|
|
|
|
|
|
|
|
if (!pcidev_match.handle) {
|
|
|
|
printk(KERN_ERR
|
|
|
|
"%s: Could not find matching ACPI device for %s.\n",
|
2008-03-04 23:15:00 +00:00
|
|
|
__func__, pci_name(dev));
|
2007-01-30 06:17:37 +00:00
|
|
|
return 1;
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
}
|
2007-01-30 06:17:37 +00:00
|
|
|
|
|
|
|
if (sn_extract_device_info(pcidev_match.handle, pcidev_info, sn_irq_info))
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
/* Build up the pcidev_info.pdi_slot_host_handle */
|
|
|
|
host_devfn = get_host_devfn(pcidev_match.handle, rootbus_handle);
|
|
|
|
(*pcidev_info)->pdi_slot_host_handle =
|
|
|
|
((unsigned long) pci_domain_nr(dev) << 40) |
|
|
|
|
/* bus == 0 */
|
|
|
|
host_devfn;
|
|
|
|
return 0;
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
}
|
|
|
|
|
2006-10-04 21:49:52 +00:00
|
|
|
/*
|
2007-01-30 06:17:37 +00:00
|
|
|
* sn_acpi_slot_fixup - Obtain the pcidev_info and sn_irq_info.
|
|
|
|
* Perform any SN specific slot fixup.
|
2006-10-04 21:49:52 +00:00
|
|
|
* At present there does not appear to be
|
|
|
|
* any generic way to handle a ROM image
|
|
|
|
* that has been shadowed by the PROM, so
|
|
|
|
* we pass a pointer to it within the
|
|
|
|
* pcidev_info structure.
|
|
|
|
*/
|
|
|
|
|
|
|
|
void
|
2007-01-30 06:17:37 +00:00
|
|
|
sn_acpi_slot_fixup(struct pci_dev *dev)
|
2006-10-04 21:49:52 +00:00
|
|
|
{
|
|
|
|
void __iomem *addr;
|
2007-01-30 06:17:37 +00:00
|
|
|
struct pcidev_info *pcidev_info = NULL;
|
|
|
|
struct sn_irq_info *sn_irq_info = NULL;
|
2007-07-09 18:42:24 +00:00
|
|
|
size_t image_size, size;
|
2006-10-04 21:49:52 +00:00
|
|
|
|
2007-01-30 06:17:37 +00:00
|
|
|
if (sn_acpi_get_pcidev_info(dev, &pcidev_info, &sn_irq_info)) {
|
|
|
|
panic("%s: Failure obtaining pcidev_info for %s\n",
|
2008-03-04 23:15:00 +00:00
|
|
|
__func__, pci_name(dev));
|
2007-01-30 06:17:37 +00:00
|
|
|
}
|
|
|
|
|
2006-10-04 21:49:52 +00:00
|
|
|
if (pcidev_info->pdi_pio_mapped_addr[PCI_ROM_RESOURCE]) {
|
|
|
|
/*
|
|
|
|
* A valid ROM image exists and has been shadowed by the
|
2007-07-09 18:42:24 +00:00
|
|
|
* PROM. Setup the pci_dev ROM resource with the address
|
|
|
|
* of the shadowed copy, and the actual length of the ROM image.
|
2006-10-04 21:49:52 +00:00
|
|
|
*/
|
2007-07-09 18:42:24 +00:00
|
|
|
size = pci_resource_len(dev, PCI_ROM_RESOURCE);
|
|
|
|
addr = ioremap(pcidev_info->pdi_pio_mapped_addr[PCI_ROM_RESOURCE],
|
|
|
|
size);
|
2009-01-29 19:12:47 +00:00
|
|
|
image_size = pci_get_rom_size(dev, addr, size);
|
2006-10-04 21:49:52 +00:00
|
|
|
dev->resource[PCI_ROM_RESOURCE].start = (unsigned long) addr;
|
|
|
|
dev->resource[PCI_ROM_RESOURCE].end =
|
2007-07-09 18:42:24 +00:00
|
|
|
(unsigned long) addr + image_size - 1;
|
2006-10-04 21:49:52 +00:00
|
|
|
dev->resource[PCI_ROM_RESOURCE].flags |= IORESOURCE_ROM_BIOS_COPY;
|
|
|
|
}
|
2007-01-30 06:17:37 +00:00
|
|
|
sn_pci_fixup_slot(dev, pcidev_info, sn_irq_info);
|
2006-10-04 21:49:52 +00:00
|
|
|
}
|
|
|
|
|
2007-01-30 06:17:37 +00:00
|
|
|
EXPORT_SYMBOL(sn_acpi_slot_fixup);
|
|
|
|
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
|
2007-01-30 06:17:37 +00:00
|
|
|
/*
|
|
|
|
* sn_acpi_bus_fixup - Perform SN specific setup of software structs
|
|
|
|
* (pcibus_bussoft, pcidev_info) and hardware
|
|
|
|
* registers, for the specified bus and devices under it.
|
|
|
|
*/
|
|
|
|
void
|
|
|
|
sn_acpi_bus_fixup(struct pci_bus *bus)
|
|
|
|
{
|
|
|
|
struct pci_dev *pci_dev = NULL;
|
|
|
|
struct pcibus_bussoft *prom_bussoft_ptr;
|
|
|
|
|
|
|
|
if (!bus->parent) { /* If root bus */
|
|
|
|
prom_bussoft_ptr = sn_get_bussoft_ptr(bus);
|
|
|
|
if (prom_bussoft_ptr == NULL) {
|
|
|
|
printk(KERN_ERR
|
|
|
|
"%s: 0x%04x:0x%02x Unable to "
|
|
|
|
"obtain prom_bussoft_ptr\n",
|
2008-03-04 23:15:00 +00:00
|
|
|
__func__, pci_domain_nr(bus), bus->number);
|
2007-01-30 06:17:37 +00:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
sn_common_bus_fixup(bus, prom_bussoft_ptr);
|
|
|
|
}
|
|
|
|
list_for_each_entry(pci_dev, &bus->devices, bus_list) {
|
|
|
|
sn_acpi_slot_fixup(pci_dev);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
/*
|
|
|
|
* sn_io_acpi_init - PROM has ACPI support for IO, defining at a minimum the
|
|
|
|
* nodes and root buses in the DSDT. As a result, bus scanning
|
|
|
|
* will be initiated by the Linux ACPI code.
|
|
|
|
*/
|
|
|
|
|
|
|
|
void __init
|
|
|
|
sn_io_acpi_init(void)
|
|
|
|
{
|
|
|
|
u64 result;
|
2009-05-22 20:49:49 +00:00
|
|
|
long status;
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
|
2006-12-22 17:50:04 +00:00
|
|
|
/* SN Altix does not follow the IOSAPIC IRQ routing model */
|
|
|
|
acpi_irq_model = ACPI_IRQ_MODEL_PLATFORM;
|
|
|
|
|
2007-02-23 22:24:16 +00:00
|
|
|
/* Setup hubdev_info for all SGIHUB/SGITIO devices */
|
|
|
|
acpi_get_devices("SGIHUB", sn_acpi_hubdev_init, NULL, NULL);
|
|
|
|
acpi_get_devices("SGITIO", sn_acpi_hubdev_init, NULL, NULL);
|
|
|
|
|
Altix: Add initial ACPI IO support
First phase in introducing ACPI support to SN.
In this phase, when running with an ACPI capable PROM,
the DSDT will define the root busses and all SN nodes
(SGIHUB, SGITIO). An ACPI bus driver will be registered
for the node devices, with the acpi_pci_root_driver being
used for the root busses. An ACPI vendor descriptor is
now used to pass platform specific information for both
nodes and busses, eliminating the need for the current
SAL calls. Also, with ACPI support, SN fixup code is no longer
needed to initiate the PCI bus scans, as the acpi_pci_root_driver
does that.
However, to maintain backward compatibility with non-ACPI capable
PROMs, none of the current 'fixup' code can been deleted, though
much restructuring has been done. For example, the bulk of the code
in io_common.c is relocated code that is now common regardless
of what PROM is running, while io_acpi_init.c and io_init.c contain
routines specific to an ACPI or non ACPI capable PROM respectively.
A new pci bus fixup platform vector has been created to provide
a hook for invoking platform specific bus fixup from pcibios_fixup_bus().
The size of io_space[] has been increased to support systems with
large IO configurations.
Signed-off-by: John Keller <jpk@sgi.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-10-04 21:49:25 +00:00
|
|
|
status = sal_ioif_init(&result);
|
|
|
|
if (status || result)
|
|
|
|
panic("sal_ioif_init failed: [%lx] %s\n",
|
|
|
|
status, ia64_sal_strerror(status));
|
|
|
|
}
|