1. 11 1月, 2013 1 次提交
  2. 20 11月, 2012 2 次提交
  3. 08 11月, 2012 1 次提交
    • S
      ARM: EXYNOS: Add missing static storage class specifiers in clock-exynos5.c · cbd40b38
      Sachin Kamat 提交于
      Fixes the following warnings:
      arch/arm/mach-exynos/clock-exynos5.c:300:19: warning:
      symbol 'exynos5_clk_mout_mpll' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:475:12: warning:
      symbol 'exynos5_clkset_aclk_top_list' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:480:23: warning:
      symbol 'exynos5_clkset_aclk' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:494:12: warning:
      symbol 'exynos5_clkset_aclk_333_166_list' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:499:23: warning:
      symbol 'exynos5_clkset_aclk_333_166' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:989:12: warning:
      symbol 'exynos5_clkset_group_list' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:1002:23: warning:
      symbol 'exynos5_clkset_group' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:1218:19: warning:
      symbol 'exynos5_clk_sclk_fimd1' was not declared. Should it be static?
      arch/arm/mach-exynos/clock-exynos5.c:1499:20: warning:
      symbol 'exynos5_clock_syscore_ops' was not declared. Should it be static?
      Signed-off-by: NSachin Kamat <sachin.kamat@linaro.org>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      cbd40b38
  4. 29 10月, 2012 2 次提交
  5. 19 10月, 2012 2 次提交
  6. 26 9月, 2012 1 次提交
  7. 21 9月, 2012 1 次提交
  8. 07 9月, 2012 1 次提交
  9. 29 8月, 2012 1 次提交
  10. 14 7月, 2012 1 次提交
  11. 20 5月, 2012 1 次提交
  12. 16 5月, 2012 1 次提交
  13. 15 5月, 2012 1 次提交
  14. 13 5月, 2012 1 次提交
  15. 21 4月, 2012 1 次提交
  16. 05 4月, 2012 1 次提交
    • K
      ARM: EXYNOS: Change System MMU platform device definitions · bca10b90
      KyongHo Cho 提交于
      Handling System MMUs with an identifier is not flexible to manage
      System MMU platform devices because of the following reasons:
      1. A device driver which needs to handle System MMU must know the ID.
      2. A System MMU may not present in some implementations of Exynos family.
      3. Handling System MMU with IOMMU API does not require an ID.
      
      This patch is the result of removing ID of System MMUs.
      Instead, a device driver that needs to handle its System MMU must
      use IOMMU API while its descriptor of platform device is given.
      
      This patch also includes the following enhancements:
      - A System MMU device becomes a child if its power domain device.
      - clkdev
      Signed-off-by: NKyongHo Cho <pullip.cho@samsung.com>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      bca10b90
  17. 14 3月, 2012 1 次提交