2005-01-06 01:43:34 +00:00
|
|
|
/*-
|
2017-11-27 14:52:40 +00:00
|
|
|
* SPDX-License-Identifier: BSD-2-Clause-FreeBSD
|
|
|
|
*
|
2019-12-04 08:03:33 +00:00
|
|
|
* Copyright 1997, Stefan Esser <se@freebsd.org>
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
*
|
|
|
|
* 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 unmodified, this list of conditions, and the following
|
|
|
|
* disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
|
|
|
|
* IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
|
|
|
|
* OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
|
|
|
|
* IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
|
|
|
|
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
|
|
|
* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
* DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
* THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
* (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
|
|
|
* THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
*
|
1999-08-28 01:08:13 +00:00
|
|
|
* $FreeBSD$
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
1998-09-15 08:21:13 +00:00
|
|
|
#ifndef _PCIVAR_H_
|
2006-12-14 16:53:48 +00:00
|
|
|
#define _PCIVAR_H_
|
1998-09-15 08:21:13 +00:00
|
|
|
|
|
|
|
#include <sys/queue.h>
|
Extract eventfilter declarations to sys/_eventfilter.h
This allows replacing "sys/eventfilter.h" includes with "sys/_eventfilter.h"
in other header files (e.g., sys/{bus,conf,cpu}.h) and reduces header
pollution substantially.
EVENTHANDLER_DECLARE and EVENTHANDLER_LIST_DECLAREs were moved out of .c
files into appropriate headers (e.g., sys/proc.h, powernv/opal.h).
As a side effect of reduced header pollution, many .c files and headers no
longer contain needed definitions. The remainder of the patch addresses
adding appropriate includes to fix those files.
LOCK_DEBUG and LOCK_FILE_LINE_ARG are moved to sys/_lock.h, as required by
sys/mutex.h since r326106 (but silently protected by header pollution prior
to this change).
No functional change (intended). Of course, any out of tree modules that
relied on header pollution for sys/eventhandler.h, sys/lock.h, or
sys/mutex.h inclusion need to be fixed. __FreeBSD_version has been bumped.
2019-05-20 00:38:23 +00:00
|
|
|
#include <sys/_eventhandler.h>
|
1998-09-15 08:21:13 +00:00
|
|
|
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
/* some PCI bus constants */
|
2006-12-14 16:53:48 +00:00
|
|
|
#define PCI_MAXMAPS_0 6 /* max. no. of memory/port maps */
|
|
|
|
#define PCI_MAXMAPS_1 2 /* max. no. of maps for PCI to PCI bridge */
|
|
|
|
#define PCI_MAXMAPS_2 1 /* max. no. of maps for CardBus bridge */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2006-10-30 19:18:46 +00:00
|
|
|
typedef uint64_t pci_addr_t;
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2015-04-22 22:02:27 +00:00
|
|
|
/* Config registers for PCI-PCI and PCI-Cardbus bridges. */
|
|
|
|
struct pcicfg_bridge {
|
|
|
|
uint8_t br_seclat;
|
|
|
|
uint8_t br_subbus;
|
|
|
|
uint8_t br_secbus;
|
|
|
|
uint8_t br_pribus;
|
|
|
|
uint16_t br_control;
|
|
|
|
};
|
|
|
|
|
2003-09-14 19:30:00 +00:00
|
|
|
/* Interesting values for PCI power management */
|
|
|
|
struct pcicfg_pp {
|
|
|
|
uint16_t pp_cap; /* PCI power management capabilities */
|
2010-10-20 23:41:16 +00:00
|
|
|
uint8_t pp_status; /* conf. space addr. of PM control/status reg */
|
|
|
|
uint8_t pp_bse; /* conf. space addr. of PM BSE reg */
|
|
|
|
uint8_t pp_data; /* conf. space addr. of PM data reg */
|
2003-09-14 19:30:00 +00:00
|
|
|
};
|
2011-03-31 13:22:12 +00:00
|
|
|
|
|
|
|
struct pci_map {
|
|
|
|
pci_addr_t pm_value; /* Raw BAR value */
|
|
|
|
pci_addr_t pm_size;
|
2015-03-01 00:40:26 +00:00
|
|
|
uint16_t pm_reg;
|
2011-03-31 13:22:12 +00:00
|
|
|
STAILQ_ENTRY(pci_map) pm_link;
|
|
|
|
};
|
|
|
|
|
2006-10-09 16:15:56 +00:00
|
|
|
struct vpd_readonly {
|
|
|
|
char keyword[2];
|
|
|
|
char *value;
|
2014-01-20 20:56:09 +00:00
|
|
|
int len;
|
2006-10-09 16:15:56 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
struct vpd_write {
|
|
|
|
char keyword[2];
|
|
|
|
char *value;
|
|
|
|
int start;
|
|
|
|
int len;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct pcicfg_vpd {
|
|
|
|
uint8_t vpd_reg; /* base register, + 2 for addr, + 4 data */
|
2007-03-26 20:18:52 +00:00
|
|
|
char vpd_cached;
|
2006-10-09 16:15:56 +00:00
|
|
|
char *vpd_ident; /* string identifier */
|
|
|
|
int vpd_rocnt;
|
|
|
|
struct vpd_readonly *vpd_ros;
|
|
|
|
int vpd_wcnt;
|
|
|
|
struct vpd_write *vpd_w;
|
|
|
|
};
|
|
|
|
|
2003-09-14 19:30:00 +00:00
|
|
|
/* Interesting values for PCI MSI */
|
|
|
|
struct pcicfg_msi {
|
|
|
|
uint16_t msi_ctrl; /* Message Control */
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
uint8_t msi_location; /* Offset of MSI capability registers. */
|
2003-09-14 19:30:00 +00:00
|
|
|
uint8_t msi_msgnum; /* Number of messages */
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
int msi_alloc; /* Number of allocated messages. */
|
|
|
|
uint64_t msi_addr; /* Contents of address register. */
|
|
|
|
uint16_t msi_data; /* Contents of data register. */
|
2007-05-02 17:50:36 +00:00
|
|
|
u_int msi_handlers;
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
};
|
|
|
|
|
2006-11-14 17:54:55 +00:00
|
|
|
/* Interesting values for PCI MSI-X */
|
2007-05-02 17:50:36 +00:00
|
|
|
struct msix_vector {
|
|
|
|
uint64_t mv_address; /* Contents of address register. */
|
|
|
|
uint32_t mv_data; /* Contents of data register. */
|
|
|
|
int mv_irq;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct msix_table_entry {
|
|
|
|
u_int mte_vector; /* 1-based index into msix_vectors array. */
|
|
|
|
u_int mte_handlers;
|
|
|
|
};
|
|
|
|
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
struct pcicfg_msix {
|
|
|
|
uint16_t msix_ctrl; /* Message Control */
|
|
|
|
uint16_t msix_msgnum; /* Number of messages */
|
2007-05-02 17:50:36 +00:00
|
|
|
uint8_t msix_location; /* Offset of MSI-X capability registers. */
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
uint8_t msix_table_bar; /* BAR containing vector table. */
|
|
|
|
uint8_t msix_pba_bar; /* BAR containing PBA. */
|
|
|
|
uint32_t msix_table_offset;
|
|
|
|
uint32_t msix_pba_offset;
|
2007-05-02 17:50:36 +00:00
|
|
|
int msix_alloc; /* Number of allocated vectors. */
|
|
|
|
int msix_table_len; /* Length of virtual table. */
|
|
|
|
struct msix_table_entry *msix_table; /* Virtual table. */
|
|
|
|
struct msix_vector *msix_vectors; /* Array of allocated vectors. */
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
struct resource *msix_table_res; /* Resource containing vector table. */
|
|
|
|
struct resource *msix_pba_res; /* Resource containing PBA. */
|
2003-09-14 19:30:00 +00:00
|
|
|
};
|
|
|
|
|
2022-05-07 09:17:43 +00:00
|
|
|
struct pci_id_ofw_iommu {
|
|
|
|
uint32_t id;
|
|
|
|
uint32_t xref;
|
|
|
|
};
|
|
|
|
|
2008-07-23 09:44:36 +00:00
|
|
|
/* Interesting values for HyperTransport */
|
|
|
|
struct pcicfg_ht {
|
2011-03-18 12:13:04 +00:00
|
|
|
uint8_t ht_slave; /* Non-zero if device is an HT slave. */
|
2008-07-23 09:44:36 +00:00
|
|
|
uint8_t ht_msimap; /* Offset of MSI mapping cap registers. */
|
|
|
|
uint16_t ht_msictrl; /* MSI mapping control */
|
|
|
|
uint64_t ht_msiaddr; /* MSI mapping base address */
|
|
|
|
};
|
|
|
|
|
2012-03-03 18:08:57 +00:00
|
|
|
/* Interesting values for PCI-express */
|
|
|
|
struct pcicfg_pcie {
|
|
|
|
uint8_t pcie_location; /* Offset of PCI-e capability registers. */
|
|
|
|
uint8_t pcie_type; /* Device type. */
|
2012-03-08 21:09:34 +00:00
|
|
|
uint16_t pcie_flags; /* Device capabilities register. */
|
|
|
|
uint16_t pcie_device_ctl; /* Device control register. */
|
|
|
|
uint16_t pcie_link_ctl; /* Link control register. */
|
|
|
|
uint16_t pcie_slot_ctl; /* Slot control register. */
|
|
|
|
uint16_t pcie_root_ctl; /* Root control register. */
|
|
|
|
uint16_t pcie_device_ctl2; /* Second device control register. */
|
|
|
|
uint16_t pcie_link_ctl2; /* Second link control register. */
|
|
|
|
uint16_t pcie_slot_ctl2; /* Second slot control register. */
|
|
|
|
};
|
|
|
|
|
|
|
|
struct pcicfg_pcix {
|
|
|
|
uint16_t pcix_command;
|
|
|
|
uint8_t pcix_location; /* Offset of PCI-X capability registers. */
|
2012-03-03 18:08:57 +00:00
|
|
|
};
|
|
|
|
|
2015-03-01 00:40:09 +00:00
|
|
|
struct pcicfg_vf {
|
|
|
|
int index;
|
|
|
|
};
|
|
|
|
|
2016-03-02 09:54:58 +00:00
|
|
|
struct pci_ea_entry {
|
|
|
|
int eae_bei;
|
|
|
|
uint32_t eae_flags;
|
|
|
|
uint64_t eae_base;
|
|
|
|
uint64_t eae_max_offset;
|
|
|
|
uint32_t eae_cfg_offset;
|
|
|
|
STAILQ_ENTRY(pci_ea_entry) eae_link;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct pcicfg_ea {
|
|
|
|
int ea_location; /* Structure offset in Configuration Header */
|
|
|
|
STAILQ_HEAD(, pci_ea_entry) ea_entries; /* EA entries */
|
|
|
|
};
|
|
|
|
|
2015-03-01 00:40:09 +00:00
|
|
|
#define PCICFG_VF 0x0001 /* Device is an SR-IOV Virtual Function */
|
|
|
|
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
/* config header information common to all header types */
|
|
|
|
typedef struct pcicfg {
|
2016-08-09 19:32:06 +00:00
|
|
|
device_t dev; /* device which owns this */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2011-03-31 13:22:12 +00:00
|
|
|
STAILQ_HEAD(, pci_map) maps; /* BARs */
|
2004-04-07 20:46:16 +00:00
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
uint16_t subvendor; /* card vendor ID */
|
|
|
|
uint16_t subdevice; /* card device ID, assigned by card vendor */
|
|
|
|
uint16_t vendor; /* chip vendor ID */
|
|
|
|
uint16_t device; /* chip device ID, assigned by chip vendor */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
uint16_t cmdreg; /* disable/enable chip and PCI options */
|
|
|
|
uint16_t statreg; /* supported PCI features and error state */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
uint8_t baseclass; /* chip PCI class */
|
|
|
|
uint8_t subclass; /* chip PCI subclass */
|
|
|
|
uint8_t progif; /* chip PCI programming interface */
|
|
|
|
uint8_t revid; /* chip revision ID */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
uint8_t hdrtype; /* chip config header type */
|
|
|
|
uint8_t cachelnsz; /* cache line size in 4byte units */
|
|
|
|
uint8_t intpin; /* PCI interrupt pin */
|
|
|
|
uint8_t intline; /* interrupt line (IRQ for PC arch) */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
uint8_t mingnt; /* min. useful bus grant time in 250ns units */
|
|
|
|
uint8_t maxlat; /* max. tolerated bus grant latency in 250ns */
|
|
|
|
uint8_t lattimer; /* latency timer in units of 30ns bus cycles */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
uint8_t mfdev; /* multi-function device (from hdrtype reg) */
|
|
|
|
uint8_t nummaps; /* actual number of PCI maps used */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2007-09-30 11:05:18 +00:00
|
|
|
uint32_t domain; /* PCI domain */
|
2003-08-22 03:11:53 +00:00
|
|
|
uint8_t bus; /* config space bus address */
|
|
|
|
uint8_t slot; /* config space slot address */
|
|
|
|
uint8_t func; /* config space function number */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2015-03-01 00:40:09 +00:00
|
|
|
uint32_t flags; /* flags defined above */
|
|
|
|
|
2015-04-22 22:02:27 +00:00
|
|
|
struct pcicfg_bridge bridge; /* Bridges */
|
2009-06-01 20:27:14 +00:00
|
|
|
struct pcicfg_pp pp; /* Power management */
|
|
|
|
struct pcicfg_vpd vpd; /* Vital product data */
|
|
|
|
struct pcicfg_msi msi; /* PCI MSI */
|
|
|
|
struct pcicfg_msix msix; /* PCI MSI-X */
|
2008-07-23 09:44:36 +00:00
|
|
|
struct pcicfg_ht ht; /* HyperTransport */
|
2012-03-03 18:08:57 +00:00
|
|
|
struct pcicfg_pcie pcie; /* PCI Express */
|
2012-03-08 21:09:34 +00:00
|
|
|
struct pcicfg_pcix pcix; /* PCI-X */
|
2015-03-01 00:40:09 +00:00
|
|
|
struct pcicfg_iov *iov; /* SR-IOV */
|
|
|
|
struct pcicfg_vf vf; /* SR-IOV Virtual Function */
|
2016-03-02 09:54:58 +00:00
|
|
|
struct pcicfg_ea ea; /* Enhanced Allocation */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
} pcicfgregs;
|
|
|
|
|
|
|
|
/* additional type 1 device config header information (PCI to PCI bridge) */
|
|
|
|
|
|
|
|
typedef struct {
|
|
|
|
pci_addr_t pmembase; /* base address of prefetchable memory */
|
|
|
|
pci_addr_t pmemlimit; /* topmost address of prefetchable memory */
|
2003-08-22 03:11:53 +00:00
|
|
|
uint32_t membase; /* base address of memory window */
|
|
|
|
uint32_t memlimit; /* topmost address of memory window */
|
|
|
|
uint32_t iobase; /* base address of port window */
|
|
|
|
uint32_t iolimit; /* topmost address of port window */
|
|
|
|
uint16_t secstat; /* secondary bus status register */
|
|
|
|
uint16_t bridgectl; /* bridge control register */
|
|
|
|
uint8_t seclat; /* CardBus latency timer */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
} pcih1cfgregs;
|
|
|
|
|
|
|
|
/* additional type 2 device config header information (CardBus bridge) */
|
|
|
|
|
|
|
|
typedef struct {
|
2003-08-22 03:11:53 +00:00
|
|
|
uint32_t membase0; /* base address of memory window */
|
|
|
|
uint32_t memlimit0; /* topmost address of memory window */
|
|
|
|
uint32_t membase1; /* base address of memory window */
|
|
|
|
uint32_t memlimit1; /* topmost address of memory window */
|
|
|
|
uint32_t iobase0; /* base address of port window */
|
|
|
|
uint32_t iolimit0; /* topmost address of port window */
|
|
|
|
uint32_t iobase1; /* base address of port window */
|
|
|
|
uint32_t iolimit1; /* topmost address of port window */
|
|
|
|
uint32_t pccardif; /* PC Card 16bit IF legacy more base addr. */
|
|
|
|
uint16_t secstat; /* secondary bus status register */
|
|
|
|
uint16_t bridgectl; /* bridge control register */
|
|
|
|
uint8_t seclat; /* CardBus latency timer */
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
} pcih2cfgregs;
|
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
extern uint32_t pci_numdevs;
|
2020-06-26 19:55:11 +00:00
|
|
|
extern int pci_enable_aspm;
|
1998-09-15 08:21:13 +00:00
|
|
|
|
2019-03-19 15:03:20 +00:00
|
|
|
/*
|
2019-03-19 21:46:21 +00:00
|
|
|
* The bitfield has to be stable and match the fields below (so that
|
|
|
|
* match_flag_vendor must be bit 0) so we have to do the endian dance. We can't
|
|
|
|
* use enums or #define constants because then the macros for subsetting matches
|
|
|
|
* wouldn't work. These tables are parsed by devmatch and others to connect
|
|
|
|
* modules with devices on the PCI bus.
|
2019-03-19 15:03:20 +00:00
|
|
|
*/
|
2018-07-07 15:25:11 +00:00
|
|
|
struct pci_device_table {
|
|
|
|
#if BYTE_ORDER == LITTLE_ENDIAN
|
|
|
|
uint16_t
|
|
|
|
match_flag_vendor:1,
|
|
|
|
match_flag_device:1,
|
|
|
|
match_flag_subvendor:1,
|
|
|
|
match_flag_subdevice:1,
|
|
|
|
match_flag_class:1,
|
|
|
|
match_flag_subclass:1,
|
|
|
|
match_flag_revid:1,
|
|
|
|
match_flag_unused:9;
|
|
|
|
#else
|
|
|
|
uint16_t
|
|
|
|
match_flag_unused:9,
|
|
|
|
match_flag_revid:1,
|
|
|
|
match_flag_subclass:1,
|
|
|
|
match_flag_class:1,
|
|
|
|
match_flag_subdevice:1,
|
|
|
|
match_flag_subvendor:1,
|
|
|
|
match_flag_device:1,
|
|
|
|
match_flag_vendor:1;
|
|
|
|
#endif
|
|
|
|
uint16_t vendor;
|
|
|
|
uint16_t device;
|
|
|
|
uint16_t subvendor;
|
|
|
|
uint16_t subdevice;
|
|
|
|
uint16_t class_id;
|
|
|
|
uint16_t subclass;
|
|
|
|
uint16_t revid;
|
|
|
|
uint16_t unused;
|
|
|
|
uintptr_t driver_data;
|
|
|
|
char *descr;
|
|
|
|
};
|
|
|
|
|
|
|
|
#define PCI_DEV(v, d) \
|
|
|
|
.match_flag_vendor = 1, .vendor = (v), \
|
|
|
|
.match_flag_device = 1, .device = (d)
|
|
|
|
#define PCI_SUBDEV(sv, sd) \
|
|
|
|
.match_flag_subvendor = 1, .subvendor = (sv), \
|
|
|
|
.match_flag_subdevice = 1, .subdevice = (sd)
|
|
|
|
#define PCI_CLASS(x) \
|
|
|
|
.match_flag_class = 1, .class_id = (x)
|
|
|
|
#define PCI_SUBCLASS(x) \
|
|
|
|
.match_flag_subclass = 1, .subclass = (x)
|
|
|
|
#define PCI_REVID(x) \
|
|
|
|
.match_flag_revid = 1, .revid = (x)
|
|
|
|
#define PCI_DESCR(x) \
|
|
|
|
.descr = (x)
|
|
|
|
#define PCI_PNP_STR \
|
|
|
|
"M16:mask;U16:vendor;U16:device;U16:subvendor;U16:subdevice;" \
|
|
|
|
"U16:class;U16:subclass;U16:revid;"
|
|
|
|
#define PCI_PNP_INFO(table) \
|
Reapply, with minor tweaks, r338025, from the original commit:
Remove unused and easy to misuse PNP macro parameter
Inspired by r338025, just remove the element size parameter to the
MODULE_PNP_INFO macro entirely. The 'table' parameter is now required to
have correct pointer (or array) type. Since all invocations of the macro
already had this property and the emitted PNP data continues to include the
element size, there is no functional change.
Mostly done with the coccinelle 'spatch' tool:
$ cat modpnpsize0.cocci
@normaltables@
identifier b,c;
expression a,d,e;
declarer MODULE_PNP_INFO;
@@
MODULE_PNP_INFO(a,b,c,d,
-sizeof(d[0]),
e);
@singletons@
identifier b,c,d;
expression a;
declarer MODULE_PNP_INFO;
@@
MODULE_PNP_INFO(a,b,c,&d,
-sizeof(d),
1);
$ rg -l MODULE_PNP_INFO -- sys | \
xargs spatch --in-place --sp-file modpnpsize0.cocci
(Note that coccinelle invokes diff(1) via a PATH search and expects diff to
tolerate the -B flag, which BSD diff does not. So I had to link gdiff into
PATH as diff to use spatch.)
Tinderbox'd (-DMAKE_JUST_KERNELS).
Approved by: re (glen)
2018-09-26 17:12:14 +00:00
|
|
|
MODULE_PNP_INFO(PCI_PNP_STR, pci, table, table, \
|
2018-07-07 15:25:11 +00:00
|
|
|
sizeof(table) / sizeof(table[0]))
|
|
|
|
|
|
|
|
const struct pci_device_table *pci_match_device(device_t child,
|
|
|
|
const struct pci_device_table *id, size_t nelt);
|
|
|
|
#define PCI_MATCH(child, table) \
|
|
|
|
pci_match_device(child, (table), nitems(table));
|
|
|
|
|
2000-05-28 16:35:57 +00:00
|
|
|
/* Only if the prerequisites are present */
|
|
|
|
#if defined(_SYS_BUS_H_) && defined(_SYS_PCIIO_H_)
|
|
|
|
struct pci_devinfo {
|
|
|
|
STAILQ_ENTRY(pci_devinfo) pci_links;
|
|
|
|
struct resource_list resources;
|
|
|
|
pcicfgregs cfg;
|
|
|
|
struct pci_conf conf;
|
|
|
|
};
|
|
|
|
#endif
|
1998-09-15 08:21:13 +00:00
|
|
|
|
1999-04-16 21:22:55 +00:00
|
|
|
#ifdef _SYS_BUS_H_
|
|
|
|
|
|
|
|
#include "pci_if.h"
|
|
|
|
|
|
|
|
enum pci_device_ivars {
|
2000-12-13 01:25:11 +00:00
|
|
|
PCI_IVAR_SUBVENDOR,
|
|
|
|
PCI_IVAR_SUBDEVICE,
|
|
|
|
PCI_IVAR_VENDOR,
|
|
|
|
PCI_IVAR_DEVICE,
|
|
|
|
PCI_IVAR_DEVID,
|
|
|
|
PCI_IVAR_CLASS,
|
|
|
|
PCI_IVAR_SUBCLASS,
|
|
|
|
PCI_IVAR_PROGIF,
|
|
|
|
PCI_IVAR_REVID,
|
|
|
|
PCI_IVAR_INTPIN,
|
|
|
|
PCI_IVAR_IRQ,
|
2007-09-30 11:05:18 +00:00
|
|
|
PCI_IVAR_DOMAIN,
|
2000-12-13 01:25:11 +00:00
|
|
|
PCI_IVAR_BUS,
|
|
|
|
PCI_IVAR_SLOT,
|
|
|
|
PCI_IVAR_FUNCTION,
|
2002-11-27 06:41:28 +00:00
|
|
|
PCI_IVAR_ETHADDR,
|
2005-09-11 03:22:03 +00:00
|
|
|
PCI_IVAR_CMDREG,
|
|
|
|
PCI_IVAR_CACHELNSZ,
|
|
|
|
PCI_IVAR_MINGNT,
|
|
|
|
PCI_IVAR_MAXLAT,
|
2008-04-12 20:26:07 +00:00
|
|
|
PCI_IVAR_LATTIMER
|
1999-04-16 21:22:55 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Simplified accessors for pci devices
|
|
|
|
*/
|
2006-12-14 16:53:48 +00:00
|
|
|
#define PCI_ACCESSOR(var, ivar, type) \
|
2001-12-21 21:49:57 +00:00
|
|
|
__BUS_ACCESSOR(pci, var, PCI, ivar, type)
|
1999-04-16 21:22:55 +00:00
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
PCI_ACCESSOR(subvendor, SUBVENDOR, uint16_t)
|
|
|
|
PCI_ACCESSOR(subdevice, SUBDEVICE, uint16_t)
|
|
|
|
PCI_ACCESSOR(vendor, VENDOR, uint16_t)
|
|
|
|
PCI_ACCESSOR(device, DEVICE, uint16_t)
|
|
|
|
PCI_ACCESSOR(devid, DEVID, uint32_t)
|
|
|
|
PCI_ACCESSOR(class, CLASS, uint8_t)
|
|
|
|
PCI_ACCESSOR(subclass, SUBCLASS, uint8_t)
|
|
|
|
PCI_ACCESSOR(progif, PROGIF, uint8_t)
|
|
|
|
PCI_ACCESSOR(revid, REVID, uint8_t)
|
|
|
|
PCI_ACCESSOR(intpin, INTPIN, uint8_t)
|
|
|
|
PCI_ACCESSOR(irq, IRQ, uint8_t)
|
2007-09-30 11:05:18 +00:00
|
|
|
PCI_ACCESSOR(domain, DOMAIN, uint32_t)
|
2003-08-22 03:11:53 +00:00
|
|
|
PCI_ACCESSOR(bus, BUS, uint8_t)
|
|
|
|
PCI_ACCESSOR(slot, SLOT, uint8_t)
|
|
|
|
PCI_ACCESSOR(function, FUNCTION, uint8_t)
|
|
|
|
PCI_ACCESSOR(ether, ETHADDR, uint8_t *)
|
2005-09-11 03:22:03 +00:00
|
|
|
PCI_ACCESSOR(cmdreg, CMDREG, uint8_t)
|
|
|
|
PCI_ACCESSOR(cachelnsz, CACHELNSZ, uint8_t)
|
|
|
|
PCI_ACCESSOR(mingnt, MINGNT, uint8_t)
|
|
|
|
PCI_ACCESSOR(maxlat, MAXLAT, uint8_t)
|
|
|
|
PCI_ACCESSOR(lattimer, LATTIMER, uint8_t)
|
1999-04-16 21:22:55 +00:00
|
|
|
|
2000-09-28 00:37:32 +00:00
|
|
|
#undef PCI_ACCESSOR
|
|
|
|
|
2000-12-13 01:25:11 +00:00
|
|
|
/*
|
|
|
|
* Operations on configuration space.
|
|
|
|
*/
|
2003-08-22 03:11:53 +00:00
|
|
|
static __inline uint32_t
|
1999-04-16 21:22:55 +00:00
|
|
|
pci_read_config(device_t dev, int reg, int width)
|
|
|
|
{
|
|
|
|
return PCI_READ_CONFIG(device_get_parent(dev), dev, reg, width);
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline void
|
2003-08-22 03:11:53 +00:00
|
|
|
pci_write_config(device_t dev, int reg, uint32_t val, int width)
|
1999-04-16 21:22:55 +00:00
|
|
|
{
|
|
|
|
PCI_WRITE_CONFIG(device_get_parent(dev), dev, reg, val, width);
|
|
|
|
}
|
|
|
|
|
1999-05-20 15:33:33 +00:00
|
|
|
/*
|
|
|
|
* Ivars for pci bridges.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*typedef enum pci_device_ivars pcib_device_ivars;*/
|
|
|
|
enum pcib_device_ivars {
|
2007-09-30 11:05:18 +00:00
|
|
|
PCIB_IVAR_DOMAIN,
|
2000-08-28 21:48:13 +00:00
|
|
|
PCIB_IVAR_BUS
|
1999-05-20 15:33:33 +00:00
|
|
|
};
|
|
|
|
|
2006-12-14 16:53:48 +00:00
|
|
|
#define PCIB_ACCESSOR(var, ivar, type) \
|
2002-08-19 22:50:08 +00:00
|
|
|
__BUS_ACCESSOR(pcib, var, PCIB, ivar, type)
|
1999-05-20 15:33:33 +00:00
|
|
|
|
2007-09-30 11:05:18 +00:00
|
|
|
PCIB_ACCESSOR(domain, DOMAIN, uint32_t)
|
2003-08-22 03:11:53 +00:00
|
|
|
PCIB_ACCESSOR(bus, BUS, uint32_t)
|
1999-05-20 15:33:33 +00:00
|
|
|
|
2000-09-28 00:37:32 +00:00
|
|
|
#undef PCIB_ACCESSOR
|
|
|
|
|
2002-02-12 01:28:49 +00:00
|
|
|
/*
|
2002-06-07 15:28:16 +00:00
|
|
|
* PCI interrupt validation. Invalid interrupt values such as 0 or 128
|
|
|
|
* on i386 or other platforms should be mapped out in the MD pcireadconf
|
|
|
|
* code and not here, since the only MI invalid IRQ is 255.
|
2002-02-12 01:28:49 +00:00
|
|
|
*/
|
2006-12-14 16:53:48 +00:00
|
|
|
#define PCI_INVALID_IRQ 255
|
|
|
|
#define PCI_INTERRUPT_VALID(x) ((x) != PCI_INVALID_IRQ)
|
2002-02-12 01:28:49 +00:00
|
|
|
|
2000-12-13 01:25:11 +00:00
|
|
|
/*
|
|
|
|
* Convenience functions.
|
|
|
|
*
|
|
|
|
* These should be used in preference to manually manipulating
|
|
|
|
* configuration space.
|
|
|
|
*/
|
2003-04-16 03:15:08 +00:00
|
|
|
static __inline int
|
2001-02-27 23:13:20 +00:00
|
|
|
pci_enable_busmaster(device_t dev)
|
|
|
|
{
|
2003-04-16 03:15:08 +00:00
|
|
|
return(PCI_ENABLE_BUSMASTER(device_get_parent(dev), dev));
|
2001-02-27 23:13:20 +00:00
|
|
|
}
|
|
|
|
|
2003-04-16 03:15:08 +00:00
|
|
|
static __inline int
|
2001-02-27 23:13:20 +00:00
|
|
|
pci_disable_busmaster(device_t dev)
|
|
|
|
{
|
2003-04-16 03:15:08 +00:00
|
|
|
return(PCI_DISABLE_BUSMASTER(device_get_parent(dev), dev));
|
2001-02-27 23:13:20 +00:00
|
|
|
}
|
|
|
|
|
2003-04-16 03:15:08 +00:00
|
|
|
static __inline int
|
2001-02-27 23:13:20 +00:00
|
|
|
pci_enable_io(device_t dev, int space)
|
|
|
|
{
|
2003-04-16 03:15:08 +00:00
|
|
|
return(PCI_ENABLE_IO(device_get_parent(dev), dev, space));
|
2001-02-27 23:13:20 +00:00
|
|
|
}
|
|
|
|
|
2003-04-16 03:15:08 +00:00
|
|
|
static __inline int
|
2001-02-27 23:13:20 +00:00
|
|
|
pci_disable_io(device_t dev, int space)
|
|
|
|
{
|
2003-04-16 03:15:08 +00:00
|
|
|
return(PCI_DISABLE_IO(device_get_parent(dev), dev, space));
|
2001-02-27 23:13:20 +00:00
|
|
|
}
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2006-10-09 16:15:56 +00:00
|
|
|
static __inline int
|
|
|
|
pci_get_vpd_ident(device_t dev, const char **identptr)
|
|
|
|
{
|
|
|
|
return(PCI_GET_VPD_IDENT(device_get_parent(dev), dev, identptr));
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline int
|
2012-03-03 14:25:36 +00:00
|
|
|
pci_get_vpd_readonly(device_t dev, const char *kw, const char **vptr)
|
2006-10-09 16:15:56 +00:00
|
|
|
{
|
2012-03-03 14:25:36 +00:00
|
|
|
return(PCI_GET_VPD_READONLY(device_get_parent(dev), dev, kw, vptr));
|
2006-10-09 16:15:56 +00:00
|
|
|
}
|
|
|
|
|
2005-04-29 02:03:11 +00:00
|
|
|
/*
|
|
|
|
* Check if the address range falls within the VGA defined address range(s)
|
|
|
|
*/
|
|
|
|
static __inline int
|
2016-01-27 02:23:54 +00:00
|
|
|
pci_is_vga_ioport_range(rman_res_t start, rman_res_t end)
|
2005-04-29 02:03:11 +00:00
|
|
|
{
|
2018-07-07 15:25:11 +00:00
|
|
|
|
2005-04-29 02:03:11 +00:00
|
|
|
return (((start >= 0x3b0 && end <= 0x3bb) ||
|
|
|
|
(start >= 0x3c0 && end <= 0x3df)) ? 1 : 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline int
|
2016-01-27 02:23:54 +00:00
|
|
|
pci_is_vga_memory_range(rman_res_t start, rman_res_t end)
|
2005-04-29 02:03:11 +00:00
|
|
|
{
|
|
|
|
|
|
|
|
return ((start >= 0xa0000 && end <= 0xbffff) ? 1 : 0);
|
|
|
|
}
|
|
|
|
|
2000-12-13 01:25:11 +00:00
|
|
|
/*
|
|
|
|
* PCI power states are as defined by ACPI:
|
|
|
|
*
|
|
|
|
* D0 State in which device is on and running. It is receiving full
|
|
|
|
* power from the system and delivering full functionality to the user.
|
|
|
|
* D1 Class-specific low-power state in which device context may or may not
|
|
|
|
* be lost. Buses in D1 cannot do anything to the bus that would force
|
2006-08-04 07:56:35 +00:00
|
|
|
* devices on that bus to lose context.
|
2000-12-13 01:25:11 +00:00
|
|
|
* D2 Class-specific low-power state in which device context may or may
|
|
|
|
* not be lost. Attains greater power savings than D1. Buses in D2
|
2006-08-04 07:56:35 +00:00
|
|
|
* can cause devices on that bus to lose some context. Devices in D2
|
2000-12-13 01:25:11 +00:00
|
|
|
* must be prepared for the bus to be in D2 or higher.
|
|
|
|
* D3 State in which the device is off and not running. Device context is
|
|
|
|
* lost. Power can be removed from the device.
|
|
|
|
*/
|
2006-12-14 16:53:48 +00:00
|
|
|
#define PCI_POWERSTATE_D0 0
|
|
|
|
#define PCI_POWERSTATE_D1 1
|
|
|
|
#define PCI_POWERSTATE_D2 2
|
|
|
|
#define PCI_POWERSTATE_D3 3
|
|
|
|
#define PCI_POWERSTATE_UNKNOWN -1
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2001-02-27 23:13:20 +00:00
|
|
|
static __inline int
|
|
|
|
pci_set_powerstate(device_t dev, int state)
|
|
|
|
{
|
|
|
|
return PCI_SET_POWERSTATE(device_get_parent(dev), dev, state);
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline int
|
|
|
|
pci_get_powerstate(device_t dev)
|
|
|
|
{
|
|
|
|
return PCI_GET_POWERSTATE(device_get_parent(dev), dev);
|
|
|
|
}
|
Completely replace the PCI bus driver code to make it better reflect
reality. There will be a new call interface, but for now the file
pci_compat.c (which is to be deleted, after all drivers are converted)
provides an emulation of the old PCI bus driver functions. The only
change that might be visible to drivers is, that the type pcici_t
(which had been meant to be just a handle, whose exact definition
should not be relied on), has been converted into a pcicfgregs* .
The Tekram AMD SCSI driver bogusly relied on the definition of pcici_t
and has been converted to just call the PCI drivers functions to access
configuration space register, instead of inventing its own ...
This code is by no means complete, but assumed to be fully operational,
and brings the official code base more in line with my development code.
A new generic device descriptor data type has to be agreed on. The PCI
code will then use that data type to provide new functionality:
1) userconfig support
2) "wired" PCI devices
3) conflicts checking against ISA/EISA
4) maps will depend on the command register enable bits
5) PCI to Anything bridges can be defined as devices,
and are probed like any "standard" PCI device.
The following features are currently missing, but will be added back,
soon:
1) unknown device probe message
2) suppression of "mirrored" devices caused by ancient, broken chip-sets
This code relies on generic shared interrupt support just commited to
kern_intr.c (plus the modifications of isa.c and isa_device.h).
1997-05-26 15:08:43 +00:00
|
|
|
|
2011-03-22 12:05:49 +00:00
|
|
|
static __inline int
|
|
|
|
pci_find_cap(device_t dev, int capability, int *capreg)
|
|
|
|
{
|
2012-03-03 18:08:57 +00:00
|
|
|
return (PCI_FIND_CAP(device_get_parent(dev), dev, capability, capreg));
|
2011-03-22 12:05:49 +00:00
|
|
|
}
|
|
|
|
|
2018-02-19 18:41:56 +00:00
|
|
|
static __inline int
|
|
|
|
pci_find_next_cap(device_t dev, int capability, int start, int *capreg)
|
|
|
|
{
|
|
|
|
return (PCI_FIND_NEXT_CAP(device_get_parent(dev), dev, capability, start,
|
|
|
|
capreg));
|
|
|
|
}
|
|
|
|
|
2005-12-20 19:57:47 +00:00
|
|
|
static __inline int
|
|
|
|
pci_find_extcap(device_t dev, int capability, int *capreg)
|
|
|
|
{
|
2011-03-22 12:05:49 +00:00
|
|
|
return (PCI_FIND_EXTCAP(device_get_parent(dev), dev, capability, capreg));
|
2005-12-20 19:57:47 +00:00
|
|
|
}
|
|
|
|
|
2018-02-19 18:41:56 +00:00
|
|
|
static __inline int
|
|
|
|
pci_find_next_extcap(device_t dev, int capability, int start, int *capreg)
|
|
|
|
{
|
|
|
|
return (PCI_FIND_NEXT_EXTCAP(device_get_parent(dev), dev, capability,
|
|
|
|
start, capreg));
|
|
|
|
}
|
|
|
|
|
2012-03-03 18:08:57 +00:00
|
|
|
static __inline int
|
|
|
|
pci_find_htcap(device_t dev, int capability, int *capreg)
|
|
|
|
{
|
|
|
|
return (PCI_FIND_HTCAP(device_get_parent(dev), dev, capability, capreg));
|
|
|
|
}
|
|
|
|
|
2018-02-19 18:41:56 +00:00
|
|
|
static __inline int
|
|
|
|
pci_find_next_htcap(device_t dev, int capability, int start, int *capreg)
|
|
|
|
{
|
|
|
|
return (PCI_FIND_NEXT_HTCAP(device_get_parent(dev), dev, capability,
|
|
|
|
start, capreg));
|
|
|
|
}
|
|
|
|
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
static __inline int
|
|
|
|
pci_alloc_msi(device_t dev, int *count)
|
|
|
|
{
|
|
|
|
return (PCI_ALLOC_MSI(device_get_parent(dev), dev, count));
|
|
|
|
}
|
|
|
|
|
Expand the MSI/MSI-X API to address some deficiencies in the MSI-X support.
- First off, device drivers really do need to know if they are allocating
MSI or MSI-X messages. MSI requires allocating powerof2() messages for
example where MSI-X does not. To address this, split out the MSI-X
support from pci_msi_count() and pci_alloc_msi() into new driver-visible
functions pci_msix_count() and pci_alloc_msix(). As a result,
pci_msi_count() now just returns a count of the max supported MSI
messages for the device, and pci_alloc_msi() only tries to allocate MSI
messages. To get a count of the max supported MSI-X messages, use
pci_msix_count(). To allocate MSI-X messages, use pci_alloc_msix().
pci_release_msi() still handles both MSI and MSI-X messages, however.
As a result of this change, drivers using the existing API will only
use MSI messages and will no longer try to use MSI-X messages.
- Because MSI-X allows for each message to have its own data and address
values (and thus does not require all of the messages to have their
MD vectors allocated as a group), some devices allow for "sparse" use
of MSI-X message slots. For example, if a device supports 8 messages
but the OS is only able to allocate 2 messages, the device may make the
best use of 2 IRQs if it enables the messages at slots 1 and 4 rather
than default of using the first N slots (or indicies) at 1 and 2. To
support this, add a new pci_remap_msix() function that a driver may call
after a successful pci_alloc_msix() (but before allocating any of the
SYS_RES_IRQ resources) to allow the allocated IRQ resources to be
assigned to different message indices. For example, from the earlier
example, after pci_alloc_msix() returned a value of 2, the driver would
call pci_remap_msix() passing in array of integers { 1, 4 } as the
new message indices to use. The rid's for the SYS_RES_IRQ resources
will always match the message indices. Thus, after the call to
pci_remap_msix() the driver would be able to access the first message
in slot 1 at SYS_RES_IRQ rid 1, and the second message at slot 4 at
SYS_RES_IRQ rid 4. Note that the message slots/indices are 1-based
rather than 0-based so that they will always correspond to the rid
values (SYS_RES_IRQ rid 0 is reserved for the legacy INTx interrupt).
To support this API, a new PCIB_REMAP_MSIX() method was added to the
pcib interface to change the message index for a single IRQ.
Tested by: scottl
2007-01-22 21:48:44 +00:00
|
|
|
static __inline int
|
|
|
|
pci_alloc_msix(device_t dev, int *count)
|
|
|
|
{
|
|
|
|
return (PCI_ALLOC_MSIX(device_get_parent(dev), dev, count));
|
|
|
|
}
|
|
|
|
|
2014-08-20 14:57:20 +00:00
|
|
|
static __inline void
|
|
|
|
pci_enable_msi(device_t dev, uint64_t address, uint16_t data)
|
|
|
|
{
|
|
|
|
PCI_ENABLE_MSI(device_get_parent(dev), dev, address, data);
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline void
|
|
|
|
pci_enable_msix(device_t dev, u_int index, uint64_t address, uint32_t data)
|
|
|
|
{
|
|
|
|
PCI_ENABLE_MSIX(device_get_parent(dev), dev, index, address, data);
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline void
|
|
|
|
pci_disable_msi(device_t dev)
|
|
|
|
{
|
|
|
|
PCI_DISABLE_MSI(device_get_parent(dev), dev);
|
|
|
|
}
|
|
|
|
|
Expand the MSI/MSI-X API to address some deficiencies in the MSI-X support.
- First off, device drivers really do need to know if they are allocating
MSI or MSI-X messages. MSI requires allocating powerof2() messages for
example where MSI-X does not. To address this, split out the MSI-X
support from pci_msi_count() and pci_alloc_msi() into new driver-visible
functions pci_msix_count() and pci_alloc_msix(). As a result,
pci_msi_count() now just returns a count of the max supported MSI
messages for the device, and pci_alloc_msi() only tries to allocate MSI
messages. To get a count of the max supported MSI-X messages, use
pci_msix_count(). To allocate MSI-X messages, use pci_alloc_msix().
pci_release_msi() still handles both MSI and MSI-X messages, however.
As a result of this change, drivers using the existing API will only
use MSI messages and will no longer try to use MSI-X messages.
- Because MSI-X allows for each message to have its own data and address
values (and thus does not require all of the messages to have their
MD vectors allocated as a group), some devices allow for "sparse" use
of MSI-X message slots. For example, if a device supports 8 messages
but the OS is only able to allocate 2 messages, the device may make the
best use of 2 IRQs if it enables the messages at slots 1 and 4 rather
than default of using the first N slots (or indicies) at 1 and 2. To
support this, add a new pci_remap_msix() function that a driver may call
after a successful pci_alloc_msix() (but before allocating any of the
SYS_RES_IRQ resources) to allow the allocated IRQ resources to be
assigned to different message indices. For example, from the earlier
example, after pci_alloc_msix() returned a value of 2, the driver would
call pci_remap_msix() passing in array of integers { 1, 4 } as the
new message indices to use. The rid's for the SYS_RES_IRQ resources
will always match the message indices. Thus, after the call to
pci_remap_msix() the driver would be able to access the first message
in slot 1 at SYS_RES_IRQ rid 1, and the second message at slot 4 at
SYS_RES_IRQ rid 4. Note that the message slots/indices are 1-based
rather than 0-based so that they will always correspond to the rid
values (SYS_RES_IRQ rid 0 is reserved for the legacy INTx interrupt).
To support this API, a new PCIB_REMAP_MSIX() method was added to the
pcib interface to change the message index for a single IRQ.
Tested by: scottl
2007-01-22 21:48:44 +00:00
|
|
|
static __inline int
|
2007-05-02 17:50:36 +00:00
|
|
|
pci_remap_msix(device_t dev, int count, const u_int *vectors)
|
Expand the MSI/MSI-X API to address some deficiencies in the MSI-X support.
- First off, device drivers really do need to know if they are allocating
MSI or MSI-X messages. MSI requires allocating powerof2() messages for
example where MSI-X does not. To address this, split out the MSI-X
support from pci_msi_count() and pci_alloc_msi() into new driver-visible
functions pci_msix_count() and pci_alloc_msix(). As a result,
pci_msi_count() now just returns a count of the max supported MSI
messages for the device, and pci_alloc_msi() only tries to allocate MSI
messages. To get a count of the max supported MSI-X messages, use
pci_msix_count(). To allocate MSI-X messages, use pci_alloc_msix().
pci_release_msi() still handles both MSI and MSI-X messages, however.
As a result of this change, drivers using the existing API will only
use MSI messages and will no longer try to use MSI-X messages.
- Because MSI-X allows for each message to have its own data and address
values (and thus does not require all of the messages to have their
MD vectors allocated as a group), some devices allow for "sparse" use
of MSI-X message slots. For example, if a device supports 8 messages
but the OS is only able to allocate 2 messages, the device may make the
best use of 2 IRQs if it enables the messages at slots 1 and 4 rather
than default of using the first N slots (or indicies) at 1 and 2. To
support this, add a new pci_remap_msix() function that a driver may call
after a successful pci_alloc_msix() (but before allocating any of the
SYS_RES_IRQ resources) to allow the allocated IRQ resources to be
assigned to different message indices. For example, from the earlier
example, after pci_alloc_msix() returned a value of 2, the driver would
call pci_remap_msix() passing in array of integers { 1, 4 } as the
new message indices to use. The rid's for the SYS_RES_IRQ resources
will always match the message indices. Thus, after the call to
pci_remap_msix() the driver would be able to access the first message
in slot 1 at SYS_RES_IRQ rid 1, and the second message at slot 4 at
SYS_RES_IRQ rid 4. Note that the message slots/indices are 1-based
rather than 0-based so that they will always correspond to the rid
values (SYS_RES_IRQ rid 0 is reserved for the legacy INTx interrupt).
To support this API, a new PCIB_REMAP_MSIX() method was added to the
pcib interface to change the message index for a single IRQ.
Tested by: scottl
2007-01-22 21:48:44 +00:00
|
|
|
{
|
2007-05-02 17:50:36 +00:00
|
|
|
return (PCI_REMAP_MSIX(device_get_parent(dev), dev, count, vectors));
|
Expand the MSI/MSI-X API to address some deficiencies in the MSI-X support.
- First off, device drivers really do need to know if they are allocating
MSI or MSI-X messages. MSI requires allocating powerof2() messages for
example where MSI-X does not. To address this, split out the MSI-X
support from pci_msi_count() and pci_alloc_msi() into new driver-visible
functions pci_msix_count() and pci_alloc_msix(). As a result,
pci_msi_count() now just returns a count of the max supported MSI
messages for the device, and pci_alloc_msi() only tries to allocate MSI
messages. To get a count of the max supported MSI-X messages, use
pci_msix_count(). To allocate MSI-X messages, use pci_alloc_msix().
pci_release_msi() still handles both MSI and MSI-X messages, however.
As a result of this change, drivers using the existing API will only
use MSI messages and will no longer try to use MSI-X messages.
- Because MSI-X allows for each message to have its own data and address
values (and thus does not require all of the messages to have their
MD vectors allocated as a group), some devices allow for "sparse" use
of MSI-X message slots. For example, if a device supports 8 messages
but the OS is only able to allocate 2 messages, the device may make the
best use of 2 IRQs if it enables the messages at slots 1 and 4 rather
than default of using the first N slots (or indicies) at 1 and 2. To
support this, add a new pci_remap_msix() function that a driver may call
after a successful pci_alloc_msix() (but before allocating any of the
SYS_RES_IRQ resources) to allow the allocated IRQ resources to be
assigned to different message indices. For example, from the earlier
example, after pci_alloc_msix() returned a value of 2, the driver would
call pci_remap_msix() passing in array of integers { 1, 4 } as the
new message indices to use. The rid's for the SYS_RES_IRQ resources
will always match the message indices. Thus, after the call to
pci_remap_msix() the driver would be able to access the first message
in slot 1 at SYS_RES_IRQ rid 1, and the second message at slot 4 at
SYS_RES_IRQ rid 4. Note that the message slots/indices are 1-based
rather than 0-based so that they will always correspond to the rid
values (SYS_RES_IRQ rid 0 is reserved for the legacy INTx interrupt).
To support this API, a new PCIB_REMAP_MSIX() method was added to the
pcib interface to change the message index for a single IRQ.
Tested by: scottl
2007-01-22 21:48:44 +00:00
|
|
|
}
|
|
|
|
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
static __inline int
|
|
|
|
pci_release_msi(device_t dev)
|
|
|
|
{
|
|
|
|
return (PCI_RELEASE_MSI(device_get_parent(dev), dev));
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline int
|
|
|
|
pci_msi_count(device_t dev)
|
|
|
|
{
|
|
|
|
return (PCI_MSI_COUNT(device_get_parent(dev), dev));
|
|
|
|
}
|
|
|
|
|
Expand the MSI/MSI-X API to address some deficiencies in the MSI-X support.
- First off, device drivers really do need to know if they are allocating
MSI or MSI-X messages. MSI requires allocating powerof2() messages for
example where MSI-X does not. To address this, split out the MSI-X
support from pci_msi_count() and pci_alloc_msi() into new driver-visible
functions pci_msix_count() and pci_alloc_msix(). As a result,
pci_msi_count() now just returns a count of the max supported MSI
messages for the device, and pci_alloc_msi() only tries to allocate MSI
messages. To get a count of the max supported MSI-X messages, use
pci_msix_count(). To allocate MSI-X messages, use pci_alloc_msix().
pci_release_msi() still handles both MSI and MSI-X messages, however.
As a result of this change, drivers using the existing API will only
use MSI messages and will no longer try to use MSI-X messages.
- Because MSI-X allows for each message to have its own data and address
values (and thus does not require all of the messages to have their
MD vectors allocated as a group), some devices allow for "sparse" use
of MSI-X message slots. For example, if a device supports 8 messages
but the OS is only able to allocate 2 messages, the device may make the
best use of 2 IRQs if it enables the messages at slots 1 and 4 rather
than default of using the first N slots (or indicies) at 1 and 2. To
support this, add a new pci_remap_msix() function that a driver may call
after a successful pci_alloc_msix() (but before allocating any of the
SYS_RES_IRQ resources) to allow the allocated IRQ resources to be
assigned to different message indices. For example, from the earlier
example, after pci_alloc_msix() returned a value of 2, the driver would
call pci_remap_msix() passing in array of integers { 1, 4 } as the
new message indices to use. The rid's for the SYS_RES_IRQ resources
will always match the message indices. Thus, after the call to
pci_remap_msix() the driver would be able to access the first message
in slot 1 at SYS_RES_IRQ rid 1, and the second message at slot 4 at
SYS_RES_IRQ rid 4. Note that the message slots/indices are 1-based
rather than 0-based so that they will always correspond to the rid
values (SYS_RES_IRQ rid 0 is reserved for the legacy INTx interrupt).
To support this API, a new PCIB_REMAP_MSIX() method was added to the
pcib interface to change the message index for a single IRQ.
Tested by: scottl
2007-01-22 21:48:44 +00:00
|
|
|
static __inline int
|
|
|
|
pci_msix_count(device_t dev)
|
|
|
|
{
|
|
|
|
return (PCI_MSIX_COUNT(device_get_parent(dev), dev));
|
2015-12-23 21:51:10 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static __inline int
|
|
|
|
pci_msix_pba_bar(device_t dev)
|
|
|
|
{
|
|
|
|
return (PCI_MSIX_PBA_BAR(device_get_parent(dev), dev));
|
|
|
|
}
|
|
|
|
|
|
|
|
static __inline int
|
|
|
|
pci_msix_table_bar(device_t dev)
|
|
|
|
{
|
|
|
|
return (PCI_MSIX_TABLE_BAR(device_get_parent(dev), dev));
|
Expand the MSI/MSI-X API to address some deficiencies in the MSI-X support.
- First off, device drivers really do need to know if they are allocating
MSI or MSI-X messages. MSI requires allocating powerof2() messages for
example where MSI-X does not. To address this, split out the MSI-X
support from pci_msi_count() and pci_alloc_msi() into new driver-visible
functions pci_msix_count() and pci_alloc_msix(). As a result,
pci_msi_count() now just returns a count of the max supported MSI
messages for the device, and pci_alloc_msi() only tries to allocate MSI
messages. To get a count of the max supported MSI-X messages, use
pci_msix_count(). To allocate MSI-X messages, use pci_alloc_msix().
pci_release_msi() still handles both MSI and MSI-X messages, however.
As a result of this change, drivers using the existing API will only
use MSI messages and will no longer try to use MSI-X messages.
- Because MSI-X allows for each message to have its own data and address
values (and thus does not require all of the messages to have their
MD vectors allocated as a group), some devices allow for "sparse" use
of MSI-X message slots. For example, if a device supports 8 messages
but the OS is only able to allocate 2 messages, the device may make the
best use of 2 IRQs if it enables the messages at slots 1 and 4 rather
than default of using the first N slots (or indicies) at 1 and 2. To
support this, add a new pci_remap_msix() function that a driver may call
after a successful pci_alloc_msix() (but before allocating any of the
SYS_RES_IRQ resources) to allow the allocated IRQ resources to be
assigned to different message indices. For example, from the earlier
example, after pci_alloc_msix() returned a value of 2, the driver would
call pci_remap_msix() passing in array of integers { 1, 4 } as the
new message indices to use. The rid's for the SYS_RES_IRQ resources
will always match the message indices. Thus, after the call to
pci_remap_msix() the driver would be able to access the first message
in slot 1 at SYS_RES_IRQ rid 1, and the second message at slot 4 at
SYS_RES_IRQ rid 4. Note that the message slots/indices are 1-based
rather than 0-based so that they will always correspond to the rid
values (SYS_RES_IRQ rid 0 is reserved for the legacy INTx interrupt).
To support this API, a new PCIB_REMAP_MSIX() method was added to the
pcib interface to change the message index for a single IRQ.
Tested by: scottl
2007-01-22 21:48:44 +00:00
|
|
|
}
|
|
|
|
|
2016-05-16 09:15:50 +00:00
|
|
|
static __inline int
|
|
|
|
pci_get_id(device_t dev, enum pci_id_type type, uintptr_t *id)
|
|
|
|
{
|
|
|
|
return (PCI_GET_ID(device_get_parent(dev), dev, type, id));
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This is the deprecated interface, there is no way to tell the difference
|
|
|
|
* between a failure and a valid value that happens to be the same as the
|
|
|
|
* failure value.
|
|
|
|
*/
|
2014-04-01 15:47:24 +00:00
|
|
|
static __inline uint16_t
|
|
|
|
pci_get_rid(device_t dev)
|
|
|
|
{
|
2016-05-16 09:15:50 +00:00
|
|
|
uintptr_t rid;
|
|
|
|
|
|
|
|
if (pci_get_id(dev, PCI_ID_RID, &rid) != 0)
|
|
|
|
return (0);
|
|
|
|
|
|
|
|
return (rid);
|
2014-04-01 15:47:24 +00:00
|
|
|
}
|
|
|
|
|
2014-08-22 15:05:51 +00:00
|
|
|
static __inline void
|
|
|
|
pci_child_added(device_t dev)
|
|
|
|
{
|
|
|
|
|
|
|
|
return (PCI_CHILD_ADDED(device_get_parent(dev), dev));
|
|
|
|
}
|
|
|
|
|
2003-08-22 03:11:53 +00:00
|
|
|
device_t pci_find_bsf(uint8_t, uint8_t, uint8_t);
|
2007-09-30 11:05:18 +00:00
|
|
|
device_t pci_find_dbsf(uint32_t, uint8_t, uint8_t, uint8_t);
|
2003-08-22 03:11:53 +00:00
|
|
|
device_t pci_find_device(uint16_t, uint16_t);
|
2011-07-09 14:30:13 +00:00
|
|
|
device_t pci_find_class(uint8_t class, uint8_t subclass);
|
2020-12-10 17:38:41 +00:00
|
|
|
device_t pci_find_class_from(uint8_t class, uint8_t subclass, device_t devfrom);
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
|
2007-05-02 17:50:36 +00:00
|
|
|
/* Can be used by drivers to manage the MSI-X table. */
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
int pci_pending_msix(device_t dev, u_int index);
|
2007-05-02 17:50:36 +00:00
|
|
|
|
2006-12-14 19:57:06 +00:00
|
|
|
int pci_msi_device_blacklisted(device_t dev);
|
2013-07-09 23:12:26 +00:00
|
|
|
int pci_msix_device_blacklisted(device_t dev);
|
First cut at MI support for PCI Message Signalled Interrupts (MSI):
- Add 3 new functions to the pci_if interface along with suitable wrappers
to provide the device driver visible API:
- pci_alloc_msi(dev, int *count) backed by PCI_ALLOC_MSI(). '*count'
here is an in and out parameter. The driver stores the desired number
of messages in '*count' before calling the function. On success,
'*count' holds the number of messages allocated to the device. Also on
success, the driver can access the messages as SYS_RES_IRQ resources
starting at rid 1. Note that the legacy INTx interrupt resource will
not be available when using MSI. Note that this function will allocate
either MSI or MSI-X messages depending on the devices capabilities and
the 'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. Also note
that the driver should activate the memory resource that holds the
MSI-X table and pending bit array (PBA) before calling this function
if the device supports MSI-X.
- pci_release_msi(dev) backed by PCI_RELEASE_MSI(). This function
releases the messages allocated for this device. All of the
SYS_RES_IRQ resources need to be released for this function to succeed.
- pci_msi_count(dev) backed by PCI_MSI_COUNT(). This function returns
the maximum number of MSI or MSI-X messages supported by this device.
MSI-X is preferred if present, but this function will honor the
'hw.pci.enable_msix' and 'hw.pci.enable_msi' tunables. This function
should return the largest value that pci_alloc_msi() can return
(assuming the MD code is able to allocate sufficient backing resources
for all of the messages).
- Add default implementations for these 3 methods to the pci_driver generic
PCI bus driver. (The various other PCI bus drivers such as for ACPI and
OFW will inherit these default implementations.) This default
implementation depends on 4 new pcib_if methods that bubble up through
the PCI bridges to the MD code to allocate IRQ values and perform any
needed MD setup code needed:
- PCIB_ALLOC_MSI() attempts to allocate a group of MSI messages.
- PCIB_RELEASE_MSI() releases a group of MSI messages.
- PCIB_ALLOC_MSIX() attempts to allocate a single MSI-X message.
- PCIB_RELEASE_MSIX() releases a single MSI-X message.
- Add default implementations for these 4 methods that just pass the
request up to the parent bus's parent bridge driver and use the
default implementation in the various MI PCI bridge drivers.
- Add MI functions for use by MD code when managing MSI and MSI-X
interrupts:
- pci_enable_msi(dev, address, data) programs the MSI capability address
and data registers for a group of MSI messages
- pci_enable_msix(dev, index, address, data) initializes a single MSI-X
message in the MSI-X table
- pci_mask_msix(dev, index) masks a single MSI-X message
- pci_unmask_msix(dev, index) unmasks a single MSI-X message
- pci_pending_msix(dev, index) returns true if the specified MSI-X
message is currently pending
- Save the MSI capability address and data registers in the pci_cfgreg
block in a PCI devices ivars and restore the values when a device is
resumed. Note that the MSI-X table is not currently restored during
resume.
- Add constants for MSI-X register offsets and fields.
- Record interesting data about any MSI-X capability blocks we come
across in the pci_cfgreg block in the ivars for PCI devices.
Tested on: em (i386, MSI), bce (amd64/i386, MSI), mpt (amd64, MSI-X)
Reviewed by: scottl, grehan, jfv
MFC after: 2 months
2006-11-13 21:47:30 +00:00
|
|
|
|
2008-07-23 09:44:36 +00:00
|
|
|
void pci_ht_map_msi(device_t dev, uint64_t addr);
|
|
|
|
|
2015-11-05 21:27:25 +00:00
|
|
|
device_t pci_find_pcie_root_port(device_t dev);
|
2021-03-16 15:06:42 +00:00
|
|
|
int pci_get_relaxed_ordering_enabled(device_t dev);
|
2016-06-24 17:26:42 +00:00
|
|
|
int pci_get_max_payload(device_t dev);
|
2010-02-05 17:18:48 +00:00
|
|
|
int pci_get_max_read_req(device_t dev);
|
2012-03-01 20:20:55 +00:00
|
|
|
void pci_restore_state(device_t dev);
|
|
|
|
void pci_save_state(device_t dev);
|
2010-02-05 17:18:48 +00:00
|
|
|
int pci_set_max_read_req(device_t dev, int size);
|
2019-04-05 19:25:26 +00:00
|
|
|
int pci_power_reset(device_t dev);
|
2015-11-05 21:26:06 +00:00
|
|
|
uint32_t pcie_read_config(device_t dev, int reg, int width);
|
|
|
|
void pcie_write_config(device_t dev, int reg, uint32_t value, int width);
|
|
|
|
uint32_t pcie_adjust_config(device_t dev, int reg, uint32_t mask,
|
|
|
|
uint32_t value, int width);
|
2020-07-27 21:19:41 +00:00
|
|
|
void pcie_apei_error(device_t dev, int sev, uint8_t *aer);
|
2016-09-06 21:15:35 +00:00
|
|
|
bool pcie_flr(device_t dev, u_int max_delay, bool force);
|
|
|
|
int pcie_get_max_completion_timeout(device_t dev);
|
|
|
|
bool pcie_wait_for_pending_transactions(device_t dev, u_int max_delay);
|
2019-04-05 19:25:26 +00:00
|
|
|
int pcie_link_reset(device_t port, int pcie_location);
|
2013-10-24 20:21:37 +00:00
|
|
|
|
2018-08-18 20:35:19 +00:00
|
|
|
void pci_print_faulted_dev(void);
|
|
|
|
|
2000-12-13 01:25:11 +00:00
|
|
|
#endif /* _SYS_BUS_H_ */
|
1995-02-01 22:56:55 +00:00
|
|
|
|
2000-12-13 01:25:11 +00:00
|
|
|
/*
|
|
|
|
* cdev switch for control device, initialised in generic PCI code
|
|
|
|
*/
|
|
|
|
extern struct cdevsw pcicdev;
|
1998-07-22 08:39:08 +00:00
|
|
|
|
2000-12-13 01:25:11 +00:00
|
|
|
/*
|
|
|
|
* List of all PCI devices, generation count for the list.
|
|
|
|
*/
|
2001-12-19 08:49:11 +00:00
|
|
|
STAILQ_HEAD(devlist, pci_devinfo);
|
|
|
|
|
|
|
|
extern struct devlist pci_devq;
|
2003-08-22 03:11:53 +00:00
|
|
|
extern uint32_t pci_generation;
|
1999-04-24 19:59:20 +00:00
|
|
|
|
2011-03-31 13:22:12 +00:00
|
|
|
struct pci_map *pci_find_bar(device_t dev, int reg);
|
2022-08-19 21:59:06 +00:00
|
|
|
struct pci_map *pci_first_bar(device_t dev);
|
|
|
|
struct pci_map *pci_next_bar(struct pci_map *pm);
|
2011-03-31 13:22:12 +00:00
|
|
|
int pci_bar_enabled(device_t dev, struct pci_map *pm);
|
2014-01-20 20:56:09 +00:00
|
|
|
struct pcicfg_vpd *pci_fetch_vpd_list(device_t dev);
|
2011-03-31 13:22:12 +00:00
|
|
|
|
2013-08-25 18:09:11 +00:00
|
|
|
#define VGA_PCI_BIOS_SHADOW_ADDR 0xC0000
|
|
|
|
#define VGA_PCI_BIOS_SHADOW_SIZE 131072
|
|
|
|
|
|
|
|
int vga_pci_is_boot_display(device_t dev);
|
|
|
|
void * vga_pci_map_bios(device_t dev, size_t *size);
|
|
|
|
void vga_pci_unmap_bios(device_t dev, void *bios);
|
2015-03-01 12:47:36 +00:00
|
|
|
int vga_pci_repost(device_t dev);
|
2013-08-25 18:09:11 +00:00
|
|
|
|
2016-09-06 20:17:54 +00:00
|
|
|
/**
|
|
|
|
* Global eventhandlers invoked when PCI devices are added or removed
|
|
|
|
* from the system.
|
|
|
|
*/
|
|
|
|
typedef void (*pci_event_fn)(void *arg, device_t dev);
|
|
|
|
EVENTHANDLER_DECLARE(pci_add_device, pci_event_fn);
|
|
|
|
EVENTHANDLER_DECLARE(pci_delete_device, pci_event_fn);
|
|
|
|
|
1998-09-15 08:21:13 +00:00
|
|
|
#endif /* _PCIVAR_H_ */
|