Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
大约 1 年 前同步成功

通知 158
Star 36
Fork 7
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 17 3月, 2015 1 次提交
  3. 14 3月, 2015 1 次提交
  5. 13 3月, 2015 3 次提交
  7. 02 2月, 2015 3 次提交
  9. 15 1月, 2015 3 次提交
  11. 02 12月, 2014 1 次提交
  13. 27 11月, 2014 2 次提交
  15. 22 11月, 2014 2 次提交
  17. 21 11月, 2014 1 次提交
  19. 19 11月, 2014 3 次提交
  21. 13 11月, 2014 1 次提交
  23. 04 11月, 2014 3 次提交
  25. 02 10月, 2014 1 次提交
  27. 22 9月, 2014 1 次提交
  29. 19 9月, 2014 1 次提交
  31. 17 9月, 2014 1 次提交
  33. 15 9月, 2014 1 次提交
  35. 25 8月, 2014 1 次提交
  37. 20 8月, 2014 1 次提交
  39. 20 12月, 2013 1 次提交
  41. 02 12月, 2013 1 次提交
    • B
      ARM: at91: add Kconfig options for common clk support · c8a8c630
      由 Boris BREZILLON 提交于 
      This patch adds the following Kconfig options to prepare the transition to
common clk framework:

- AT91_USE_OLD_CLK: this option is selected by every SoC which does not
  support new at91 clks based on common clk framework (SoC which does not
  define the clock tree in its device tree).
  This options is also selected when the user choose non dt boards support
  (new at91 clks can only be registered from a device tree definition).

- COMMON_CLK_AT91: this option cannot be selected directly. Instead it is
  enabled if these 3 conditions are met:
   * at least one of the selected SoCs have a PMC (Power Management
     Controller) Unit
   * device tree support is enabled
   * the old at91 clk implementation is disabled (every selected SoC define
     its clks in its device tree and non dt boards support is disabled)

- OLD_CLK_AT91: this option cannot be selected directly. Instead it is
  enabled if these 2 conditions are met:
   * at least one of the selected SoCs have a PMC (Power Management
     Controller) Unit
   * at least one of the selected SoCs does not define its clks in its
     device tree or non dt-boards support is enabled

This patch selects AT91_USE_OLD_CLK in all currently supported SoCs. These
selects will be removed after clk definitions are properly added in each
soc's device tree.
It also selects AT91_USE_OLD_CLK in all non-dt boards support.

AT91_PMC_UNIT references are replaced by OLD_CLK_AT91, because PMC Unit is
enabled for both old and common clk implementations, and old clk
implementation should not be compiled if COMMON_CLK is enabled.

To avoid future link errors, a new stub is created for at91_dt_clock_init
function if OLD_CLK_AT91 is disabled.

A new check is added in dt init functions (setup.c) to prepare for SoCs
supporting new clk implementation. These SoCs won't setup the
register_clocks callback (clk registration is done using of_clk_init).
Signed-off-by: NBoris BREZILLON <b.brezillon@overkiz.com>
Acked-by: NMike Turquette <mturquette@linaro.org>
Signed-off-by: NNicolas Ferre <nicolas.ferre@atmel.com>
      c8a8c630
  43. 15 11月, 2013 1 次提交
    • J
      ARM: at91: fix hanged boot due to early rtc-interrupt · 6de714c2
      由 Johan Hovold 提交于 
      Make sure the RTC-interrupts are masked at boot by adding a new helper
function to be used at SOC-init.

This fixes hanged boot on all AT91 SOCs with an RTC (but RM9200), for
example, after a reset during an RTC-update or if an RTC-alarm goes off
after shutdown (e.g. when using RTC wakeup).

The RTC and RTT-peripherals are powered by backup power (VDDBU) (on all
AT91 SOCs but RM9200) and are not reset on wake-up, user, watchdog or
software reset. This means that their interrupts may be enabled during
early boot if, for example, they where not disabled during a previous
shutdown (e.g. due to a buggy driver or a non-clean shutdown such as a
user reset). Furthermore, an RTC or RTT-alarm may also be active.

The RTC and RTT-interrupts use the shared system-interrupt line, which
is also used by the PIT, and if an interrupt occurs before a handler
(e.g. RTC-driver) has been installed this leads to the system interrupt
being disabled and prevents the system from booting.

Note that when boot hangs due to an early RTC or RTT-interrupt, the only
way to get the system to start again is to remove the backup power (e.g.
battery) or to disable the interrupt manually from the bootloader. In
particular, a user reset is not sufficient.
Signed-off-by: NJohan Hovold <jhovold@gmail.com>
Signed-off-by: NNicolas Ferre <nicolas.ferre@atmel.com>
Cc: stable@vger.kernel.org # 3.11.x
      6de714c2
  45. 17 10月, 2013 1 次提交
  47. 18 6月, 2013 1 次提交
  49. 31 5月, 2013 1 次提交
  51. 17 5月, 2013 1 次提交
  53. 26 3月, 2013 2 次提交