Hello, Aaron. On Thu, Nov 01, 2012 at 10:35:10AM +0800, Aaron Lu wrote: > > You can always add some fields. :) > > OK. My concern is that, such information is only useful to ZPODD > capable device+platforms, so checking this loading mechanism thing for > all ATAPI devices during probe time doesn't seem a good idea.
Hmmm.. but it's not like querying acpi is high cost or anything. Maybe I'm missing something but if it can be simpler that way, please do so by all means. I don't care whether you add some extra fields or some processing overhead during probing. It doesn't really matter. > > Hmm... I see. Which ACPI binding is it? The ATA ACPI binding happens > > during probing. It's a different one, I presume? > > Since commit 6b66d95895c149cbc04d4fac5a2f5477c543a8ae: > libata: bind the Linux device tree to the ACPI device tree > ACPI binding happens when SCSI devices are added to the device tree. The > ata port/device software structure does not have a acpi_handle field > anymore. Please bear with me. I haven't paid much attention to zpodd, so it probably is my ignorance but at least the ATA <-> ACPI association happens during probing by calling ata_acpi_on_devcfg() from ata_dev_configure(), and it pretty much has to happen then because _SDD/_GTF should be executed after hardreset which happens during probing. So, yeah, I'm confused. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
