From: Scott Wood <scottwood@freescale•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: Peter LaDow <petela@gocougs•wsu.edu>, linuxppc-dev@lists•ozlabs.org
Subject: Re: Inbound PCI and Memory Corruption
Date: Fri, 19 Jul 2013 12:44:33 -0500 [thread overview]
Message-ID: <1374255873.5357.20@snotra> (raw)
In-Reply-To: <1374184953.19894.525.camel@pasglop> (from benh@kernel.crashing.org on Thu Jul 18 17:02:33 2013)
On 07/18/2013 05:02:33 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-07-18 at 14:30 -0700, Peter LaDow wrote:
> > We are still stumped on this one, but during a review of the system
> > setup one thing came up that we aren't sure about is the device tree
> > and the DMA engine.
> >
> > It does seem that for incoming PCI transactions the Freescale DMA
> > engine is not used. And in our device tree we have the DMA engine
> > commented out. That is, the "fsl,mpc8349-dma" and "fsl,elo-dma"
> > compatible items are not present in the FDT.
> >
> > I don't suppose this could be a problem?
>=20
> I doubt it but somebody from FSL might be able to give a better =20
> answer.
The DMA engine is not related to inbound PCI transactions.
-Scott=
next prev parent reply other threads:[~2013-07-19 17:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 16:56 Inbound PCI and Memory Corruption Peter LaDow
2013-06-21 17:14 ` Peter LaDow
2013-06-23 0:00 ` Benjamin Herrenschmidt
2013-06-24 0:56 ` Peter LaDow
2013-06-24 1:16 ` Benjamin Herrenschmidt
2013-06-24 3:47 ` Peter LaDow
2013-06-24 3:49 ` Benjamin Herrenschmidt
2013-06-25 18:44 ` Peter LaDow
2013-07-10 21:06 ` Peter LaDow
2013-07-10 21:40 ` Benjamin Herrenschmidt
2013-07-10 22:16 ` Peter LaDow
2013-07-11 21:00 ` Peter LaDow
2013-07-18 21:30 ` Peter LaDow
2013-07-18 22:02 ` Benjamin Herrenschmidt
2013-07-19 17:44 ` Scott Wood [this message]
2013-07-19 13:46 ` Gerhard Sittig
2013-07-24 4:22 ` Peter LaDow
2013-07-24 4:27 ` Benjamin Herrenschmidt
2013-07-24 15:39 ` Peter LaDow
2013-07-24 22:08 ` Benjamin Herrenschmidt
2013-07-25 6:13 ` Peter LaDow
2013-08-02 15:01 ` Peter LaDow
2013-07-24 8:40 ` David Laight
2013-07-19 20:13 ` Timur Tabi
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=1374255873.5357.20@snotra \
--to=scottwood@freescale$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=petela@gocougs$(echo .)wsu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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