1. 26 11月, 2016 1 次提交
  2. 19 11月, 2016 2 次提交
    • L
      ARM: dts: Add Integrator/AP cpus node and operating points · 964971c8
      Linus Walleij 提交于
      This adds the cpus node to the Integrator/AP device tree so
      that we have a proper placeholder to put in the DT-defined
      operating points for the generic DT/OPP cpufreq driver,
      along with the proper operating points.
      
      The old Integrator cpufreq driver would resolve the max
      frequency to 71MHz, and the min frequency to 12 MHz, but
      the clock driver can actually handle any frequency inbetween
      so I picked a few select frequencies as OPPs. The cpufreq
      framework doesn't seem to deal with sliding frequency scales,
      only fixed points so 7 OPPs is better than 2 atleast.
      
      We define a CPU node since this is required for cpufreq-dt,
      however we do not define any compatible string for the CPU
      since this architecture has pluggable CPU modules and we
      do not know which one will be used. If necessary, the CPU
      compatible can be filled in by the boot loader, but for
      just cpufreq-dt it is not required.
      
      Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
      Cc: Viresh Kumar <viresh.kumar@linaro.org>
      Cc: Russell King <linux@armlinux.org.uk>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      964971c8
    • L
      ARM: dts: Add Integrator/CP cpus node and operating points · 426610dd
      Linus Walleij 提交于
      This adds the cpus node to the Integrator/CP device tree so
      that we have a proper placeholder to put in the DT-defined
      operating points for the generic DT/OPP cpufreq driver,
      along with two working operating points.
      
      I have only put in 48 and 50 MHz because going to e.g. 36
      MHz hangs the system when CLCD graphics are active.
      Presumably the memory bus gets to slow to feed the display
      and the systems hangs for this reason. The ideal solution
      would be for the display controller to put constraints on
      the memory bus frequency, but that need to be a separate
      longer-term project.
      
      We define a CPU node since this is required for cpufreq-dt,
      however we do not define any compatible string for the CPU
      since this architecture has pluggable CPU modules and we
      do not know which one will be used. If necessary, the CPU
      compatible can be filled in by the boot loader, but for
      just cpufreq-dt it is not required.
      
      Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
      Cc: Viresh Kumar <viresh.kumar@linaro.org>
      Cc: Russell King <linux@armlinux.org.uk>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      426610dd
  3. 16 11月, 2016 1 次提交
    • T
      ARM: dts: Add minimal support for motorola droid 4 xt894 · 7e2f8c0a
      Tony Lindgren 提交于
      Let's add minimal support for droid 4 with MMC and WLAN working.
      It can be booted with appended dtb using kexec to a state where
      MMC and WLAN work with currently no support for it's PMIC or
      display.
      
      Note that we are currently using fixed regulators as we don't
      have support for it's cpcap PMIC. I'll be posting regmap_spi
      based minimal cpcap patches later on for USB and the debug
      UART on droid 4 multiplexed with the USB connector.
      
      Cc: Marcel Partap <mpartap@gmx.net>
      Cc: Michael Scott <michael.scott@linaro.org>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      7e2f8c0a
  4. 15 11月, 2016 8 次提交
  5. 14 11月, 2016 7 次提交
  6. 11 11月, 2016 2 次提交
  7. 10 11月, 2016 19 次提交