On Thu, 2009-07-16 at 15:45 +0100, Matthew Garrett wrote: > On Thu, Jul 16, 2009 at 02:43:19PM +0000, James Bottomley wrote: > > On Thu, 2009-07-16 at 15:38 +0100, Matthew Garrett wrote: > > > Exactly. > > > > OK, so if this is only in relation to SATA power management, put it in > > libata and call it something like pm_capable. That way we don't have to > > work out what to do with it for the rest of SCSI. > > I have vague memories of this coming up before and it being suggested > that it should be done at the SCSI layer instead, but I can't find that > now. Doing it entirely in libata certainly isn't a problem. Well, a flag that says 'hotplug' and means both the controller and bus support hotplugging might be SCSI specific. However, the fact is that most people make such a determination on the bus type, so it's a bit redundant (in true SCSI there really is no controller on a hotplug bus that doesn't support hotplug because they can't scan the bus without it). If you intend to use it to make link power management decisions, that's completely different because SAS PM support still isn't standardised and most of the rest of SCSI doesn't have it either. So it sounds to me you're looking for a flag that says "might have a problem with SATA link power management" ... in which case this is currently libata specific. We might be able to expand it to libsas if (when) we actually get link power management standardised, but a lot of the other busses aren't even going to have a concept of link power management. James -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
