From: David Miller <davem@davemloft.net>
To: stefanr@s5r6.in-berlin.de
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@suse.de, krh@bitplanet.net,
linux1394-devel@lists.sourceforge.net
Subject: Re: No dma_sync_* during pci_probe? (Sparc, post 2.6.22 regression)
Date: Mon, 17 Dec 2007 16:50:32 -0800 (PST) [thread overview]
Message-ID: <20071217.165032.41424988.davem@davemloft.net> (raw)
In-Reply-To: <47670BDF.80409@s5r6.in-berlin.de>
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Date: Tue, 18 Dec 2007 00:53:03 +0100
> The fault happens due to dma_sync_single_for_device() which
> drivers/firewire/fw-ohci.c calls in ar_context_add_page() when still
> being in its pci_probe method. I suspect that --- at least on Sparc and
> after 2.6.22 --- it is not possible anymore to use dma_sync_* before the
> pci_device's or device's probe was finished.
>
> Would that be a bug in the Sparc platform code? Or a bug in driver core
> code or in PCI code? Or am I expected to refrain from dma_sync_* calls
> until after the probe returned?
The problem is likely what device struct you are passing to
dma_sync_single_for_device(), it has to be a real pci_dev or similar
that has it's dev_archdata properly initialized.
I bet dev_archdata in whatever "struct device" is being passed in has
a NULL iommu pointer or something like that.
Oh yeah, I see what you're doing, that won't work, please pass in
the correct device struct pointer. Please pass in the &pci_dev->dev
not this ohci->card.device thing.
next prev parent reply other threads:[~2007-12-18 0:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9160-4803@http.bugzilla.kernel.org/>
[not found] ` <47112797.7060003@s5r6.in-berlin.de>
2007-12-17 23:53 ` No dma_sync_* during pci_probe? (Sparc, post 2.6.22 regression) Stefan Richter
2007-12-18 0:50 ` David Miller [this message]
2007-12-18 10:38 ` Stefan Richter
2007-12-18 22:29 ` David Miller
2007-12-19 16:33 ` Stefan Richter
2007-12-19 23:06 ` David Miller
2007-12-20 8:40 ` David Miller
2007-12-20 20:19 ` Emanuele Rocca
2007-12-22 13:10 ` Stefan Richter
2007-12-18 22:30 ` David Miller
2007-12-19 21:08 ` Benjamin Herrenschmidt
2007-12-19 21:07 ` Benjamin Herrenschmidt
2007-12-18 2:58 ` Chris Newport
2007-12-18 3:03 ` David Miller
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=20071217.165032.41424988.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=krh@bitplanet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox