1. 23 9月, 2009 3 次提交
  2. 17 9月, 2009 1 次提交
  3. 15 9月, 2009 2 次提交
  4. 09 9月, 2009 2 次提交
  5. 29 8月, 2009 1 次提交
  6. 20 8月, 2009 1 次提交
  7. 14 8月, 2009 1 次提交
  8. 09 7月, 2009 2 次提交
  9. 03 7月, 2009 1 次提交
    • M
      MIPS: BC47xx: Fix SSB irq setup · ea4bbfd0
      matthieu castet 提交于
      The current ssb irq setup in ssb_mipscore_init has the problem that it
      configures some device on some irq without checking that the irq is not
      taken by an other device.
      
      For example in my case PCI host is on irq 0 and IPSEC on irq 3.
      The current code:
        - store in dev->irq that IPSEC irq is 3 + 2
        - do a set_irq 0->3 on PCI host
      
      But now IPSEC irq is not routed anymore to the mips code and dev->irq is
      wrong.  This causes a problem described in [1].
      
      This patch tries to solve the problem by making set_irq configure the
      device we want to take the irq on the shared irq0. The previous example
      becomes:
        - store in dev->irq that IPSEC irq is 3 + 2
        - do a set_irq 0->3 on PCI host:
        - irq 3 is already taken by IPSEC. do a set_irq 3->0 on IPSEC
      
      I also added some code to print the irq configuration after irq setup to
      allow easier debugging. And I add extra checking in ssb_mips_irq to report
      device without irq or device with not routed irq.
      
      [1] http://www.danm.de/files/src/bcm5365p/REPORTED_DEVICESSigned-off-by: NMatthieu CASTET <castet.matthieu@free.fr>
      Acked-by : Michael Buesch <mb@bu3sch.de>
      Tested-by: NFlorian Fainelli <florian@openwrt.org>
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      ea4bbfd0
  10. 08 6月, 2009 1 次提交
  11. 28 3月, 2009 2 次提交
  12. 06 3月, 2009 1 次提交
  13. 10 2月, 2009 1 次提交
  14. 30 1月, 2009 2 次提交
  15. 22 11月, 2008 1 次提交
    • K
      ssb: struct device - replace bus_id with dev_name(), dev_set_name() · b7b05fe7
      Kay Sievers 提交于
      This patch is part of a larger patch series which will remove
      the "char bus_id[20]" name string from struct device. The device
      name is managed in the kobject anyway, and without any size
      limitation, and just needlessly copied into "struct device".
      
      To set and read the device name dev_name(dev) and dev_set_name(dev)
      must be used. If your code uses static kobjects, which it shouldn't
      do, "const char *init_name" can be used to statically provide the
      name the registered device should have. At registration time, the
      init_name field is cleared, to enforce the use of dev_name(dev) to
      access the device name at a later time.
      
      We need to get rid of all occurrences of bus_id in the entire tree
      to be able to enable the new interface. Please apply this patch,
      and possibly convert any remaining remaining occurrences of bus_id.
      
      We want to submit a patch to -next, which will remove bus_id from
      "struct device", to find the remaining pieces to convert, and finally
      switch over to the new api, which will remove the 20 bytes array
      and does no longer have a size limitation.
      
      CC: Michael Buesch <mb@bu3sch.de>
      Acked-by: NGreg Kroah-Hartman <gregkh@suse.de>
      Signed-Off-By: NKay Sievers <kay.sievers@vrfy.org>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b7b05fe7
  16. 11 11月, 2008 1 次提交
  17. 27 9月, 2008 1 次提交
  18. 30 8月, 2008 2 次提交
  19. 23 8月, 2008 2 次提交
  20. 18 8月, 2008 1 次提交
  21. 08 7月, 2008 1 次提交
  22. 27 6月, 2008 1 次提交
  23. 14 6月, 2008 1 次提交
  24. 05 6月, 2008 1 次提交
  25. 08 5月, 2008 1 次提交
  26. 24 4月, 2008 1 次提交
  27. 17 4月, 2008 1 次提交
  28. 16 4月, 2008 1 次提交
    • M
      ssb: Fix usage of struct device used for DMAing · 4ac58469
      Michael Buesch 提交于
      This fixes DMA on architectures where DMA is nontrivial, like PPC64.
      We must use the host-device's (PCI) struct device for any DMA
      operation instead of the SSB device. For this we add a new
      struct device pointer to the SSB device structure that will always
      point to the right device for DMAing.
      
      Without this patch b43 and b44 drivers won't work on complex-DMA
      architectures, that for example need dev->archdata for DMA operations.
      Signed-off-by: NMichael Buesch <mb@bu3sch.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      4ac58469
  29. 09 4月, 2008 3 次提交
反馈
建议
客服 返回
顶部