FW: [Bug 43247] O2 micro SD/MMC+1394 controller: 1394 device can't work (Register access failure)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Add linux-pci@xxxxxxxxxxxxxxx
Does anyone can help us?

Best regards,
Jennfer
-----Original Message-----
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx [mailto:bugzilla-daemon@xxxxxxxxxxxxxxxxxxx] 
Sent: Saturday, July 14, 2012 9:09 PM
To: Jennifer Li (TP)
Subject: [Bug 43247] O2 micro SD/MMC+1394 controller: 1394 device can't work (Register access failure)

https://bugzilla.kernel.org/show_bug.cgi?id=43247





--- Comment #20 from Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>  2012-07-14 13:09:16 --- 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.]

--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: ------- You reported the bug.



Unless otherwise stated, this e-mail message does not constitute a solicitation to buy or sell any products or services, or to participate in any particular trading strategy. This e-mail message and any attachments are intended solely for the use of the individual or entity to which it is addressed and may contain information that is confidential or legally privileged. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and permanently delete this message and any attachments. O2Micro International Ltd., and its subsidiaries and affiliates, are neither liable for the proper and complete transmission of the information contained in this communication, the accuracy of the information contained therein, nor for any delay in its receipt.  


��.n��������+%������w��{.n�����{���"�)��jg��������ݢj����G�������j:+v���w�m������w�������h�����٥



[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux