On Jul 10 bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=43247 > > --- Comment #19 from jennifer <jennifer.li@xxxxxxxxxxx> 2012-07-10 11:02:16 --- [...] > > Do you mean by that that > > the original Linux driver works for you if you boot Linux but do not let > > the driver be automatically loaded during boot, but instead load the driver > > later by 'modprobe firewire-ohci' after the rest of the system has finished > > booting up? > > Yes. > > > > > And if yes, did you also need to load the sdhci-pci driver manually this > > way? > > There are 4 ways which can pass the issue. > 1. Load 1394 by OS + Load sdhci-pci by manually. > 2. Load sdhci-pci by OS + Load 1394 by manually. > 3. Load 1394 by manually + load sdhci-pci by manually. > 4. Load sdhci-pci by manually + load 1394 by manually. > > > And further, does it matter whether sdhci-pci is loaded before > > firewire-ohci or the other way around? > > According to our test result, if we load the driver by manually and the issue > will disappear. It didn't has the relationship about the loaded priority. > But, if we load those drivers by OS and the issue will happen. Could somebody at linux-pci@xxxxxxxxxxxxxxx please advise? 1.) Is there a kernel parameter which Jennifer could try in order to force serialized PCI driver probing? 2.) If there is one and if this turns out to cure the issue in testing: How can I implement serialization between the O2Micro FireWire .probe() and .resume() on one hand and the O2Micro SDHCI .probe() and .resume() on the other hand? [If you reply to this via bugzilla mail, please add Cc: linux-pci@xxxxxxxxxxxxxxx in your reply. I am not aware of a way to add it to bugzilla.kernel.org's Cc list of bug 43247.] -- Stefan Richter -=====-===-- -=== -===- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
