1. 10 6月, 2016 4 次提交
  2. 14 4月, 2016 1 次提交
  3. 13 4月, 2016 2 次提交
  4. 27 2月, 2016 1 次提交
    • R
      ARM: dts: am335x: Fix NAND device nodes · 03752148
      Roger Quadros 提交于
      Add compatible id, GPMC register resource and interrupt
      resource to NAND controller nodes.
      
      The GPMC node will provide an interrupt controller for the
      NAND IRQs.
      
      Cc: Teresa Remmet <t.remmet@phytec.de>
      Cc: Ilya Ledvich <ilya@compulab.co.il>
      Cc: Yegor Yefremov <yegorslists@googlemail.com>
      Cc: Rostislav Lisovy <lisovy@gmail.com>
      Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>
      Signed-off-by: NRoger Quadros <rogerq@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      03752148
  5. 22 1月, 2016 1 次提交
  6. 18 12月, 2015 1 次提交
  7. 01 12月, 2015 1 次提交
  8. 02 11月, 2015 1 次提交
  9. 27 10月, 2015 1 次提交
  10. 14 8月, 2015 1 次提交
  11. 05 8月, 2015 1 次提交
  12. 24 7月, 2015 1 次提交
  13. 14 7月, 2015 1 次提交
  14. 01 4月, 2015 1 次提交
  15. 11 12月, 2014 1 次提交
  16. 24 11月, 2014 2 次提交
  17. 11 11月, 2014 2 次提交
  18. 30 9月, 2014 2 次提交
  19. 19 9月, 2014 1 次提交
  20. 12 9月, 2014 3 次提交
  21. 15 7月, 2014 1 次提交
  22. 22 5月, 2014 1 次提交
  23. 15 5月, 2014 1 次提交
  24. 06 5月, 2014 1 次提交
  25. 29 4月, 2014 1 次提交
    • T
      ARM: common: edma: Fix xbar mapping · cf7eb979
      Thomas Gleixner 提交于
      This is another great example of trainwreck engineering:
      
      commit 2646a0e529 (ARM: edma: Add EDMA crossbar event mux support)
      added support for using EDMA on peripherals which have no direct EDMA
      event mapping.
      
      The code compiles and does not explode in your face, but that's it.
      
      1) Reading an u16 array from an u32 device tree array simply does not
         work. Even if the function is named "edma_of_read_u32_to_s16_array".
      
         It merily calls of_property_read_u16_array. So the resulting 16bit
         array will have every other entry = 0.
      
      2) The DT entry for the xbar registers related to xbar has length 0x10
         instead of the real length: 0xfd0 - 0xf90 = 0x40.
      
         Not a real problem as it does not cross a page boundary, but
         wrong nevertheless.
      
      3) But none of this matters as the mapping never happens:
      
         After reading nonsense edma_of_read_u32_to_s16_array() invalidates
         the first array entry pair, so nobody can ever notice the
         braindamage by immediate explosion.
      
      Seems the QA criteria for this code was solely not to explode when
      someone adds edma-xbar-event-map entries to the DT. Goal achieved,
      congratulations!
      
      Not really helpful if someone wants to use edma on a device which
      requires a xbar mapping.
      
      Fix the issues by:
      
      - annotating the device tree entry with "/bits/ 16" as documented in
        the of_property_read_u16_array kernel doc
      
      - make the size of the xbar register mapping correct
      
      - invalidating the end of the array and not the start
      
      This convoluted mess wants to be completely rewritten as there is no
      point to keep the xbar_chan array memory and the iomapping of the xbar
      regs around forever. Marking the xbar mapped channels as used should
      be done right there.
      
      But that's a different issue and this patch is small enough to make it
      work and allows a simple backport for stable.
      
      Cc: stable@vger.kernel.org # v3.12+
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      cf7eb979
  26. 23 4月, 2014 1 次提交
  27. 19 4月, 2014 2 次提交
  28. 14 3月, 2014 1 次提交
  29. 01 3月, 2014 2 次提交