On Fri, Jun 01, 2012 at 05:08:52PM -0500, Scott Wood wrote: > On 05/11/2012 06:53 AM, Zhao Chenhui wrote: > > Add APIs for setting wakeup source and lossless Ethernet in low power modes. > > These APIs can be used by wake-on-packet feature. > > > > Signed-off-by: Dave Liu <dave...@freescale.com> > > Signed-off-by: Li Yang <le...@freescale.com> > > Signed-off-by: Jin Qing <b24...@freescale.com> > > Signed-off-by: Zhao Chenhui <chenhui.z...@freescale.com> > > --- > > arch/powerpc/sysdev/fsl_pmc.c | 71 > > ++++++++++++++++++++++++++++++++++++++++- > > arch/powerpc/sysdev/fsl_soc.h | 9 +++++ > > 2 files changed, 79 insertions(+), 1 deletions(-) > > > > diff --git a/arch/powerpc/sysdev/fsl_pmc.c b/arch/powerpc/sysdev/fsl_pmc.c > > index 1dc6e9e..c1170f7 100644 > > --- a/arch/powerpc/sysdev/fsl_pmc.c > > +++ b/arch/powerpc/sysdev/fsl_pmc.c > > @@ -34,6 +34,7 @@ struct pmc_regs { > > __be32 powmgtcsr; > > #define POWMGTCSR_SLP 0x00020000 > > #define POWMGTCSR_DPSLP 0x00100000 > > +#define POWMGTCSR_LOSSLESS 0x00400000 > > __be32 res3[2]; > > __be32 pmcdr; > > }; > > @@ -43,6 +44,74 @@ static unsigned int pmc_flag; > > > > #define PMC_SLEEP 0x1 > > #define PMC_DEEP_SLEEP 0x2 > > +#define PMC_LOSSLESS 0x4 > > + > > +/** > > + * mpc85xx_pmc_set_wake - enable devices as wakeup event source > > + * @pdev: platform device affected > > + * @enable: True to enable event generation; false to disable > > + * > > + * This enables the device as a wakeup event source, or disables it. > > + * > > + * RETURN VALUE: > > + * 0 is returned on success > > + * -EINVAL is returned if device is not supposed to wake up the system > > + * Error code depending on the platform is returned if both the platform > > and > > + * the native mechanism fail to enable the generation of wake-up events > > + */ > > +int mpc85xx_pmc_set_wake(struct platform_device *pdev, bool enable) > > Why does it have to be a platform_device? Would a bare device_node work > here? If it's for stuff like device_may_wakeup() that could be in a > platform_device wrapper function.
It does not have to be a platform_device. I think it can be a struct device. > > Where does this get called from? I don't see an example user in this > patchset. It will be used by a gianfar related patch. I plan to submit that patch after these patches accepted. > > > +{ > > + int ret = 0; > > + struct device_node *clk_np; > > + u32 *prop; > > + u32 pmcdr_mask; > > + > > + if (!pmc_regs) { > > + pr_err("%s: PMC is unavailable\n", __func__); > > + return -ENODEV; > > + } > > + > > + if (enable && !device_may_wakeup(&pdev->dev)) > > + return -EINVAL; > > Who is setting can_wakeup for these devices? The device driver is responsible to set can_wakeup. > > > + clk_np = of_parse_phandle(pdev->dev.of_node, "fsl,pmc-handle", 0); > > + if (!clk_np) > > + return -EINVAL; > > + > > + prop = (u32 *)of_get_property(clk_np, "fsl,pmcdr-mask", NULL); > > Don't cast the const away. OK. > > > + if (!prop) { > > + ret = -EINVAL; > > + goto out; > > + } > > + pmcdr_mask = be32_to_cpup(prop); > > + > > + if (enable) > > + /* clear to enable clock in low power mode */ > > + clrbits32(&pmc_regs->pmcdr, pmcdr_mask); > > + else > > + setbits32(&pmc_regs->pmcdr, pmcdr_mask); > > What is the default PMCDR if this function is never called? Should init > to all bits set on PM driver probe (or maybe limit it to defined bits > only, though that's a little harder to do generically). > > -Scot The default PMCDR is defined separately by individual chip. I agree with you. I will have a try. -Chenhui _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev