On Thu, May 24, 2007 at 09:43:39AM +1000, Benjamin Herrenschmidt wrote: > We might have to provide an optional ->flush() that is device specific ? Probably > Config space access would do the job nicely in most cases though. If > it's really only for SRST which can be slow. If it's for the 400ns of > writing the command, then we have a deeper problem but I would expect > MMIO chipsets to be smarter than that ... There are errata for config space and posting in some chipsets and as you says its slow. The 400nS command writing bit applies too - they chipsets are not that smart in my experience. > Ah yes, the PRD table pointer is a good option too... We could introduce > a ->flush() and have a default sff version that reads that pointer ? Normal SFF is I/O cycles so the default SFF one would be NULL which is just perfect 8). SIL680/3112 would register a PRD read and the rest can do whatever their non SFF design does. - 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
