1. 10 Sep, 2019 1 commit
  2. 09 Sep, 2019 4 commits
  3. 07 Sep, 2019 19 commits
  4. 16 Aug, 2019 9 commits
  5. 01 Aug, 2019 4 commits
    • Stephen Boyd's avatar
      platform/x86: intel_int0002_vgpio: Remove dev_err() usage after platform_get_irq() · f839b4b5
      Stephen Boyd authored
      We don't need dev_err() messages when platform_get_irq() fails now that
      platform_get_irq() prints an error message itself when something goes
      wrong. Let's remove these prints with a simple semantic patch.
      
      // <smpl>
      @@
      expression ret;
      struct platform_device *E;
      @@
      
      ret =
      (
      platform_get_irq(E, ...)
      |
      platform_get_irq_byname(E, ...)
      );
      
      if ( \( ret < 0 \| ret <= 0 \) )
      {
      (
      -if (ret != -EPROBE_DEFER)
      -{ ...
      -dev_err(...);
      -... }
      |
      ...
      -dev_err(...);
      )
      ...
      }
      // </smpl>
      
      While we're here, remove braces on if statements that only have one
      statement (manually).
      
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>
      Cc: Hans de Goede <hdegoede@redhat.com>
      Cc: "Darren Hart (VMware)" <dvhart@infradead.org>
      Cc: Roman Kiryanov <rkir@google.com>
      Cc: Vadim Pasternak <vadimp@mellanox.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarStephen Boyd <swboyd@chromium.org>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      f839b4b5
    • Stephen Boyd's avatar
      platform/x86: intel_bxtwc_tmu: Remove dev_err() usage after platform_get_irq() · b2dd2d9a
      Stephen Boyd authored
      We don't need dev_err() messages when platform_get_irq() fails now that
      platform_get_irq() prints an error message itself when something goes
      wrong. Let's remove these prints with a simple semantic patch.
      
      // <smpl>
      @@
      expression ret;
      struct platform_device *E;
      @@
      
      ret =
      (
      platform_get_irq(E, ...)
      |
      platform_get_irq_byname(E, ...)
      );
      
      if ( \( ret < 0 \| ret <= 0 \) )
      {
      (
      -if (ret != -EPROBE_DEFER)
      -{ ...
      -dev_err(...);
      -... }
      |
      ...
      -dev_err(...);
      )
      ...
      }
      // </smpl>
      
      While we're here, remove braces on if statements that only have one
      statement (manually).
      
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>
      Cc: Hans de Goede <hdegoede@redhat.com>
      Cc: "Darren Hart (VMware)" <dvhart@infradead.org>
      Cc: Roman Kiryanov <rkir@google.com>
      Cc: Vadim Pasternak <vadimp@mellanox.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarStephen Boyd <swboyd@chromium.org>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      b2dd2d9a
    • Stephen Boyd's avatar
      platform/mellanox: mlxreg-hotplug: Remove dev_err() usage after platform_get_irq() · eaae882c
      Stephen Boyd authored
      We don't need dev_err() messages when platform_get_irq() fails now that
      platform_get_irq() prints an error message itself when something goes
      wrong. Let's remove these prints with a simple semantic patch.
      
      // <smpl>
      @@
      expression ret;
      struct platform_device *E;
      @@
      
      ret =
      (
      platform_get_irq(E, ...)
      |
      platform_get_irq_byname(E, ...)
      );
      
      if ( \( ret < 0 \| ret <= 0 \) )
      {
      (
      -if (ret != -EPROBE_DEFER)
      -{ ...
      -dev_err(...);
      -... }
      |
      ...
      -dev_err(...);
      )
      ...
      }
      // </smpl>
      
      While we're here, remove braces on if statements that only have one
      statement (manually).
      
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>
      Cc: Hans de Goede <hdegoede@redhat.com>
      Cc: "Darren Hart (VMware)" <dvhart@infradead.org>
      Cc: Roman Kiryanov <rkir@google.com>
      Cc: Vadim Pasternak <vadimp@mellanox.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarStephen Boyd <swboyd@chromium.org>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      eaae882c
    • Stephen Boyd's avatar
      platform/x86: intel_pmc_ipc: Remove dev_err() usage after platform_get_irq() · 50944213
      Stephen Boyd authored
      We don't need dev_err() messages when platform_get_irq() fails now that
      platform_get_irq() prints an error message itself when something goes
      wrong. Let's remove these prints with a simple semantic patch.
      
      // <smpl>
      @@
      expression ret;
      struct platform_device *E;
      @@
      
      ret =
      (
      platform_get_irq(E, ...)
      |
      platform_get_irq_byname(E, ...)
      );
      
      if ( \( ret < 0 \| ret <= 0 \) )
      {
      (
      -if (ret != -EPROBE_DEFER)
      -{ ...
      -dev_err(...);
      -... }
      |
      ...
      -dev_err(...);
      )
      ...
      }
      // </smpl>
      
      While we're here, remove braces on if statements that only have one
      statement (manually).
      
      Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>
      Cc: Hans de Goede <hdegoede@redhat.com>
      Cc: "Darren Hart (VMware)" <dvhart@infradead.org>
      Cc: Roman Kiryanov <rkir@google.com>
      Cc: Vadim Pasternak <vadimp@mellanox.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarStephen Boyd <swboyd@chromium.org>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      50944213
  6. 30 Jul, 2019 3 commits
    • Daniel Drake's avatar
      platform/x86: asus-wmi: fix CPU fan control on recent products · e3168b87
      Daniel Drake authored
      Previously, asus-wmi was using the AGFN interface and FAN_CTRL device
      for CPU fan control. However, this code has been found to be not fully
      working on some recent products, and having checked the spec, these
      interfaces are marked as being removed from future products currently
      in development.
      
      The replacement appears to be the CPU_FAN device, added in spec version
      8.3 (March 2014) and present on many modern Asus laptops.
      
      Add support for this device, and use it whenever it is detected.
      The older approach based on AGFN and FAN_CTRL is used as a fallback
      on products that do not have such device.
      
      Other than switching between automatic and full speed, there is
      no fan speed control through this new interface.
      Signed-off-by: default avatarDaniel Drake <drake@endlessm.com>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      e3168b87
    • Daniel Drake's avatar
      platform/x86: asus-wmi: add a helper for device presence · f1fc0321
      Daniel Drake authored
      Factor out the WLAN LED and lightbar LED presence checks into a
      helper function, which will also be used by the upcoming CPU fan device
      support.
      Signed-off-by: default avatarDaniel Drake <drake@endlessm.com>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      f1fc0321
    • Daniel Drake's avatar
      platform/x86: asus-wmi: cleanup AGFN fan handling · 2889ffcf
      Daniel Drake authored
      The asus-wmi driver currently uses the "AGFN" interface and
      the FAN_CTRL device for fan control. According to the spec, this
      interface is very dated and marked as pending removal from products
      currently in development.
      
      Clean up the way that the AGFN fan is detected and handled, also
      preparing the driver for the introduction of an alternate fan
      control method needed to support recent Asus products.
      
      Not anticipating further development of this interface, simplify
      the code by dropping any notion of being able to control multiple
      AGFN fans (this was already limited to just a single fan through only
      exposing a single fan in sysfs).
      
      Check for the presence of AGFN fans at probe time, simplifying the code
      flow in asus_hwmon_sysfs_is_visible().
      Signed-off-by: default avatarDaniel Drake <drake@endlessm.com>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      2889ffcf