[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F3D2C86.6080701@garzik.org>
Date: Thu, 16 Feb 2012 11:19:18 -0500
From: Jeff Garzik <jeff@...zik.org>
To: Mark Lord <kernel@...savvy.com>
CC: Tejun Heo <tj@...nel.org>,
Brian Norris <computersforpeace@...il.com>,
Lin Ming <ming.m.lin@...el.com>,
Norbert Preining <preining@...ic.at>,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org,
"stern@...land.harvard.edu >> Alan Stern" <stern@...land.harvard.edu>,
linux-ide@...r.kernel.org,
Linux PM mailing list <linux-pm@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Jian Peng <jipeng2005@...il.com>,
Kevin Cernekee <cernekee@...il.com>, valdis.kletnieks@...edu
Subject: Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET
failed
On 02/16/2012 09:20 AM, Mark Lord wrote:
> On 12-02-15 01:31 PM, Tejun Heo wrote:
>> Hey, Jeff.
>>
>> On Wed, Feb 15, 2012 at 01:29:29PM -0500, Jeff Garzik wrote:
>>> A module parameter is not necessarily the best/only option.
>>> ahci_platform already has infrastructure set up to deal with
>>> platform-specific quirks. An internal flag seems more appropriate
>>> to enable automatic handling of this on the specific platforms where
>>> it applies (plus the revert Tejun has already mentioned).
>>
>> The problem is that there's no way to identify the controller in
>> question, so we can't do this automatically, so might just as well do
>> it in the simplest way for now. :(
>
> Well, a module parameter is no good,
> because that method would affect all attached controllers
> rather than just the one(s) with the issue.
>
> Something in sysfs perhaps.
See the method already described in my previous message.
grep for IMX53_AHCI.
Jeff
--
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