On Tue, 2014-07-22 at 11:52 +0300, Andy Shevchenko wrote: > (I dared to move the discussion from LKML to dmaengine@ mailing list to > avoid unrelated noise in the first one. If you think it needs to be > continued there, please, return it back, but keep dmaengine@ in Cc > list.) No problem. I wasn't sure which list was going to be relevant. I've never had to dig into DMA engine stuff before. > I would like you to check if your kernel has the following patch > applied: > > commit c78b0830667a7e7c1f0ca65b76b33166a84806b3 "ACPI / LPSS: custom power domain for LPSS" I'm running 3.16-rc5 so that commit is there. I'm currently running the packaged kernel from Debian experimental as building anything was difficult until I figured out which module to blacklist. I'll be able to build kernels if we need to try some patches. > If not, please try v3.16-rc6. > > > I'd like some advice on how this should be fixed: > > > > I see that some very similar chipsets would cause the > > i2c_designware-pci driver to be loaded where as mine loads the > > platform device. > > You laptop seems to use ACPI, meanwhile other PCI mode for some devices > inside (LPSS). > > > So is the correct fix to get some PCI ids and settings added to the > > PCI driver? > > I'm pretty sure you don't need this. I was pretty sure that was the case as I can't see a PCI device which would match but just wanted to check. > > Or should I be looking to add a DMI based blacklist to stop the i2c > > bus being detected at all. > > > > > > Or is this just a bug in the dw_dmac module. If so how can I get any > > debug out of it during the rmmod? > > It unlikely a bug in that driver, but to be sure please check what I > asked above. Cheers, Scott -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html