From: Scott Wood <scottwood@freescale.com>
To: Daniel Walker <danielwa@cisco.com>
Cc: Jia Hongtao <B38951@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
"Michael Ellerman" <mpe@ellerman.id.au>,
<linuxppc-dev@lists.ozlabs.org>,
"David Beazley (dbeazley)" <dbeazley@cisco.com>,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>
Subject: Re: powerpc/fsl-pci: Unify pci/pcie initialization code
Date: Thu, 5 Nov 2015 17:12:34 -0600 [thread overview]
Message-ID: <1446765154.12676.132.camel@freescale.com> (raw)
In-Reply-To: <563BA46C.8000202@cisco.com>
On Thu, 2015-11-05 at 10:48 -0800, Daniel Walker wrote:
> Hi,
>
> 905e75c46dba5f3061049277e4eb7110beedba43:arch/powerpc/platforms/85xx/mpc85xx_ads.c
>
>
> This commit seems to cause problems with PCI devices doing DMA, just
> with mpc85xx ads. If you do the "fsl_add_bridge()" after you setup the
> ppc_md.pci_exclude_device to mpc85xx_exclude_device, then the
> early_read_config_word() calls in
> arch/powerpc/sysdev/fsl_pci.c:setup_pci_cmd() are like no-ops.
>
> This issue was found by David Beazley (on the CC), he can respond to
> more detailed questions on it. The fix he came up with was to remove the
> "pci_exclude_device".
>
> Daniel
OK, please send a patch.
-Scott
next prev parent reply other threads:[~2015-11-05 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 18:48 powerpc/fsl-pci: Unify pci/pcie initialization code Daniel Walker
2015-11-05 23:12 ` Scott Wood [this message]
2015-11-05 23:16 ` Daniel Walker
2015-11-05 23:40 ` Scott Wood
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=1446765154.12676.132.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=B38951@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=danielwa@cisco.com \
--cc=dbeazley@cisco.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xe-kernel@external.cisco.com \
/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;
as well as URLs for NNTP newsgroup(s).