1. 16 Sep, 2019 1 commit
  2. 21 Aug, 2019 1 commit
  3. 08 Jul, 2019 1 commit
    • Arnd Bergmann's avatar
      power: reset: nvmem-reboot-mode: add CONFIG_OF dependency · caa2b557
      Arnd Bergmann authored
      Without CONFIG_OF, we get a build failure in the reboot-mode
      implementation:
      
      drivers/power/reset/reboot-mode.c: In function 'reboot_mode_register':
      drivers/power/reset/reboot-mode.c:72:2: error: implicit declaration of function 'for_each_property_of_node'; did you mean 'for_each_child_of_node'? [-Werror=implicit-function-declaration]
        for_each_property_of_node(np, prop) {
      
      Add a Kconfig dependency like we have for the other users of
      CONFIG_REBOOT_MODE.
      
      Fixes: 7a78a7f7 ("power: reset: nvmem-reboot-mode: use NVMEM as reboot mode write interface")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarSebastian Reichel <sebastian.reichel@collabora.com>
      caa2b557
  4. 04 Jul, 2019 1 commit
  5. 28 Jun, 2019 2 commits
    • Enric Balletbo i Serra's avatar
      power: supply: cros: allow to set input voltage and current limit · 2ffb500d
      Enric Balletbo i Serra authored
      This patch allows reading and writing the input voltage and current
      limit through the POWER_SUPPLY_PROP_INPUT_VOLTAGE_LIMIT and
      POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT sysfs properties. This allows
      userspace to see current values and to re-configure these values at
      runtime based on system-level knowledge or user input.
      
      By default there is no limit, this is reported as a -1 when reading from
      userspace. Writing a value will set the current or voltage limit in uA
      or uV, and writing any negative value will remove that limit.
      Signed-off-by: default avatarEnric Balletbo i Serra <enric.balletbo@collabora.com>
      Reviewed-by: default avatarGuenter Roeck <groeck@chromium.org>
      Signed-off-by: default avatarSebastian Reichel <sebastian.reichel@collabora.com>
      2ffb500d
    • Enric Balletbo i Serra's avatar
      power: supply: add input power and voltage limit properties · a4496d52
      Enric Balletbo i Serra authored
      For thermal management strategy you might be interested on limit the
      input power for a power supply. We already have current limit but
      basically what we probably want is to limit power. So, introduce the
      input_power_limit property.
      
      Although the common use case is limit the input power, in some
      specific cases it is the voltage that is problematic (i.e some regulators
      have different efficiencies at higher voltage resulting in more heat).
      So introduce also the input_voltage_limit property.
      
      This happens in one Chromebook and is used on the Pixel C's thermal
      management strategy to effectively limit the input power to 5V 3A when
      the screen is on. When the screen is on, the display, the CPU, and the GPU
      all contribute more heat to the system than while the screen is off, and
      we made a tradeoff to throttle the charger in order to give more of the
      thermal budget to those other components.
      
      So there's nothing fundamentally broken about the hardware that would
      cause the Pixel C to malfunction if we were charging at 9V or 12V instead
      of 5V when the screen is on, i.e. if userspace doesn't change this.
      
      What would happen is that you wouldn't meet Google's skin temperature
      targets on the system if the charger was allowed to run at 9V or 12V with
      the screen on.
      
      For folks hacking on Pixel Cs (which is now outside of Google's official
      support window for Android) and customizing their own kernel and userspace
      this would be acceptable, but we wanted to expose this feature in the
      power supply properties because the feature does exist in the Emedded
      Controller firmware of the Pixel C and all of Google's Chromebooks with
      USB-C made since 2015 in case someone running an up to date kernel wanted
      to limit the charging power for thermal or other reasons.
      
      This patch exposes a new property, similar to input current limit, to
      re-configure the maximum voltage from the external supply at runtime
      based on system-level knowledge or user input.
      Signed-off-by: default avatarEnric Balletbo i Serra <enric.balletbo@collabora.com>
      Reviewed-by: default avatarGuenter Roeck <groeck@chromium.org>
      Acked-by: default avatarAdam Thomson <Adam.Thomson.Opensource@diasemi.com>
      Reviewed-by: default avatarBenson Leung <bleung@chromium.org>
      Signed-off-by: default avatarSebastian Reichel <sebastian.reichel@collabora.com>
      a4496d52
  6. 27 Jun, 2019 1 commit
  7. 26 Jun, 2019 1 commit
  8. 25 Jun, 2019 1 commit
  9. 24 Jun, 2019 1 commit
  10. 23 Jun, 2019 10 commits
  11. 21 Jun, 2019 1 commit
  12. 19 Jun, 2019 2 commits
  13. 18 Jun, 2019 1 commit
  14. 14 Jun, 2019 1 commit
  15. 05 Jun, 2019 5 commits
  16. 30 May, 2019 10 commits