2009-08-07 22:35:16 +07:00
|
|
|
/*
|
|
|
|
* MPC85xx RDB Board Setup
|
|
|
|
*
|
2013-11-06 16:08:02 +07:00
|
|
|
* Copyright 2009,2012-2013 Freescale Semiconductor Inc.
|
2009-08-07 22:35:16 +07:00
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
* under the terms of the GNU General Public License as published by the
|
|
|
|
* Free Software Foundation; either version 2 of the License, or (at your
|
|
|
|
* option) any later version.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/stddef.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/pci.h>
|
|
|
|
#include <linux/kdev_t.h>
|
|
|
|
#include <linux/delay.h>
|
|
|
|
#include <linux/seq_file.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/of_platform.h>
|
2015-09-20 11:29:53 +07:00
|
|
|
#include <linux/fsl/guts.h>
|
2009-08-07 22:35:16 +07:00
|
|
|
|
|
|
|
#include <asm/time.h>
|
|
|
|
#include <asm/machdep.h>
|
|
|
|
#include <asm/pci-bridge.h>
|
|
|
|
#include <mm/mmu_decl.h>
|
|
|
|
#include <asm/prom.h>
|
|
|
|
#include <asm/udbg.h>
|
|
|
|
#include <asm/mpic.h>
|
2015-11-30 09:48:57 +07:00
|
|
|
#include <soc/fsl/qe/qe.h>
|
|
|
|
#include <soc/fsl/qe/qe_ic.h>
|
2009-08-07 22:35:16 +07:00
|
|
|
|
|
|
|
#include <sysdev/fsl_soc.h>
|
|
|
|
#include <sysdev/fsl_pci.h>
|
2011-12-02 13:27:58 +07:00
|
|
|
#include "smp.h"
|
2009-08-07 22:35:16 +07:00
|
|
|
|
2011-11-18 00:56:16 +07:00
|
|
|
#include "mpc85xx.h"
|
|
|
|
|
2009-08-07 22:35:16 +07:00
|
|
|
#undef DEBUG
|
|
|
|
|
|
|
|
#ifdef DEBUG
|
|
|
|
#define DBG(fmt, args...) printk(KERN_ERR "%s: " fmt, __func__, ## args)
|
|
|
|
#else
|
|
|
|
#define DBG(fmt, args...)
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
|
|
void __init mpc85xx_rdb_pic_init(void)
|
|
|
|
{
|
|
|
|
struct mpic *mpic;
|
|
|
|
|
2012-02-22 12:44:06 +07:00
|
|
|
#ifdef CONFIG_QUICC_ENGINE
|
|
|
|
struct device_node *np;
|
|
|
|
#endif
|
|
|
|
|
2016-07-05 12:04:04 +07:00
|
|
|
if (of_machine_is_compatible("fsl,MPC85XXRDB-CAMP")) {
|
2011-12-22 17:19:14 +07:00
|
|
|
mpic = mpic_alloc(NULL, 0, MPIC_NO_RESET |
|
2011-12-22 17:19:12 +07:00
|
|
|
MPIC_BIG_ENDIAN |
|
2011-07-12 14:49:43 +07:00
|
|
|
MPIC_SINGLE_DEST_CPU,
|
powerpc/85xx: Create dts for each core in CAMP mode for P2020RDB
This patch creates the dts files for each core and splits the devices
between the two cores for P2020RDB.
core0 has memory, L2, i2c, spi, dma1, usb, eth0, eth1, crypto,
global-util, pci0,
core1 has L2, dma2, eth0, pci1, msi.
MPIC is shared between two cores but each core will protect its
interrupts from other core by using "protected-sources" of mpic.
Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2009-09-20 00:13:56 +07:00
|
|
|
0, 256, " OpenPIC ");
|
|
|
|
} else {
|
2011-12-02 13:28:02 +07:00
|
|
|
mpic = mpic_alloc(NULL, 0,
|
2011-12-22 17:19:12 +07:00
|
|
|
MPIC_BIG_ENDIAN |
|
2009-08-07 22:35:16 +07:00
|
|
|
MPIC_SINGLE_DEST_CPU,
|
|
|
|
0, 256, " OpenPIC ");
|
powerpc/85xx: Create dts for each core in CAMP mode for P2020RDB
This patch creates the dts files for each core and splits the devices
between the two cores for P2020RDB.
core0 has memory, L2, i2c, spi, dma1, usb, eth0, eth1, crypto,
global-util, pci0,
core1 has L2, dma2, eth0, pci1, msi.
MPIC is shared between two cores but each core will protect its
interrupts from other core by using "protected-sources" of mpic.
Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
2009-09-20 00:13:56 +07:00
|
|
|
}
|
2009-08-07 22:35:16 +07:00
|
|
|
|
|
|
|
BUG_ON(mpic == NULL);
|
|
|
|
mpic_init(mpic);
|
2012-02-22 12:44:06 +07:00
|
|
|
|
|
|
|
#ifdef CONFIG_QUICC_ENGINE
|
|
|
|
np = of_find_compatible_node(NULL, NULL, "fsl,qe-ic");
|
|
|
|
if (np) {
|
|
|
|
qe_ic_init(np, 0, qe_ic_cascade_low_mpic,
|
|
|
|
qe_ic_cascade_high_mpic);
|
|
|
|
of_node_put(np);
|
|
|
|
|
|
|
|
} else
|
|
|
|
pr_err("%s: Could not find qe-ic node\n", __func__);
|
|
|
|
#endif
|
|
|
|
|
2009-08-07 22:35:16 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Setup the architecture
|
|
|
|
*/
|
|
|
|
static void __init mpc85xx_rdb_setup_arch(void)
|
|
|
|
{
|
|
|
|
if (ppc_md.progress)
|
|
|
|
ppc_md.progress("mpc85xx_rdb_setup_arch()", 0);
|
|
|
|
|
|
|
|
mpc85xx_smp_init();
|
2012-02-22 12:44:06 +07:00
|
|
|
|
2012-08-28 14:44:08 +07:00
|
|
|
fsl_pci_assign_primary();
|
|
|
|
|
2012-02-22 12:44:06 +07:00
|
|
|
#ifdef CONFIG_QUICC_ENGINE
|
2013-11-06 16:08:02 +07:00
|
|
|
mpc85xx_qe_init();
|
2014-03-06 08:38:12 +07:00
|
|
|
mpc85xx_qe_par_io_init();
|
2012-02-22 12:44:06 +07:00
|
|
|
#if defined(CONFIG_UCC_GETH) || defined(CONFIG_SERIAL_QE)
|
|
|
|
if (machine_is(p1025_rdb)) {
|
2014-02-21 03:48:16 +07:00
|
|
|
struct device_node *np;
|
2012-02-22 12:44:06 +07:00
|
|
|
|
2012-03-19 23:06:39 +07:00
|
|
|
struct ccsr_guts __iomem *guts;
|
2012-02-22 12:44:06 +07:00
|
|
|
|
|
|
|
np = of_find_node_by_name(NULL, "global-utilities");
|
|
|
|
if (np) {
|
|
|
|
guts = of_iomap(np, 0);
|
|
|
|
if (!guts) {
|
|
|
|
|
|
|
|
pr_err("mpc85xx-rdb: could not map global utilities register\n");
|
|
|
|
|
|
|
|
} else {
|
|
|
|
/* P1025 has pins muxed for QE and other functions. To
|
|
|
|
* enable QE UEC mode, we need to set bit QE0 for UCC1
|
|
|
|
* in Eth mode, QE0 and QE3 for UCC5 in Eth mode, QE9
|
|
|
|
* and QE12 for QE MII management singals in PMUXCR
|
|
|
|
* register.
|
|
|
|
*/
|
|
|
|
setbits32(&guts->pmuxcr, MPC85xx_PMUXCR_QE(0) |
|
|
|
|
MPC85xx_PMUXCR_QE(3) |
|
|
|
|
MPC85xx_PMUXCR_QE(9) |
|
|
|
|
MPC85xx_PMUXCR_QE(12));
|
|
|
|
iounmap(guts);
|
|
|
|
}
|
|
|
|
of_node_put(np);
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
#endif /* CONFIG_QUICC_ENGINE */
|
|
|
|
|
2009-08-07 22:35:16 +07:00
|
|
|
printk(KERN_INFO "MPC85xx RDB board from Freescale Semiconductor\n");
|
|
|
|
}
|
|
|
|
|
2012-08-28 14:44:08 +07:00
|
|
|
machine_arch_initcall(p2020_rdb, mpc85xx_common_publish_devices);
|
|
|
|
machine_arch_initcall(p2020_rdb_pc, mpc85xx_common_publish_devices);
|
|
|
|
machine_arch_initcall(p1020_mbg_pc, mpc85xx_common_publish_devices);
|
|
|
|
machine_arch_initcall(p1020_rdb, mpc85xx_common_publish_devices);
|
|
|
|
machine_arch_initcall(p1020_rdb_pc, mpc85xx_common_publish_devices);
|
2013-07-01 11:12:22 +07:00
|
|
|
machine_arch_initcall(p1020_rdb_pd, mpc85xx_common_publish_devices);
|
2012-08-28 14:44:08 +07:00
|
|
|
machine_arch_initcall(p1020_utm_pc, mpc85xx_common_publish_devices);
|
|
|
|
machine_arch_initcall(p1021_rdb_pc, mpc85xx_common_publish_devices);
|
|
|
|
machine_arch_initcall(p1025_rdb, mpc85xx_common_publish_devices);
|
|
|
|
machine_arch_initcall(p1024_rdb, mpc85xx_common_publish_devices);
|
2009-08-07 22:35:16 +07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Called very early, device-tree isn't unflattened
|
|
|
|
*/
|
|
|
|
static int __init p2020_rdb_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
if (of_machine_is_compatible("fsl,P2020RDB"))
|
2009-08-07 22:35:16 +07:00
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2009-09-25 11:20:28 +07:00
|
|
|
static int __init p1020_rdb_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
if (of_machine_is_compatible("fsl,P1020RDB"))
|
2009-09-25 11:20:28 +07:00
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-02-10 13:48:15 +07:00
|
|
|
static int __init p1020_rdb_pc_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
return of_machine_is_compatible("fsl,P1020RDB-PC");
|
2012-02-10 13:48:15 +07:00
|
|
|
}
|
|
|
|
|
2013-07-01 11:12:22 +07:00
|
|
|
static int __init p1020_rdb_pd_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
return of_machine_is_compatible("fsl,P1020RDB-PD");
|
2013-07-01 11:12:22 +07:00
|
|
|
}
|
|
|
|
|
2012-01-17 15:01:30 +07:00
|
|
|
static int __init p1021_rdb_pc_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
if (of_machine_is_compatible("fsl,P1021RDB-PC"))
|
2012-01-17 15:01:30 +07:00
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-12-28 10:41:47 +07:00
|
|
|
static int __init p2020_rdb_pc_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
if (of_machine_is_compatible("fsl,P2020RDB-PC"))
|
2011-12-28 10:41:47 +07:00
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-02-14 05:06:22 +07:00
|
|
|
static int __init p1025_rdb_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
return of_machine_is_compatible("fsl,P1025RDB");
|
2012-02-14 05:06:22 +07:00
|
|
|
}
|
|
|
|
|
2012-03-14 16:08:27 +07:00
|
|
|
static int __init p1020_mbg_pc_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
return of_machine_is_compatible("fsl,P1020MBG-PC");
|
2012-03-14 16:08:27 +07:00
|
|
|
}
|
|
|
|
|
2012-03-14 16:08:28 +07:00
|
|
|
static int __init p1020_utm_pc_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
return of_machine_is_compatible("fsl,P1020UTM-PC");
|
2012-03-14 16:08:28 +07:00
|
|
|
}
|
|
|
|
|
2012-05-24 16:08:28 +07:00
|
|
|
static int __init p1024_rdb_probe(void)
|
|
|
|
{
|
2016-07-05 12:04:05 +07:00
|
|
|
return of_machine_is_compatible("fsl,P1024RDB");
|
2012-05-24 16:08:28 +07:00
|
|
|
}
|
|
|
|
|
2009-08-07 22:35:16 +07:00
|
|
|
define_machine(p2020_rdb) {
|
|
|
|
.name = "P2020 RDB",
|
|
|
|
.probe = p2020_rdb_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2009-08-07 22:35:16 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2009-09-25 11:20:28 +07:00
|
|
|
|
|
|
|
define_machine(p1020_rdb) {
|
|
|
|
.name = "P1020 RDB",
|
|
|
|
.probe = p1020_rdb_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2009-09-25 11:20:28 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2012-01-17 15:01:30 +07:00
|
|
|
|
|
|
|
define_machine(p1021_rdb_pc) {
|
|
|
|
.name = "P1021 RDB-PC",
|
|
|
|
.probe = p1021_rdb_pc_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2012-01-17 15:01:30 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2011-12-28 10:41:47 +07:00
|
|
|
|
|
|
|
define_machine(p2020_rdb_pc) {
|
|
|
|
.name = "P2020RDB-PC",
|
|
|
|
.probe = p2020_rdb_pc_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2011-12-28 10:41:47 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2012-02-14 05:06:22 +07:00
|
|
|
|
|
|
|
define_machine(p1025_rdb) {
|
|
|
|
.name = "P1025 RDB",
|
|
|
|
.probe = p1025_rdb_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2012-02-14 05:06:22 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2012-03-14 16:08:27 +07:00
|
|
|
|
|
|
|
define_machine(p1020_mbg_pc) {
|
|
|
|
.name = "P1020 MBG-PC",
|
|
|
|
.probe = p1020_mbg_pc_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2012-03-14 16:08:27 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2012-03-14 16:08:28 +07:00
|
|
|
|
|
|
|
define_machine(p1020_utm_pc) {
|
|
|
|
.name = "P1020 UTM-PC",
|
|
|
|
.probe = p1020_utm_pc_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2012-03-14 16:08:28 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2012-02-10 13:48:15 +07:00
|
|
|
|
|
|
|
define_machine(p1020_rdb_pc) {
|
|
|
|
.name = "P1020RDB-PC",
|
|
|
|
.probe = p1020_rdb_pc_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2012-02-10 13:48:15 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
2012-05-24 16:08:28 +07:00
|
|
|
|
2013-07-01 11:12:22 +07:00
|
|
|
define_machine(p1020_rdb_pd) {
|
|
|
|
.name = "P1020RDB-PD",
|
|
|
|
.probe = p1020_rdb_pd_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2013-07-01 11:12:22 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|
|
|
|
|
2012-05-24 16:08:28 +07:00
|
|
|
define_machine(p1024_rdb) {
|
|
|
|
.name = "P1024 RDB",
|
|
|
|
.probe = p1024_rdb_probe,
|
|
|
|
.setup_arch = mpc85xx_rdb_setup_arch,
|
|
|
|
.init_IRQ = mpc85xx_rdb_pic_init,
|
|
|
|
#ifdef CONFIG_PCI
|
|
|
|
.pcibios_fixup_bus = fsl_pcibios_fixup_bus,
|
fsl/pci: The new pci suspend/resume implementation
If we do nothing in suspend/resume, some platform PCIe ip-block
can't guarantee the link back to L0 state from sleep, then, when
we read the EP device will hang. Only we send pme turnoff message
in pci controller suspend, and send pme exit message in resume, the
link state will be normal.
When we send pme turnoff message in pci controller suspend, the
links will into l2/l3 ready, then, host cannot communicate with
ep device, but pci-driver will call back EP device to save them
state. So we need to change platform_driver->suspend/resume to
syscore->suspend/resume.
So the new suspend/resume implementation, send pme turnoff message
in suspend, and send pme exit message in resume. And add a PME handler,
to response PME & message interrupt.
Change platform_driver->suspend/resume to syscore->suspend/resume.
pci-driver will call back EP device, to save EP state in
pci_pm_suspend_noirq, so we need to keep the link, until
pci_pm_suspend_noirq finish.
Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
Signed-off-by: Scott Wood <scottwood@freescale.com>
2014-03-20 10:19:37 +07:00
|
|
|
.pcibios_fixup_phb = fsl_pcibios_fixup_phb,
|
2012-05-24 16:08:28 +07:00
|
|
|
#endif
|
|
|
|
.get_irq = mpic_get_irq,
|
|
|
|
.calibrate_decr = generic_calibrate_decr,
|
|
|
|
.progress = udbg_progress,
|
|
|
|
};
|