From: Scott Wood <scottwood@freescale.com>
To: Aaron Sierra <asierra@xes-inc.com>
Cc: Minghuan Lian <Minghuan.Lian@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: fsl_pci: Fix PCI/PCI-X regression
Date: Thu, 21 Aug 2014 16:19:56 -0500 [thread overview]
Message-ID: <1408655996.2395.7.camel@snotra.buserror.net> (raw)
In-Reply-To: <1335064415.96829.1408578704825.JavaMail.zimbra@xes-inc.com>
On Wed, 2014-08-20 at 18:51 -0500, Aaron Sierra wrote:
> @@ -520,9 +520,22 @@ int fsl_add_bridge(struct platform_device *pdev, int is_primary)
> goto no_bridge;
>
> } else {
> - /* For PCI read PROG to identify controller mode */
> - early_read_config_byte(hose, 0, 0, PCI_CLASS_PROG, &progif);
> - if ((progif & 1) == 1)
> + u16 master;
> +
> + /*
> + * If the controller is PCI-X, then Host mode refers to a
> + * bridge that drives the PCI-X initialization pattern to
> + * indicate bus operating mode/frequency to devices on the bus.
> + * Some hardware (specifically PrPMC modules) are Agents, since
> + * the mezzanine carrier is responsible for driving the
> + * pattern, but they still may perform bus enumeration.
> + *
> + * Allow the bridge to be used for enumeration, if hardware
> + * strapping (Host mode) or firmware (Agent mode) has enabled
> + * bus mastering.
> + */
> + early_read_config_word(hose, 0, 0, PCI_COMMAND, &master);
> + if (!(master & PCI_COMMAND_MASTER))
> goto no_bridge;
> }
Why wouldn't a normal PCI agent be able to bus master?
-Scott
next prev parent reply other threads:[~2014-08-21 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1884375274.96749.1408578481814.JavaMail.zimbra@xes-inc.com>
2014-08-20 23:51 ` [PATCH] powerpc: fsl_pci: Fix PCI/PCI-X regression Aaron Sierra
2014-08-21 21:19 ` Scott Wood [this message]
2014-08-21 21:54 ` Aaron Sierra
2014-08-21 22:01 ` Scott Wood
2014-08-22 17:54 ` Aaron Sierra
2014-08-22 18:36 ` Scott Wood
2014-08-22 19:00 ` Aaron Sierra
2014-08-22 19:53 ` 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=1408655996.2395.7.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Minghuan.Lian@freescale.com \
--cc=asierra@xes-inc.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).