On Mon, Oct 24, 2016 at 10:46 AM, Dan Williams <dan.j.williams@xxxxxxxxx> wrote: > On Mon, Oct 24, 2016 at 8:16 AM, Christoph Hellwig <hch@xxxxxx> wrote: [..] >> If it's the latter let's keep AHCI entirely out >> of the game - add the affected PCI IDs to the NVMe driver itself, add >> a quirk for them and implement the enable sequence inside the NVMe >> driver. > > The PCI ID of the AHCI device is not uniquely identifiable when in this mode. > > We could flip the arrangement and have the ahci device as the platform > device, but I'm not sure this makes the nvme reset problem much > better. If we allow subsystem resets at all they would still need to > be coordinated across 2 devices/drivers to reinitialize pci registers. ...but it still might be the better way to go. I.e. push the hacks to the legacy driver and not burden nvme with this new "nvme_dev_ops" concept. -- 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
