[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110110160001.GC5275@kroah.com>
Date: Mon, 10 Jan 2011 08:00:01 -0800
From: Greg KH <greg@...ah.com>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Jesse Barnes <jbarnes@...tuousgeek.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
linux-usb@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
Borislav Petkov <borislav.petkov@....com>,
Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: [PATCH 3/3] x86: usb handoff in early_quirk
On Sun, Jan 09, 2011 at 11:59:56AM -0800, Yinghai Lu wrote:
>
> some systems keep getting
> APIC calibration not consistent with PM-Timer: 139ms instead of 100ms
> APIC delta adjusted to PM-Timer: 831249 (1163736)
>
> USB legacy SMI handler is not disabled at that time.
>
> Try to disable USB legacy support early with this patch.
> So later APIC Timer calibration don't get messed up by USB legacy support SMI handler.
> After this patch, that warning never show up for 100 reboot tests.
But is that warning a real issue? Does it cause problems for the user
(becides annoying them of course)?
> reuse code from drivers/usb/host/pci-quirks.c
> with changes
> 1. delay and sleep ===> io_delay
> 2. dev_warn etc to pr_warn(num, slot, func...)
Why change this function? What's wrong with dev_warn()? It's much more
descriptive of the device that is being referred to.
thanks,
greg k-h
--
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