Skip to content
  1. Aug 19, 2017
  2. Aug 18, 2017
  3. Aug 06, 2017
  4. Aug 01, 2017
    • Caesar Wang's avatar
      arm64: dts: rockchip: update dynamic-power-coefficient for rk3399 · 45a995c0
      Caesar Wang authored
      
      
      This patch updates the dynamic-power-coefficient for big cluster on
      rk3399 SoCs.
      
      The dynamic power consumption of the CPU is proportional to the square of
      the Voltage (V) and the clock frequency (f). The coefficient is used to
      calculate the dynamic power as below -
      Pdyn = dynamic-power-coefficient * V^2 * f
      Where Voltage is in uV, frequency is in MHz.
      
      As the following is the tested data on rk3399's big cluster.
      frequency(MHz)  Voltage(V)  Current(mA) Dynamic-power-coefficient
      24              0.8         15
      48              0.8         23          ~417
      96              0.8         40          ~443
      216             0.8         82          ~438
      312             0.8         115         ~430
      408             0.8         150         ~455
      So the dynamic-power-coefficient average value is about 436.
      
      Signed-off-by: default avatarCaesar Wang <wxt@rock-chips.com>
      Signed-off-by: default avatarHeiko Stuebner <heiko@sntech.de>
      45a995c0
  5. Jul 23, 2017
  6. Jul 16, 2017
  7. May 30, 2017
  8. May 23, 2017
  9. Mar 23, 2017
    • Shawn Lin's avatar
      arm64: dts: rockchip: fix PCIe domain number for rk3399 · 41b464ef
      Shawn Lin authored
      
      
      It's suggested to fix the domain number for all PCIe
      host bridges or not set it at all. However, if we don't
      fix it, the domain number will keep increasing ever when
      doing unbind/bind test, which makes the bus tree of lspci
      introduce pointless domain hierarchy. More investigation shows
      the domain number allocater of PCI doesn't consider the conflict
      of domain number if we have more than one PCIe port belonging to
      different domains. So once unbinding/binding one of them and keep
      others would going to overflow the domain number so that finally
      it will share the same domain as others, but actually it shouldn't.
      We should fix the domain number for PCIe or invent new indexing
      ID mechanisms. However it isn't worth inventing new indexing ID
      mechanisms personlly, Just look at how other Root Complex drivers
      did, for instance, broadcom and qualcomm, it seems fixing the domain
      number was more popular. So this patch gonna fix the domain number
      of PCIe for rk3399.
      
      Signed-off-by: default avatarShawn Lin <shawn.lin@rock-chips.com>
      Reviewed-by: default avatarBrian Norris <briannorris@chromium.org>
      Tested-by: default avatarBrian Norris <briannorris@chromium.org>
      Signed-off-by: default avatarHeiko Stuebner <heiko@sntech.de>
      41b464ef
  10. Mar 22, 2017
  11. Mar 06, 2017
  12. Jan 14, 2017
  13. Jan 13, 2017
  14. Jan 06, 2017
  15. Jan 02, 2017
  16. Nov 21, 2016
  17. Nov 15, 2016
  18. Nov 14, 2016
  19. Nov 11, 2016
  20. Nov 09, 2016
  21. Nov 02, 2016
  22. Oct 16, 2016
  23. Sep 08, 2016
  24. Sep 06, 2016