1. 17 7月, 2018 1 次提交
  2. 27 6月, 2018 1 次提交
    • C
      aspeed/scu: introduce clock frequencies · fda9aaa6
      Cédric Le Goater 提交于
      All Aspeed SoC clocks are driven by an input source clock which can
      have different frequencies : 24MHz or 25MHz, and also, on the Aspeed
      AST2400 SoC, 48MHz. The H-PLL (CPU) clock is defined from a
      calculation using parameters in the H-PLL Parameter register or from a
      predefined set of frequencies if the setting is strapped by hardware
      (Aspeed AST2400 SoC). The other clocks of the SoC are then defined
      from the H-PLL using dividers.
      
      We introduce first the APB clock because it should be used to drive
      the Aspeed timer model.
      Signed-off-by: NCédric Le Goater <clg@kaod.org>
      Reviewed-by: NAndrew Jeffery <andrew@aj.id.au>
      Message-id: 20180622075700.5923-2-clg@kaod.org
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      fda9aaa6
  3. 20 11月, 2017 1 次提交
    • J
      hw/arm/aspeed: Unlock SCU when running kernel · b6e70d1d
      Joel Stanley 提交于
      The ASPEED hardware contains a lock register for the SCU that disables
      any writes to the SCU when it is locked. The machine comes up with the
      lock enabled, but on all known hardware u-boot will unlock it and leave
      it unlocked when loading the kernel.
      
      This means the kernel expects the SCU to be unlocked. When booting from
      an emulated ROM the normal u-boot unlock path is executed. Things don't
      go well when booting using the -kernel command line, as u-boot does not
      run first.
      
      Change behaviour so that when a kernel is passed to the machine, set the
      reset value of the SCU to be unlocked.
      Signed-off-by: NJoel Stanley <joel@jms.id.au>
      Reviewed-by: NCédric Le Goater <clg@kaod.org>
      Message-id: 20171114122018.12204-1-joel@jms.id.au
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      b6e70d1d
  4. 27 12月, 2016 1 次提交
  5. 23 9月, 2016 2 次提交
  6. 14 7月, 2016 1 次提交
  7. 27 6月, 2016 1 次提交
    • A
      hw/misc: Add a model for the ASPEED System Control Unit · 1c8a2388
      Andrew Jeffery 提交于
      The SCU is a collection of chip-level control registers that manage the
      various functions supported by ASPEED SoCs. Typically the bits control
      interactions with clocks, external hardware or reset behaviour, and we
      can largly take a hands-off approach to reads and writes.
      
      Firmware makes heavy use of the state to determine how to boot, but the
      reset values vary from SoC to SoC (eg AST2400 vs AST2500). A qdev
      property is exposed so that the integrating SoC model can configure the
      silicon revision, which in-turn selects the appropriate reset values.
      Further qdev properties are exposed so the board model can configure the
      board-dependent hardware strapping.
      
      Almost all provided AST2400 reset values are specified by the datasheet.
      The notable exception is SOC_SCRATCH1, where we mark the DRAM as
      successfully initialised to avoid unnecessary dark corners in the SoC's
      u-boot support.
      Signed-off-by: NAndrew Jeffery <andrew@aj.id.au>
      Message-id: 1466744305-23163-2-git-send-email-andrew@aj.id.au
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      [PMM: drop unnecessary inttypes.h include]
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      1c8a2388