linux-toradex.git/include/linux/pci-acpi.h, branch v3.10.56

PCI: acpiphp: Re-enumerate devices when host bridge receives Bus Check

2013-05-17T20:12:06+00:00

When a PCI host bridge device receives a Bus Check notification, we
must re-enumerate starting with the bridge to discover changes (devices
that have been added or removed).

Prior to 668192b678 ("PCI: acpiphp: Move host bridge hotplug to
pci_root.c"), this happened in _handle_hotplug_event_bridge().  After that
commit, _handle_hotplug_event_bridge() is not installed for host bridges,
and the host bridge notify handler, _handle_hotplug_event_root() did not
re-enumerate.

This patch adds re-enumeration to _handle_hotplug_event_root().

This fixes cases where we don't notice the addition or removal of
PCI devices, e.g., the PCI-to-USB ExpressCard in the bugzilla below.

[bhelgaas: changelog, references]
Reference: https://lkml.kernel.org/r/CAAh6nkmbKR3HTqm5ommevsBwhL_u0N8Rk7Wsms_LfP=nBgKNew@mail.gmail.com
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=57961
Reported-by: Gavin Guo 
Tested-by: Gavin Guo 
Signed-off-by: Yinghai Lu 
Signed-off-by: Bjorn Helgaas 
Reviewed-by: Jiang Liu 
Acked-by: Rafael J. Wysocki 
CC: stable@vger.kernel.org	# v3.9+

PCI: acpiphp: Do not use ACPI PCI subdriver mechanism

2013-04-12T22:52:01+00:00

Previously the acpiphp driver registered itself as an ACPI PCI subdriver,
so its callbacks were invoked when creating/destroying PCI root
buses to manage ACPI-based PCI hotplug slots.  But it doesn't handle
P2P bridge hotplug events, so it will cause strange behaviour if there
are hotplug slots associated with a hot-removed P2P bridge.

This patch fixes this issue by:
1) Directly hooking into PCI core to update hotplug slot devices when
   creating/destroying PCI buses through:
	pci_{add|remove}_bus() -> acpi_pci_{add|remove}_bus()
2) Getting rid of unused ACPI PCI subdriver-related code

It also cleans up unused code in the acpiphp driver.

[bhelgaas: keep acpi_pci_add_bus() stub for CONFIG_ACPI=n]
Signed-off-by: Jiang Liu 
Signed-off-by: Yijing Wang 
Signed-off-by: Bjorn Helgaas 
Reviewed-by: Yinghai Lu 
Cc: "Rafael J. Wysocki" 
Cc: Toshi Kani

PCI/ACPI: Handle PCI slot devices when creating/destroying PCI buses

2013-04-12T21:38:25+00:00

Currently the pci_slot driver doesn't update PCI slot devices when PCI
device hotplug event happens, which may cause memory leak and returning
stale information to user.

Now the pci_slot driver has been changed as built-in driver, so invoke
PCI slot enumeration and destroy routines directly from the PCI core.
And remove ACPI PCI sub-driver related code because it isn't needed
any more.

[bhelgas: removed "extern" from function declarations]
Signed-off-by: Jiang Liu 
Signed-off-by: Yijing Wang 
Signed-off-by: Bjorn Helgaas 
Reviewed-by: Yinghai Lu 
Acked-by: Rafael J. Wysocki 
Cc: Toshi Kani

PCI/ACPI: Prepare stub functions to handle ACPI PCI (hotplug) slots

2013-04-12T21:38:25+00:00

Prepare two stub functions to handle ACPI PCI slots and ACPI PCI hotplug
slots, which will be invoked by the PCI core when creating/destroying
PCI buses.

It will be used to get rid of ACPI PCI subdrivers for pci_slot and
acpiphp, and eventually remove the ACPI PCI subdriver mechanism.

And it will also be used to handle ACPI PCI (hotplug) slots in a unified
way, both at boot time and for PCI hotplug operations.

