@@ -2992,6 +2992,18 @@ static bool pci_bridge_d3_allowed(struct pci_dev *bridge, pci_power_t state)
if (pci_bridge_d3_force)
return true;
+ /*
+ * Allow D3Hot for all Devicetree based platforms having a
+ * separate node for the bridge. We don't allow D3Cold for now
+ * since not all platforms are exposing the Vcc supply in
+ * Devicetree which is required for transitioning the bridge to
+ * D3Cold.
+ *
+ * NOTE: The bridge is expected to be defined in Devicetree.
+ */
+ if (state == PCI_D3hot && dev_of_node(&bridge->dev))
+ return true;
+
/* Even the oldest 2010 Thunderbolt controller supports D3. */
if (bridge->is_thunderbolt)
return true;
@@ -3042,7 +3054,7 @@ bool pci_bridge_d3cold_allowed(struct pci_dev *bridge)
*
* This function checks if the bridge is allowed to move to D3Hot.
* Currently we only allow D3Hot for recent enough PCIe ports on ACPI based
- * platforms and Thunderbolt.
+ * platforms, Thunderbolt and Devicetree based platforms.
*/
bool pci_bridge_d3hot_allowed(struct pci_dev *bridge)
{
Unlike ACPI based platforms, there are no known issues with D3Hot for the PCI bridges in the Devicetree based platforms. So let's allow the PCI bridges to go to D3Hot during runtime. It should be noted that the bridges need to be defined in Devicetree for this to work. Currently, D3Cold is not allowed since Vcc supply which is required for transitioning the device to D3Cold is not exposed on all Devicetree based platforms. Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> --- drivers/pci/pci.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)