src/sys/dev/cardbus, branch releng/10.2 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=releng%2F10.2 2015-04-01T21:48:54Z MFC 261790: 2015-04-01T21:48:54Z John Baldwin jhb@FreeBSD.org 2015-04-01T21:48:54Z urn:sha1:2558ef53a140a2a8c43348bd9356347b8a6b60ba Add support for managing PCI bus numbers. As with BARs and PCI-PCI bridge I/O windows, the default is to preserve the firmware-assigned resources. PCI bus numbers are only managed if NEW_PCIB is enabled and the architecture defines a PCI_RES_BUS resource type. - Add a helper API to create top-level PCI bus resource managers for each PCI domain/segment. Host-PCI bridge drivers use this API to allocate bus numbers from their associated domain. - Change the PCI bus and CardBus drivers to allocate a bus resource for their bus number from the parent PCI bridge device. - Change the PCI-PCI and PCI-CardBus bridge drivers to allocate the full range of bus numbers from secbus to subbus from their parent bridge. The drivers also always program their primary bus register. The bridge drivers also support growing their bus range by extending the bus resource and updating subbus to match the larger range. - Add support for managing PCI bus resources to the Host-PCI bridge drivers used for amd64 and i386 (acpi_pcib, mptable_pcib, legacy_pcib, and qpi_pcib). - Define a PCI_RES_BUS resource type for amd64 and i386. PR: 197076 - Add a bus_dma tag to each PCI bus that is a child of a Host-PCI bridge. 2012-03-02T20:38:04Z John Baldwin jhb@FreeBSD.org 2012-03-02T20:38:04Z urn:sha1:1b1596a3b34a5a8a84fc24d1ef7b1c2d071afaf2 The tag enforces a single restriction that all DMA transactions must not cross a 4GB boundary. Note that while this restriction technically only applies to PCI-express, this change applies it to all PCI devices as it is simpler to implement that way and errs on the side of caution. - Add a softc structure for PCI bus devices to hold the bus_dma tag and a new pci_attach_common() routine that performs actions common to the attach phase of all PCI bus drivers. Right now this only consists of a bootverbose printf and the allocate of a bus_dma tag if necessary. - Adjust all PCI bus drivers to allocate a PCI bus softc and to call pci_attach_common() from their attach routines. MFC after: 2 weeks Mark all SYSCTL_NODEs static that have no corresponding SYSCTL_DECLs. 2011-11-07T15:43:11Z Ed Schouten ed@FreeBSD.org 2011-11-07T15:43:11Z urn:sha1:6472ac3d8a86336899b6cfb789a4cd9897e3fab5 The SYSCTL_NODE macro defines a list that stores all child-elements of that node. If there's no SYSCTL_DECL macro anywhere else, there's no reason why it shouldn't be static. Partially revert 222753: If a CardBus card stores its CIS in a BAR, delete 2011-09-12T15:21:52Z John Baldwin jhb@FreeBSD.org 2011-09-12T15:21:52Z urn:sha1:06c9ee053d10612a3452d396aec23852f4306d6b the BAR after parsing the CIS. This forces the resource range to be reallocated if the BAR is reused by the device. Submitted by: deischen Reviewed by: imp Approved by: re (kib) Minor cleanup: 2011-06-21T22:45:31Z Warner Losh imp@FreeBSD.org 2011-06-21T22:45:31Z urn:sha1:4089559520ae60c6d28d8c3c9895a18c311037d2 o Consider No CIS a normal event and stop whining about it so much (too many cards are like this, espeically usb/firewire cards). o Add comments to the cis reading code. o Made the read from config space a smidge easier to read and eliminate a loop that can be done mathematically. More properly handle Cardbus cards that that store their CIS in a BAR after 2011-06-06T13:21:11Z John Baldwin jhb@FreeBSD.org 2011-06-06T13:21:11Z urn:sha1:0d439b5f93ffc3751cd431eb32953992727bfe1b the recent changes to track BAR state explicitly. The code would now attempt to add the same BAR twice in this case. Instead, change this so that it recognizes this case and only adds it once and do not delete the BAR outright after parsing the CIS. Tested by: bschmidt Don't explicitly list pci_write_ivar() for bus_write_ivar, the method is 2011-05-02T15:01:28Z John Baldwin jhb@FreeBSD.org 2011-05-02T15:01:28Z urn:sha1:8d43fea45f9f1bafb90402093998c614f3e3a8ea already inherited from the PCI bus driver. Move the PCI-specific logic of removing a cardbus device into a 2010-01-05T20:42:25Z John Baldwin jhb@FreeBSD.org 2010-01-05T20:42:25Z urn:sha1:af827f96428cc9f789028215d2232b76ba039d99 pci_delete_child() function called by the cardbus driver. The new function uses resource_list_unreserve() to release the BARs decoded by the device being removed. Reviewed by: imp Tested by: brooks Fix an error case I missed in the previous change so that the CIS resource 2009-12-30T22:34:26Z John Baldwin jhb@FreeBSD.org 2009-12-30T22:34:26Z urn:sha1:3a6b4b04ab8a701413dd31c215fb0a9e9aeffd0a is fully cleaned up if we fail to find the CIS in the devices ROM. Delete the CIS resource after releasing it. This is needed when the CIS is 2009-12-30T20:49:13Z John Baldwin jhb@FreeBSD.org 2009-12-30T20:49:13Z urn:sha1:767dff0ac99b37f758d511ba10d4e538750f546a stored in a BAR since the CIS BAR is mapped before the PCI bus driver enumerates all the BARs. Without this change, the PCI bus driver would attempt to initialize a BAR that was already allocated resulting in a panic.