Signed-off-by: Jiang Liu 
Signed-off-by: Yijing Wang 
Signed-off-by: Bjorn Helgaas 
Reviewed-by: Yinghai Lu 
Cc: "Rafael J. Wysocki" 
Cc: Toshi Kani 
Cc: Tony Luck 
Cc: Fenghua Yu 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Myron Stowe

PCI/ACPI: Use DEVICE_ACPI_HANDLE rather than searching acpi_pci_roots

2012-09-24T20:51:23+00:00

When we bind a device to an ACPI handle, the handle is stored in
dev->archdata.acpi_handle.  For such devices, there's no need to
search the acpi_pci_roots list with acpi_get_pci_rootbridge_handle();
we can just use DEVICE_ACPI_HANDLE(dev) directly.

[bhelgaas: changelog, reorder "if" to avoid negation]
Signed-off-by: Yinghai Lu 
Signed-off-by: Bjorn Helgaas 
Cc: Len Brown 
Cc: linux-acpi@vger.kernel.org

PCI/ACPI: provide MMCONFIG address for PCI host bridges

2012-06-22T21:16:51+00:00

This patch provide MMCONFIG address for PCI host bridges, which will
be used to support host bridge hotplug.  It gets MMCONFIG address
by evaluating _CBA method if available.

Reviewed-by: Yinghai Lu 
Signed-off-by: Jiang Liu 
Signed-off-by: Bjorn Helgaas

PCI / ACPI: Fix build of the AER driver for CONFIG_ACPI unset

2011-01-16T19:56:26+00:00

After commit 415e12b23792 ("PCI/ACPI: Request _OSC control once for each
root bridge (v3)") include/linux/pci-acpi.h is included by
drivers/pci/pcie/aer/aerdrv.c and if CONFIG_ACPI is unset, the bogus and
unnecessary alternative definition of acpi_find_root_bridge_handle()
causes a build error to occur.

Remove the offending piece of garbage.

Reported-and-tested-by: Stephen Rothwell 
Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Linus Torvalds

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 / ACPI / PM: Platform support for PCI PME wake-up

2010-02-23T00:21:02+00:00

Although the majority of PCI devices can generate PMEs that in
principle may be used to wake up devices suspended at run time,
platform support is generally necessary to convert PMEs into wake-up
events that can be delivered to the kernel.  If ACPI is used for this
purpose, PME signals generated by a PCI device will trigger the ACPI
GPE associated with the device to generate an ACPI wake-up event that
we can set up a handler for, provided that everything is configured
correctly.

Unfortunately, the subset of PCI devices that have GPEs associated
with them is quite limited.  The devices without dedicated GPEs have
to rely on the GPEs associated with other devices (in the majority of
cases their upstream bridges and, possibly, the root bridge) to
generate ACPI wake-up events in response to PME signals from them.

Add ACPI platform support for PCI PME wake-up:
o Add a framework making is possible to use ACPI system notify
  handlers for run-time PM.
o Add new PCI platform callback ->run_wake() to struct
  pci_platform_pm_ops allowing us to enable/disable the platform to
  generate wake-up events for given device.  Implemet this callback
  for the ACPI platform.
o Define ACPI wake-up handlers for PCI devices and PCI root buses and
  make the PCI-ACPI binding code register wake-up notifiers for all
  PCI devices present in the ACPI tables.
o Add function pci_dev_run_wake() which can be used by PCI drivers to
  check if given device is capable of generating wake-up events at
  run time.

Developed in cooperation with Matthew Garrett .

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

PCI: use pci_is_root_bus() in acpi_find_root_bridge_handle()

2009-06-16T21:29:30+00:00

Use pci_is_root_bus() in acpi_find_root_bridge_handle() to check if
the pci bus is root, for code consistency.

Reviewed-by: Alex Chiang 
Reviewed-by: Grant Grundler 
Signed-off-by: Kenji Kaneshige 
Signed-off-by: Jesse Barnes