1. 28 Jun, 2005 30 commits
  2. 27 Jun, 2005 10 commits
    • Greg KH's avatar
    • Greg Kroah-Hartman's avatar
      [PATCH] PCI: use the MCFG table to properly access pci devices (x86-64) · 1cde8a16
      Greg Kroah-Hartman authored
      
      
      Now that we have access to the whole MCFG table, let's properly use it
      for all pci device accesses (as that's what it is there for, some boxes
      don't put all the busses into one entry.)
      
      If, for some reason, the table is incorrect, we fallback to the "old
      style" of mmconfig accesses, namely, we just assume the first entry in
      the table is the one for us, and blindly use it.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      1cde8a16
    • Greg Kroah-Hartman's avatar
      [PATCH] PCI: use the MCFG table to properly access pci devices (i386) · d57e26ce
      Greg Kroah-Hartman authored
      
      
      Now that we have access to the whole MCFG table, let's properly use it
      for all pci device accesses (as that's what it is there for, some boxes
      don't put all the busses into one entry.)
      
      If, for some reason, the table is incorrect, we fallback to the "old
      style" of mmconfig accesses, namely, we just assume the first entry in
      the table is the one for us, and blindly use it.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      d57e26ce
    • Greg Kroah-Hartman's avatar
      [PATCH] PCI: add proper MCFG table parsing to ACPI core. · 54549391
      Greg Kroah-Hartman authored
      
      
      This patch is the first step in properly handling the MCFG PCI table.
      It defines the structures properly, and saves off the table so that the
      pci mmconfig code can access it.  It moves the parsing of the table a
      little later in the boot process, but still before the information is
      needed.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      54549391
    • Greg Kroah-Hartman's avatar
      [PATCH] PCI: make drivers use the pci shutdown callback instead of the driver core callback. · d18c3db5
      Greg Kroah-Hartman authored
      
      
      Now we can change the pci core to always set this pointer, as pci drivers
      should use it, not the driver core callback.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      d18c3db5
    • Keith Moore's avatar
      [PATCH] cpqphp: fix oops during unload without probe · 4002307d
      Keith Moore authored
      
      
      drivers/pci/hotplug/cpqphp_core.c calls cpqphp_event_start_thread()
      in one_time_init(), which is called whenever the hardware is probed.
      Unfortunately, cpqphp_event_stop_thread() is *always* called when
      the module is unloaded. If the hardware is never probed, then
      cpqphp_event_stop_thread() tries to manipulate a couple of
      uninitialized mutexes.
      Signed-off-by: default avatarKeith Moore <keithmo@exmsft.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      4002307d
    • Greg Kroah-Hartman's avatar
      [PATCH] PCI: clean up the MSI code a bit. · 70549ad9
      Greg Kroah-Hartman authored
      
      
      Mostly just cleans up the irq handling logic to be smaller and a bit more
      descriptive as to what it really does.
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      70549ad9
    • Andrew Morton's avatar
      [PATCH] PCI: fix up errors after dma bursting patch and CONFIG_PCI=n · bb4a61b6
      Andrew Morton authored
      
      
      With CONFIG_PCI=n:
      
      In file included from include/linux/pci.h:917,
                       from lib/iomap.c:6:
      include/asm/pci.h:104: warning: `enum pci_dma_burst_strategy' declared inside parameter list
      include/asm/pci.h:104: warning: its scope is only this definition or declaration, which is probably not what you want.
      include/asm/pci.h: In function `pci_dma_burst_advice':
      include/asm/pci.h:106: dereferencing pointer to incomplete type
      include/asm/pci.h:106: `PCI_DMA_BURST_INFINITY' undeclared (first use in this function)
      include/asm/pci.h:106: (Each undeclared identifier is reported only once
      include/asm/pci.h:106: for each function it appears in.)
      make[1]: *** [lib/iomap.o] Error 1
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      bb4a61b6
    • David S. Miller's avatar
      [PATCH] PCI: DMA bursting advice · e24c2d96
      David S. Miller authored
      
      
      After seeing, at best, "guesses" as to the following kind
      of information in several drivers, I decided that we really
      need a way for platforms to specifically give advice in this
      area for what works best with their PCI controller implementation.
      
      Basically, this new interface gives DMA bursting advice on
      PCI.  There are three forms of the advice:
      
      1) Burst as much as possible, it is not necessary to end bursts
         on some particular boundary for best performance.
      
      2) Burst on some byte count multiple.  A DMA burst to some multiple of
         number of bytes may be done, but it is important to end the burst
         on an exact multiple for best performance.
      
         The best example of this I am aware of are the PPC64 PCI
         controllers, where if you end a burst mid-cacheline then
         chip has to refetch the data and the IOMMU translations
         which hurts performance a lot.
      
      3) Burst on a single byte count multiple.  Bursts shall end
         exactly on the next multiple boundary for best performance.
      
         Sparc64 and Alpha's PCI controllers operate this way.  They
         disconnect any device which tries to burst across a cacheline
         boundary.
      
         Actually, newer sparc64 PCI controllers do not have this behavior.
         That is why the "pdev" is passed into the interface, so I can
         add code later to check which PCI controller the system is using
         and give advice accordingly.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      e24c2d96
    • Michael Ellerman's avatar
      [PATCH] PCI: fix-pci-mmap-on-ppc-and-ppc64.patch · 2311b1f2
      Michael Ellerman authored
      
      
      This is an updated version of Ben's fix-pci-mmap-on-ppc-and-ppc64.patch
      which is in 2.6.12-rc4-mm1.
      
      It fixes the patch to work on PPC iSeries, removes some debug printks
      at Ben's request, and incorporates your
      fix-pci-mmap-on-ppc-and-ppc64-fix.patch also.
      
      Originally from Benjamin Herrenschmidt <benh@kernel.crashing.org>
      
      This patch was discussed at length on linux-pci and so far, the last
      iteration of it didn't raise any comment.  It's effect is a nop on
      architecture that don't define the new pci_resource_to_user() callback
      anyway.  It allows architecture like ppc who put weird things inside of
      PCI resource structures to convert to some different value for user
      visible ones.  It also fixes mmap'ing of IO space on those archs.
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: default avatarMichael Ellerman <michael@ellerman.id.au>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      2311b1f2