From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET
 failed
Date: Thu, 16 Feb 2012 11:19:18 -0500
Message-ID: <4F3D2C86.6080701@garzik.org>
References: <20120206024052.GI9413@gamma.logic.tuwien.ac.at> <1328496591.15079.40.camel@minggr> <20120206031528.GA16093@gamma.logic.tuwien.ac.at> <1328503376.15079.55.camel@minggr> <20120206161943.GA3926@google.com> <CAN8TOE9SM1X_rQCScE8hCZYrWVY9K-B_TM+Vvzx3tZQ2LoGxXw@mail.gmail.com> <20120213174445.GD12117@google.com> <CAN8TOE-hFvDs4mGeYVRBDyfbyg8t_7YXDintLeG1QHvMXhVh+A@mail.gmail.com> <20120215165706.GA24986@google.com> <4F3BF989.8060607@garzik.org> <20120215183139.GC24986@google.com> <4F3D10A6.8090608@teksavvy.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <4F3D10A6.8090608@teksavvy.com>
Sender: linux-kernel-owner@vger.kernel.org
To: Mark Lord <kernel@teksavvy.com>
Cc: Tejun Heo <tj@kernel.org>, Brian Norris <computersforpeace@gmail.com>, Lin Ming <ming.m.lin@intel.com>, Norbert Preining <preining@logic.at>, "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>, linux-kernel@vger.kernel.org, "stern@rowland.harvard.edu >> Alan Stern" <stern@rowland.harvard.edu>, linux-ide@vger.kernel.org, Linux PM mailing list <linux-pm@vger.kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>, Jian Peng <jipeng2005@gmail.com>, Kevin Cernekee <cernekee@gmail.com>, valdis.kletnieks@vt.edu
List-Id: linux-ide@vger.kernel.org

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