linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kevin Hao <haokexin@gmail.com>
Cc: linuxppc <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/3] powerpc/mpc85xx: remove the unneeded pci init functions for corenet ds board
Date: Thu, 30 May 2013 13:54:59 -0500	[thread overview]
Message-ID: <1369940099.14679.14@snotra> (raw)
In-Reply-To: <20130530102034.GB18702@pek-khao-d1.corp.ad.wrs.com> (from haokexin@gmail.com on Thu May 30 05:20:34 2013)

On 05/30/2013 05:20:34 AM, Kevin Hao wrote:
> On Tue, May 28, 2013 at 05:52:09PM -0500, Scott Wood wrote:
> > On 05/21/2013 07:04:58 AM, Kevin Hao wrote:
> > >It also seems that we don't support ISA on all the current corenet =20
> ds
> > >boards. So picking a primary bus seems useless, remove that =20
> function
> > >too.
> >
> > IIRC that was due to some bugs in the PPC PCI code in the absence of
> > any primary bus.
>=20
> Do you know more about these bugs?

Not off the top of my head -- either search the archives or ask Ben.

> >  fsl_pci_assign_primary() will arbitrarily pick one
> > to be primary if there's no ISA.  Have the bugs been fixed?
>=20
> I know there should be some reason that we put the =20
> fsl_pci_assign_primary()
> here. But frankly I am not sure what bugs this workaround try to fix. =20
> For these
> corenet boards picking one to be primary has no effect to the 64bit =20
> kernel.
> And for 32bit kernel, the only effect of this is that isa_io_base is =20
> set to the
> io virtual base of the primary bus. But the isa_io_base only make =20
> sense when
> we do have a isa bus, so that we can access some well-known io ports =20
> directly
> by using outx/inx. But if we don't have isa bus on the board, the =20
> value of
> isa_io_base should make no sense at all. So we really don't need to =20
> pick a
> fake primary bus. Of course I may miss something, correct me if I am =20
> wrong. :-)

outx/inx can also be used for PCI I/O BARs.

-Scott=

  reply	other threads:[~2013-05-30 18:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 12:04 [PATCH 0/3] several cleanup patches for fsl pci Kevin Hao
2013-05-21 12:04 ` [PATCH 1/3] powerpc/mpc85xx: remove the unneeded pci init functions for corenet ds board Kevin Hao
2013-05-28 22:52   ` Scott Wood
2013-05-30 10:20     ` Kevin Hao
2013-05-30 18:54       ` Scott Wood [this message]
2013-05-31  6:41         ` Kevin Hao
2013-05-31 10:11           ` Benjamin Herrenschmidt
2013-06-01 10:59             ` Kevin Hao
2013-06-01 11:47               ` Benjamin Herrenschmidt
2013-06-02  0:07                 ` Kevin Hao
2013-06-03 16:42                   ` Scott Wood
2013-06-07  2:00                     ` Kevin Hao
2013-06-08  0:00                       ` Scott Wood
2013-07-23 22:31                       ` Scott Wood
2013-07-25 12:54                         ` Kevin Hao
2013-07-26 22:43                           ` Scott Wood
2013-07-28  0:32                             ` Kevin Hao
2013-05-31  6:43         ` Kevin Hao
2013-05-31 23:27           ` Scott Wood
2013-06-01 11:13             ` Kevin Hao
2013-05-21 12:04 ` [PATCH 2/3] powerpc/fsl-pci: fix the unreachable warning message Kevin Hao
2013-05-21 12:05 ` [PATCH 3/3] powerpc/fsl-pci: enable SWIOTLB in function setup_pci_atmu Kevin Hao

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=1369940099.14679.14@snotra \
    --to=scottwood@freescale.com \
    --cc=haokexin@gmail.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).