- To: Jeff Garzik <jeff@xxxxxxxxxx>
- Subject: Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- From: Brian Norris <computersforpeace@xxxxxxxxx>
- Date: Wed, 15 Feb 2012 15:39:08 -0800
- Cc: Tejun Heo <tj@xxxxxxxxxx>, Lin Ming <ming.m.lin@xxxxxxxxx>, Norbert Preining <preining@xxxxxxxx>, "Srivatsa S. Bhat" <srivatsa.bhat@xxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, "stern@xxxxxxxxxxxxxxxxxxx >> Alan Stern" <stern@xxxxxxxxxxxxxxxxxxx>, linux-ide@xxxxxxxxxxxxxxx, Linux PM mailing list <linux-pm@xxxxxxxxxxxxxxx>, "Rafael J. Wysocki" <rjw@xxxxxxx>, Jian Peng <jipeng2005@xxxxxxxxx>, Kevin Cernekee <cernekee@xxxxxxxxx>, valdis.kletnieks@xxxxxx, Mark Lord <kernel@xxxxxxxxxxxx>
- In-reply-to: <4F3C04EF.7070404@garzik.org>
- List-id: <linux-ide.vger.kernel.org>
On Wed, Feb 15, 2012 at 11:18 AM, Jeff Garzik <jeff@xxxxxxxxxx> wrote:
> On 02/15/2012 01:31 PM, Tejun Heo wrote:
>> 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. :(
>
>
> See ahci_devtype[] and ahci_port_info[] in ahci_platform.c for how to do
> this. Brian would not have to tweak the driver out of tree as claimed; we
> put all changes in tree, and the platform calls itself "spec-strict-ahci" or
> whatever string you prefer.
OK, so can it seems I would add a flag in include/linux/libata.h that
can be added to a new entry in ahci_port_info[]? It seems a little
awkward to put in "libata.h", plus I'm not sure if all the flags have
direct meaning to ATA or if they can be AHCI-specific.
Brian
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
- References:
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
- Re: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
[Linux Filesystems]
[Linux SCSI]
[Linux RAID]
[Git]
[Kernel Newbies]
[Linux Newbie]
[Share Photos]
[Security]
[Netfilter]
[Bugtraq]
[Photo]
[Yosemite]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Samba]
[Video 4 Linux]
[Device Mapper]
[Linux Resources]