linux-toradex.git/include/linux/pci.h, branch v2.6.38-rc4

PCI / ACPI: Fix build issue in pci_root.c for !CONFIG_PCIEPORTBUS

2011-01-14T23:23:25+00:00

The compilation of drivers/acpi/pci_root.c fails if
CONFIG_PCIEPORTBUS is unset.  Fix the problem.

Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Linus Torvalds

PCI/PM: Use pm_wakeup_event() directly for reporting wakeup events

2011-01-14T16:55:43+00:00

After recent changes related to wakeup events pm_wakeup_event()
automatically checks if the given device is configured to signal wakeup,
so pci_wakeup_event() may be a static inline function calling
pm_wakeup_event() directly.

Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Jesse Barnes

PCI/ACPI: Request _OSC control once for each root bridge (v3)

2011-01-14T16:55:41+00:00

Move the evaluation of acpi_pci_osc_control_set() (to request control of
PCI Express native features) into acpi_pci_root_add() to avoid calling
it many times for the same root complex with the same arguments.
Additionally, check if all of the requisite _OSC support bits are set
before calling acpi_pci_osc_control_set() for a given root complex.

References: https://bugzilla.kernel.org/show_bug.cgi?id=20232
Reported-by: Ozan Caglayan 
Tested-by: Ozan Caglayan 
Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Jesse Barnes

PCI: make pci_restore_state return void

2010-12-23T20:53:09+00:00

pci_restore_state only ever returns 0, thus there is no benefit in
having it return any value.  Also, a large majority of the callers do
not check the return code of pci_restore_state.  Make the
pci_restore_state a void return and avoid the overhead.

Acked-by: Mauro Carvalho Chehab 
Signed-off-by: Jon Mason 
Signed-off-by: Jesse Barnes

PCI: Export some PCI PM functionality

2010-10-18T03:03:06+00:00

It's helpful to have some extra PCI power management functions available to
platform code, so move the declarations to an exported header.

Acked-by: Rafael J. Wysocki 
Signed-off-by: Matthew Garrett 
Signed-off-by: Jesse Barnes

PCI: pci_driver make name const

2010-10-15T20:09:49+00:00

The name field in pci_driver should be const, it is not
modified by PCI subsystem.

Signed-off-by: Stephen Hemminger 
Signed-off-by: Jesse Barnes

PCI: provide stub pci_domain_nr function for !CONFIG_PCI configs

2010-08-13T23:19:59+00:00

Allows the new PCI domain aware DRM code to compile on m68k.

Reported-by: Geert Uytterhoeven 
Signed-off-by: Dave Airlie 
Signed-off-by: Jesse Barnes

PCI: disable mmio during bar sizing

2010-07-30T16:29:35+00:00

It is a known issue that mmio decoding shall be disabled while doing PCI
bar sizing. Host bridge and other devices (PCI PIC) shall be excluded for
certain platforms. This patch mainly comes from Mathew Willcox's
patch in http://kerneltrap.org/mailarchive/linux-kernel/2007/9/13/258969.

A new flag bit "mmio_alway_on" is added to pci_dev with the intention that
devices with their mmio decoding cannot be disabled during BAR sizing shall
have this bit set, preferrablly in their quirks.

Without this patch, Intel Moorestown platform graphics unit will be
corrupted during bar sizing activities.

Signed-off-by: Jacob Pan 
Signed-off-by: Jesse Barnes

PCI: fall back to original BIOS BAR addresses

2010-07-16T18:39:48+00:00

If we fail to assign resources to a PCI BAR, this patch makes us try the
original address from BIOS rather than leaving it disabled.

Linux tries to make sure all PCI device BARs are inside the upstream
PCI host bridge or P2P bridge apertures, reassigning BARs if necessary.
Windows does similar reassignment.

Before this patch, if we could not move a BAR into an aperture, we left
the resource unassigned, i.e., at address zero.  Windows leaves such BARs
at the original BIOS addresses, and this patch makes Linux do the same.

This is a bit ugly because we disable the resource long before we try to
reassign it, so we have to keep track of the BIOS BAR address somewhere.
For lack of a better place, I put it in the struct pci_dev.

I think it would be cleaner to attempt the assignment immediately when the
claim fails, so we could easily remember the original address.  But we
currently claim motherboard resources in the middle, after attempting to
claim PCI resources and before assigning new PCI resources, and changing
that is a fairly big job.

Addresses https://bugzilla.kernel.org/show_bug.cgi?id=16263

Reported-by: Andrew 
Tested-by: Andrew 
Signed-off-by: Bjorn Helgaas 
Signed-off-by: Jesse Barnes

Merge branch 'linux_next' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/i7core

2010-06-04T22:39:54+00:00

* 'linux_next' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/i7core: (83 commits)
  i7core_edac: Better describe the supported devices
  Add support for Westmere to i7core_edac driver
  i7core_edac: don't free on success
  i7core_edac: Add support for X5670
  Always call i7core_[ur]dimm_check_mc_ecc_err
  i7core_edac: fix memory leak of i7core_dev
  EDAC: add __init to i7core_xeon_pci_fixup
  i7core_edac: Fix wrong device id for channel 1 devices
  i7core: add support for Lynnfield alternate address
  i7core_edac: Add initial support for Lynnfield
  i7core_edac: do not export static functions
  edac: fix i7core build
  edac: i7core_edac produces undefined behaviour on 32bit
  i7core_edac: Use a more generic approach for probing PCI devices
  i7core_edac: PCI device is called NONCORE, instead of NOCORE
  i7core_edac: Fix ringbuffer maxsize
  i7core_edac: First store, then increment
  i7core_edac: Better parse "any" addrmask
  i7core_edac: Use a lockless ringbuffer
  edac: Create an unique instance for each kobj
  ...