Skip to content
Snippets Groups Projects
  1. Oct 11, 2012
  2. Aug 17, 2012
    • Bruno Randolf's avatar
      MIPS: MTX-1: Add udelay to mtx1_pci_idsel · 143ec74e
      Bruno Randolf authored
      
      Without this udelay(1) PCI idsel does not work correctly on the
      "singleboard" (T-Mobile Surfbox) for the MiniPCI device. The result is
      that PCI configuration fails and the MiniPCI card is not detected
      correctly. Instead of
      
      PCI host bridge to bus 0000:00
      pci_bus 0000:00: root bus resource [mem 0x40000000-0x4fffffff]
      pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
      pci 0000:00:03.0: BAR 0: assigned [mem 0x40000000-0x4000ffff]
      pci 0000:00:00.0: BAR 0: assigned [mem 0x40010000-0x40010fff]
      pci 0000:00:00.1: BAR 0: assigned [mem 0x40011000-0x40011fff]
      
      We see only the CardBus device:
      
      PCI host bridge to bus 0000:00
      pci_bus 0000:00: root bus resource [mem 0x40000000-0x4fffffff]
      pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
      pci 0000:00:00.0: BAR 0: assigned [mem 0x40000000-0x40000fff]
      pci 0000:00:00.1: BAR 0: assigned [mem 0x40001000-0x40001fff]
      
      Later the device driver shows this error:
      
      ath5k 0000:00:03.0: cannot remap PCI memory region
      ath5k: probe of 0000:00:03.0 failed with error -5
      
      I assume that the logic chip which usually supresses the signal to the CardBus
      card has some settling time and without the delay it would still let the
      Cardbus interfere with the response from the MiniPCI card.
      
      What I cannot explain is why this behaviour shows up now and not in earlier
      kernel versions before. Maybe older PCI code was slower?
      
      Signed-off-by: default avatarBruno Randolf <br1@einfach.org>
      Cc: linux-mips@linux-mips.org
      Cc: manuel.lauss@googlemail.com
      Cc: florian@openwrt.org
      Patchwork: https://patchwork.linux-mips.org/patch/4087/
      
      
      Signed-off-by: default avatarRalf Baechle <ralf@linux-mips.org>
      143ec74e
  3. Jul 23, 2012
  4. May 15, 2012
  5. May 14, 2012
  6. Feb 20, 2012
    • Manuel Lauss's avatar
      MIPS: Alchemy: Increase minimum timeout for 32kHz timer. · 8e365790
      Manuel Lauss authored
      
      Since a clocksource change post 3.2-rc1, tasks on my DB1500 board
      hang after random amounts of time (from a few minutes to a few hours),
      regardless of load.  Debugging showed that the compare-match register
      value is a few seconds lower than the current counter value.
      
      The minimum value of 8 was initialy determined by a trial-and-error
      approach.  Currently it is sufficient for all Alchemys (without PCI
      apparently), independent of CPU clock;  only the DB1500 and DB1550
      boards experience these timer-related tasks hangs now.
      
      This patch increases the minimum timeout by 1 (to 9 counter ticks)
      which seems sufficient since the systems are still working perfectly
      fine after over 24 hours.
      
      Signed-off-by: default avatarManuel Lauss <manuel.lauss@googlemail.com>
      Cc: linux-mips@linux-mips.org
      Patchwork: https://patchwork.linux-mips.org/patch/3214/
      
      
      Signed-off-by: default avatarRalf Baechle <ralf@linux-mips.org>
      8e365790
  7. Dec 08, 2011
  8. Dec 07, 2011
  9. Oct 24, 2011
Loading