1. 20 Aug, 2021 6 commits
  2. 18 Aug, 2021 2 commits
  3. 17 Aug, 2021 2 commits
  4. 13 Aug, 2021 2 commits
    • JafarAkhondali's avatar
      platform/x86: acer-wmi: Add Turbo Mode support for Acer PH315-53 · ca42c119
      JafarAkhondali authored
      The Acer Predator Helios series (usually denoted by PHxxx-yy) features
      a particular key above the keyboard named "TURBO".
      The turbo key does 3 things:
      1. Set all fan's speeds to TURBO mode
      2. Overclocks the CPU and GPU in the safe range
      3. Turn on an LED just below the turbo button
      
      All the above actions are operating using WMI function calls,
      and there is no custom OC level for turbo. It acts as a flag
      for enabling turbo mode instead of telling processors to use
      a specific multiply of power (e.g. 1.3x of power).
      
      I've run some benchmark tests and it worked fine:
      
      GpuTest 0.7.0
      http://www.geeks3d.com
      
      Module: FurMark
      Normal mode Score: 7289 points (FPS: 121)
      Turbo mode Score: 7675 points (FPS: 127)
      Settings:
      - 1920x1080 fullscreen
      - antialiasing: Off
      - duration: 60000 ms
      
      Renderer:
      - GeForce RTX 2060/PCIe/SSE2
      - OpenGL: 4.6.0 NVIDIA 460.32.03
      
      This feature is presented by Acer officially and should not harm
      hardware in any case.
      
      A challenging part of implementing this feature is that calling
      overclock function requires knowing the exact count of fans
      for CPU and GPU of each model, which to the best of my
      knowledge is not available in the kernel.
      
      So after checking the official PredatorSense application methods, it
      turned out they have provided the software the list of fans in each model.
      I have access to the mentioned list, and all similar PH-iii-jj can be
      added easily by matching "DMI_PRODUCT_NAME".
      
      Creating a specific file for the Acer gaming features is not possible
      because the current in use WMI event GUID is required for the turbo button
      and it's not possible to register multiple listeners on a single WMI event.
      Signed-off-by: default avatarJafarAkhondali <jafar.akhoondali@gmail.com>
      Link: https://lore.kernel.org/r/20210812125307.1749207-1-jafar.akhoondali@gmail.comReviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      ca42c119
    • Hans de Goede's avatar
      platform/x86: Update Mario Limonciello's email address in the docs · 8599a12b
      Hans de Goede authored
      Various pdx86 docs under Documentation/ABI/testing still use Mario's
      old, now defunct, <mario.limonciello@dell.com> address.
      
      Update the docs to point to either the new Dell.Client.Kernel@dell.com
      email alias for Dell specific drivers, or to Mario's new @outlook.com
      address for other drivers.
      
      Cc: Dell.Client.Kernel@dell.com
      Cc: Mario Limonciello <mario.limonciello@outlook.com>
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Link: https://lore.kernel.org/r/20210810160900.106512-1-hdegoede@redhat.com
      8599a12b
  5. 12 Aug, 2021 19 commits
  6. 06 Aug, 2021 3 commits
  7. 29 Jul, 2021 1 commit
    • Hans de Goede's avatar
      platform/x86: Add and use a dual_accel_detect() helper · 153cca9c
      Hans de Goede authored
      Various 360 degree hinges (yoga) style 2-in-1 devices use 2 accelerometers
      to allow the OS to determine the angle between the display and the base of
      the device.
      
      On Windows these are read by a special HingeAngleService process which
      calls undocumented ACPI methods, to let the firmware know if the 2-in-1 is
      in tablet- or laptop-mode. The firmware may use this to disable the kbd and
      touchpad to avoid spurious input in tablet-mode as well as to report
      SW_TABLET_MODE info to the OS.
      
      Since Linux does not call these undocumented methods, the SW_TABLET_MODE
      info reported by various pdx86 drivers is incorrect on these devices.
      
      Before this commit the intel-hid and thinkpad_acpi code already had 2
      hardcoded checks for ACPI hardware-ids of dual-accel sensors to avoid
      reporting broken info.
      
      And now we also have a bug-report about the same problem in the intel-vbtn
      code. Since there are at least 3 different ACPI hardware-ids in play, add
      a new dual_accel_detect() helper which checks for all 3, rather then
      adding different hardware-ids to the drivers as bug-reports trickle in.
      Having shared code which checks all known hardware-ids is esp. important
      for the intel-hid and intel-vbtn drivers as these are generic drivers
      which are used on a lot of devices.
      
      The BOSC0200 hardware-id requires special handling, because often it is
      used for a single-accelerometer setup. Only in a few cases it refers to
      a dual-accel setup, in which case there will be 2 I2cSerialBus resources
      in the device's resource-list, so the helper checks for this.
      
      BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=209011Reported-and-tested-by: default avatarJulius Lehmann <julius@devpi.de>
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Reviewed-by: default avatarAndy Shevchenko <andy.shevchenko@gmail.com>
      Link: https://lore.kernel.org/r/20210729082134.6683-1-hdegoede@redhat.com
      153cca9c
  8. 28 Jul, 2021 2 commits
  9. 17 Jul, 2021 3 commits