An error occurred fetching the project authors.
  1. 24 Jul, 2015 1 commit
    • Tony Lindgren's avatar
      ARM: OMAP2+: Add custom abort handler for t410 · f5887fe5
      Tony Lindgren authored
      Similar to commit fdf4850c ("ARM: BCM5301X: workaround suppress fault"),
      let's add custom handling for the aborts on t410 that prevent booting:
      
      Unhandled fault: imprecise external abort (0xc06) at 0xee091fb0
      pgd = ee4bc000
      [ee091fb0] *pgd=ae00041e(bad)
      Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000007
      
      Cc: Matthijs van Duin <matthijsvanduin@gmail.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      f5887fe5
  2. 21 Jul, 2015 2 commits
  3. 14 Jul, 2015 1 commit
  4. 20 May, 2015 1 commit
  5. 24 Mar, 2015 2 commits
  6. 19 Mar, 2015 1 commit
  7. 06 Mar, 2015 1 commit
  8. 13 Jan, 2015 1 commit
  9. 22 Nov, 2014 1 commit
  10. 12 Nov, 2014 1 commit
  11. 31 Oct, 2014 1 commit
  12. 18 Sep, 2014 2 commits
  13. 16 Sep, 2014 1 commit
  14. 11 Sep, 2014 1 commit
  15. 09 Sep, 2014 1 commit
  16. 08 Sep, 2014 3 commits
  17. 20 May, 2014 1 commit
  18. 13 May, 2014 1 commit
  19. 04 Apr, 2014 1 commit
  20. 12 Mar, 2014 2 commits
  21. 04 Mar, 2014 2 commits
  22. 28 Feb, 2014 4 commits
  23. 27 Feb, 2014 1 commit
    • Tony Lindgren's avatar
      ARM: OMAP3: Fix pinctrl interrupts for core2 · 4b416368
      Tony Lindgren authored
      After splitting padconf core into two parts to avoid exposing
      unaccessable registers, the new padconf core2 domain was left
      without a wake-up interrupt.
      
      Fix the issue by passing the shared wake-up interrupt in
      platform data like we do for padconf core and wkup domains
      already.
      
      Fixes: 3d495383 (ARM: dts: Split omap3 pinmux core device)
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      4b416368
  24. 21 Feb, 2014 1 commit
  25. 18 Dec, 2013 1 commit
  26. 08 Dec, 2013 2 commits
    • Tony Lindgren's avatar
      ARM: OMAP2+: Use pdata quirks for emac on am3517 · 71900314
      Tony Lindgren authored
      As the emac uses the system control module registers for
      reset and interrupts, we need to pass those in the platform
      data until we have a separate system control module driver.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      71900314
    • Tony Lindgren's avatar
      ARM: OMAP2+: Add support for legacy auxdata for twl · dad12d11
      Tony Lindgren authored
      As we currently need to support a mix of legacy platform data and
      device tree intialized data, let's make sure things keep working
      for the TWL GPIOs.
      
      Mostly the issue is caused by the fact that DSS does not yet have
      device tree bindings, so we need to rely on the TWL GPIO callback
      for setting up things like LCD backlight for some boards.
      
      As of_platform_populate() for the TWL GPIO is called by twl-core
      after the I2C bus has been initialized, we cannot pass the auxdata
      table from the board init code to twl-core like we used to with
      just legacy platform data.
      
      So let's use the omap_device bus hook to patch in the platform
      data for TWL GPIO until we have sorted out the issues with the
      TWL GPIOs and device tree bindings.
      
      The other option was be to initialize twl core using legacy
      platform data, which seems like a step backwards as we're moving
      to device tree only initialization.  And we really don't want to
      add custom configuration functions to the TWL GPIO driver either
      for this.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      dad12d11
  27. 25 Nov, 2013 3 commits