1. 25 12月, 2012 1 次提交
  2. 20 12月, 2012 5 次提交
    • P
      ARM: EXYNOS: Avoid passing the clks through platform data · fb0a2059
      Padmavathi Venna 提交于
      I2S controller has an internal mux for RCLK source clks. The list
      of source clk names were passed through platform data in non-dt case.
      The variable holding the list of RCLK source clk names is not
      required, as the list of clks need to be registered with clkdev
      using generic connection id. This is required as part of adding DT
      support for I2S controller driver.
      Signed-off-by: NPadmavathi Venna <padma.v@samsung.com>
      Acked-by: NSangbeom Kim <sbkim73@samsung.com>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      fb0a2059
    • D
      ARM: EXYNOS: Fix MSHC clocks instance names · 454696fd
      Dongjin Kim 提交于
      Replace clock instance name of MSHC controller for BIC and CIU of Exynos4412.
      Signed-off-by: NDongjin Kim <tobetter@gmail.com>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      454696fd
    • S
      ARM: EXYNOS: Fix NULL pointer dereference bug in SMDKV310 · 873673d3
      Sachin Kamat 提交于
      When DRM support for Samsung SoC and Samsung S3C framebuffer support
      are selected, the kernel crashes as it does not get the required
      platform data. Change the compile macro to CONFIG_DRM_EXYNOS_FIMD
      to fix this.
      Signed-off-by: NSachin Kamat <sachin.kamat@linaro.org>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      873673d3
    • S
      ARM: EXYNOS: Fix NULL pointer dereference bug in SMDK4X12 · bdd18532
      Sachin Kamat 提交于
      When DRM support for Samsung SoC and Samsung S3C framebuffer support
      are selected, the kernel crashes as it does not get the required
      platform data. Change the compile macro to CONFIG_DRM_EXYNOS_FIMD
      to fix this.
      
      Fixes the following boot time crash:
      Unable to handle kernel NULL pointer dereference at virtual address 00000000
      PC is at 0x0
      LR is at s3c_fb_probe+0x198/0x788
      [<c0152270>] (s3c_fb_probe+0x198/0x788) from [<c019e52c>] (platform_drv_probe+0x18/0x1c)
      [<c019e52c>] (platform_drv_probe+0x18/0x1c) from [<c019d2e4>] (driver_probe_device+0x70/0x1f0)
      [<c019d2e4>] (driver_probe_device+0x70/0x1f0) from [<c019d4f0>] (__driver_attach+0x8c/0x90)
      [<c019d4f0>] (__driver_attach+0x8c/0x90) from [<c019bc3c>] (bus_for_each_dev+0x50/0x7c)
      [<c019bc3c>] (bus_for_each_dev+0x50/0x7c) from [<c019cb4c>] (bus_add_driver+0x170/0x23c)
      [<c019cb4c>] (bus_add_driver+0x170/0x23c) from [<c019d9a4>] (driver_register+0x78/0x144)
      [<c019d9a4>] (driver_register+0x78/0x144) from [<c000862c>] (do_one_initcall+0x34/0x174)
      [<c000862c>] (do_one_initcall+0x34/0x174) from [<c020ed7c>] (kernel_init+0x100/0x2a0)
      [<c020ed7c>] (kernel_init+0x100/0x2a0) from [<c000e118>] (ret_from_fork+0x14/0x3c)
      Signed-off-by: NSachin Kamat <sachin.kamat@linaro.org>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      bdd18532
    • S
      ARM: EXYNOS: Fix NULL pointer dereference bug in Origen · 479dda22
      Sachin Kamat 提交于
      When DRM support for Samsung SoC and Samsung S3C framebuffer support
      are selected, the kernel crashes as it does not get the required
      platform data. Change the compile macro to CONFIG_DRM_EXYNOS_FIMD
      to fix this.
      
      Without this patch the following crash occurs during bootup:
      
      Unable to handle kernel NULL pointer dereference at virtual address 00000000
      PC is at 0x0
      LR is at s3c_fb_probe+0x198/0x788
      [<c01520e8>] (s3c_fb_probe+0x198/0x788) from [<c01a3dd4>] (platform_drv_probe+0x18/0x1c)
      [<c01a3dd4>] (platform_drv_probe+0x18/0x1c) from [<c01a2b8c>] (driver_probe_device+0x70/0x1f0)
      [<c01a2b8c>] (driver_probe_device+0x70/0x1f0) from [<c01a2d98>] (__driver_attach+0x8c/0x90)
      [<c01a2d98>] (__driver_attach+0x8c/0x90) from [<c01a14e4>] (bus_for_each_dev+0x50/0x7c)
      [<c01a14e4>] (bus_for_each_dev+0x50/0x7c) from [<c01a23f4>] (bus_add_driver+0x170/0x23c)
      [<c01a23f4>] (bus_add_driver+0x170/0x23c) from [<c01a324c>] (driver_register+0x78/0x144)
      [<c01a324c>] (driver_register+0x78/0x144) from [<c000862c>] (do_one_initcall+0x34/0x174)
      [<c000862c>] (do_one_initcall+0x34/0x174) from [<c01de210>] (kernel_init+0x100/0x2a0)
      [<c01de210>] (kernel_init+0x100/0x2a0) from [<c000e118>] (ret_from_fork+0x14/0x3c)
      Signed-off-by: NSachin Kamat <sachin.kamat@linaro.org>
      Signed-off-by: NKukjin Kim <kgene.kim@samsung.com>
      479dda22
  3. 19 12月, 2012 3 次提交
  4. 18 12月, 2012 1 次提交
  5. 07 12月, 2012 1 次提交
  6. 29 11月, 2012 1 次提交
    • D
      ARM: EXYNOS: Avoid early use of of_machine_is_compatible() · 5b7897db
      Doug Anderson 提交于
      The recent commit "ARM: EXYNOS: add support for EXYNOS5440 SoC" broke
      support for exynos5250 because of_machine_is_compatible() was used too
      early in the boot process.  It also probably meant that the exynos5440
      failed to use the proper iotable.  Switch to use
      of_flat_dt_is_compatible() in both of these cases.
      
      The failure I was seeing in exynos5250 because of this was:
        Division by zero in kernel.
        [<80015ed4>] (unwind_backtrace+0x0/0xec) from [<8045c7a4>] (dump_stack+0x20/0x24)
        [<8045c7a4>] (dump_stack+0x20/0x24) from [<80012990>] (__div0+0x20/0x28)
        [<80012990>] (__div0+0x20/0x28) from [<8021ab04>] (Ldiv0_64+0x8/0x18)
        [<8021ab04>] (Ldiv0_64+0x8/0x18) from [<80068560>] (__clocksource_updatefreq_scale+0x54/0x134)
        [<80068560>] (__clocksource_updatefreq_scale+0x54/0x134) from [<8006865c>] (__clocksource_register_scale+0x1c/0x54)
        [<8006865c>] (__clocksource_register_scale+0x1c/0x54) from [<80612a18>] (exynos_timer_init+0x100/0x1e8)
        [<80612a18>] (exynos_timer_init+0x100/0x1e8) from [<8060d184>] (time_init+0x28/0x38)
        [<8060d184>] (time_init+0x28/0x38) from [<8060a754>] (start_kernel+0x1e0/0x3c8)
        [<8060a754>] (start_kernel+0x1e0/0x3c8) from [<40008078>] (0x40008078)
      Signed-off-by: NDoug Anderson <dianders@chromium.org>
      Acked-by: NKukjin Kim <kgene.kim@samsung.com>
      [olofj: fixed two build errors, one missing include and one !CONFIG_OF failure]
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      5b7897db
  7. 28 11月, 2012 9 次提交
  8. 22 11月, 2012 1 次提交
  9. 21 11月, 2012 4 次提交
  10. 20 11月, 2012 7 次提交
  11. 19 11月, 2012 1 次提交
  12. 09 11月, 2012 1 次提交
  13. 08 11月, 2012 2 次提交
    • 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
  14. 07 11月, 2012 3 次提交