All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: "Jennifer Li (TP)" <Jennifer.Li@o2micro.com>
Cc: linux-pci@vger.kernel.org, stefanr@s5r6.in-berlin.de,
	bugzilla-daemon@bugzilla.kernel.org
Subject: Re: FW: [Bug 43247] O2 micro SD/MMC+1394 controller: 1394 device can't work (Register access failure)
Date: Tue, 17 Jul 2012 12:24:37 -0600	[thread overview]
Message-ID: <CAErSpo5tpn0o3NTZy3VCvhU4H7+vWCSdMVmgaexqY8VY_4h=yw@mail.gmail.com> (raw)
In-Reply-To: <FC57104DF444434A9D1D8A7B4EBB29231353B632@HC-EXCHANGE.nt-fsrvr.o2micro.com>

> 1.)  Is there a kernel parameter which Jennifer could try in order to force serialized PCI driver probing?

I don't understand the question here.  As far as I know, drivers
compiled statically into the kernel are already initialized serially,
via the do_initcalls() -> do_initcall_level(6) path.  The PCI core
enumerates all the devices, then when we call each driver's
module_init() function (serially), the module_init() function will
register the driver, and the driver core will call the driver's
.probe() function for every matching PCI device.

> 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 serialization is required between two drivers, that sounds like a
driver bug.  What are the two drivers involved?

  reply	other threads:[~2012-07-17 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  1:40 FW: [Bug 43247] O2 micro SD/MMC+1394 controller: 1394 device can't work (Register access failure) Jennifer Li (TP)
2012-07-17 18:24 ` Bjorn Helgaas [this message]
2012-07-17 19:46   ` Stefan Richter
2012-07-17 20:55     ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAErSpo5tpn0o3NTZy3VCvhU4H7+vWCSdMVmgaexqY8VY_4h=yw@mail.gmail.com' \
    --to=bhelgaas@google.com \
    --cc=Jennifer.Li@o2micro.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.