[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1181471412.384.9.camel@chaos>
Date: Sun, 10 Jun 2007 12:30:12 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>,
Ingo Molnar <mingo@...e.hu>, Andi Kleen <ak@...e.de>,
Arjan van de Ven <arjan@...radead.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
Chris Wright <chrisw@...s-sol.org>
Subject: Re: [patch-mm 06/23] clockevents: Fix resume logic
On Sun, 2007-06-10 at 12:19 +0200, Rafael J. Wysocki wrote:
> > -/*
> > - * Suspend/resume part
> > - */
> > -
> > -#ifdef CONFIG_PM
> > -
> > -static int hpet_suspend(struct sys_device *sys_device, pm_message_t state)
> > -{
> > - unsigned long cfg = hpet_readl(HPET_CFG);
> > -
> > - cfg &= ~(HPET_CFG_ENABLE|HPET_CFG_LEGACY);
> > - hpet_writel(cfg, HPET_CFG);
> > -
> > - return 0;
> > -}
>
> Hmm, I haven't found anything to replace the above in the patch. Is that
> intentional, or is it there, but I haven't noticed?
> > + case CLOCK_EVT_MODE_RESUME:
> > + hpet_enable_int();
> > + break;
tglx
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists