1. 05 Aug, 2015 2 commits
  2. 31 Jul, 2015 3 commits
  3. 30 Jul, 2015 1 commit
  4. 28 Jul, 2015 2 commits
  5. 27 Jul, 2015 5 commits
  6. 24 Jul, 2015 4 commits
  7. 23 Jul, 2015 8 commits
  8. 22 Jul, 2015 4 commits
  9. 20 Jul, 2015 1 commit
  10. 18 Jul, 2015 3 commits
    • Vaishali Thakkar's avatar
      ARM: pxa: Use setup_timer · 6d6db340
      Vaishali Thakkar authored
      Use the timer API function setup_timer instead of structure field
      assignments to initialize a timer.
      
      A simplified version of the Coccinelle semantic patch that performs
      this transformation is as follows:
      
      @change@
      expression e1, e2, a;
      @@
      
      -init_timer(&e1);
      +setup_timer(&e1, a, 0UL);
      ... when != a = e2
      -e1.function = a;
      Signed-off-by: default avatarVaishali Thakkar <vthakkar1994@gmail.com>
      Signed-off-by: default avatarRobert Jarzmik <robert.jarzmik@free.fr>
      6d6db340
    • Vaishali Thakkar's avatar
      ARM: pxa: Use module_platform_driver · 9754c8ef
      Vaishali Thakkar authored
      Use module_platform_driver for drivers whose init and exit functions
      only register and unregister, respectively.
      
      A simplified version of the Coccinelle semantic patch that performs
      this transformation is as follows:
      
      @A@
      identifier f, x;
      @@
      -static f(...) { return platform_driver_register(&x); }
      
      @b depends on a@
      identifier e, a.x;
      @@
      -static e(...) { platform_driver_unregister(&x); }
      
      @c depends on a && b@
      identifier a.f;
      declarer name module_init;
      @@
      -module_init(f);
      
      @d depends on a && b && c@
      identifier b.e, a.x;
      declarer name module_exit;
      declarer name module_platform_driver;
      @@
      -module_exit(e);
      +module_platform_driver(x);
      Signed-off-by: default avatarVaishali Thakkar <vthakkar1994@gmail.com>
      Signed-off-by: default avatarRobert Jarzmik <robert.jarzmik@free.fr>
      9754c8ef
    • Robert Jarzmik's avatar
      ARM: pxa: transition to dmaengine phase 1 · 4be0856f
      Robert Jarzmik authored
      In order to slowly transition pxa to dmaengine, the legacy code will now
      rely on dmaengine to request a channel.
      
      This implies that PXA architecture selects DMADEVICES and PXA_DMA,
      which is not pretty. Yet it enables PXA drivers to be ported one by one,
      with part of them using dmaengine, and the other part using the legacy
      code.
      Signed-off-by: default avatarRobert Jarzmik <robert.jarzmik@free.fr>
      4be0856f
  11. 17 Jul, 2015 1 commit
  12. 16 Jul, 2015 6 commits