1. 19 11月, 2012 1 次提交
  2. 12 11月, 2012 2 次提交
  3. 08 11月, 2012 3 次提交
    • 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
    • S
      ARM: EXYNOS: Make combiner_of_init function static · 96046ea3
      Sachin Kamat 提交于
      Silences the following warning:
      arch/arm/mach-exynos/common.c:576:12: warning:
      symbol 'combiner_of_init' 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>
      96046ea3
    • T
      ARM: EXYNOS: Make s3c_device_i2c0 always use id 0 · 62ef4a5d
      Tomasz Figa 提交于
      This patch removes compatibility definitions added long time ago when
      clock ids were used instead of devnames that were needed for platforms
      with only one i2c controller with id -1 (some s3c24xx's).
      
      Because currently devname field is used for matching device instances to
      clocks and if no devname is provided (as in clock-s3c2412.c and
      common-s3c2443.c for i2c clock, both in arch/arm/mach-s3c24xx) the clock
      is being matched only by name, so s3c_device_i2c0 can always have id 0.
      
      This patch solves the issue with i2c0 broken on boards where its the
      only i2c controller used, tested on Origen.
      Signed-off-by: NTomasz Figa <t.figa@samsung.com>
      Signed-off-by: NKyungmin Park <kyungmin.park@samsung.com>
      Reviewed-by: NSylwester Nawrocki <s.nawrocki@samsung.com>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      62ef4a5d
  4. 07 11月, 2012 2 次提交
  5. 30 10月, 2012 1 次提交
  6. 29 10月, 2012 2 次提交
  7. 27 10月, 2012 4 次提交
  8. 26 10月, 2012 1 次提交
  9. 25 10月, 2012 14 次提交
  10. 24 10月, 2012 3 次提交
  11. 23 10月, 2012 7 次提交