platform/x86: Switch back to struct platform_driver::remove()After commit 0edb555a65d1 ("platform: Make platform_driver::remove()return void") .remove() is (again) the right callback to implement
platform/x86: Switch back to struct platform_driver::remove()After commit 0edb555a65d1 ("platform: Make platform_driver::remove()return void") .remove() is (again) the right callback to implement forplatform drivers.Convert all platform drivers below drivers/platform/x86/ to use.remove(), with the eventual goal to drop structplatform_driver::remove_new(). As .remove() and .remove_new() have thesame prototypes, conversion is done by just changing the structuremember name in the driver initializer.While touching these files, make indention of the struct initializerconsistent in several files.Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>Link: https://lore.kernel.org/r/20241017073802.53235-2-u.kleine-koenig@baylibre.comReviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
show more ...
platform/x86: intel: int1092: intel_sar: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume
platform/x86: intel: int1092: intel_sar: Convert to platform remove callback returning voidThe .remove() callback for a platform driver returns an int which makesmany driver authors wrongly assume it's possible to do error handling byreturning an error code. However the value returned is (mostly) ignoredand this typically results in resource leaks. To improve here there is aquest to make the remove callback return void. In the first step of thisquest all drivers are converted to .remove_new() which already returnsvoid.Trivially convert this driver from always returning zero in the removecallback to the void returning variant.Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>Link: https://lore.kernel.org/r/20230302144732.1903781-21-u.kleine-koenig@pengutronix.deReviewed-by: Hans de Goede <hdegoede@redhat.com>Signed-off-by: Hans de Goede <hdegoede@redhat.com>
platform/x86: int1092: Switch to use acpi_evaluate_dsm_typed()The acpi_evaluate_dsm_typed() provides a way to check the type of theobject evaluated by _DSM call. Use it instead of open coded varia
platform/x86: int1092: Switch to use acpi_evaluate_dsm_typed()The acpi_evaluate_dsm_typed() provides a way to check the type of theobject evaluated by _DSM call. Use it instead of open coded variant.Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>Link: https://lore.kernel.org/r/20230119180904.78446-1-andriy.shevchenko@linux.intel.comReviewed-by: Hans de Goede <hdegoede@redhat.com>Signed-off-by: Hans de Goede <hdegoede@redhat.com>
platform/x86: int1092: Fix non sequential device mode handlingSAR information from BIOS may come in non sequential pattern.To overcome the issue, a check is made to extract the right SARinformat
platform/x86: int1092: Fix non sequential device mode handlingSAR information from BIOS may come in non sequential pattern.To overcome the issue, a check is made to extract the right SARinformation using the device mode which is currently being used.Remove .owner field if calls are used which set it automatically.Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocciSigned-off-by: Shravan S <s.shravan@intel.com>Link: https://lore.kernel.org/r/20211006073525.1332925-1-s.shravan@intel.comSigned-off-by: Hans de Goede <hdegoede@redhat.com>Reviewed-by: Hans de Goede <hdegoede@redhat.com>
platform/x86: BIOS SAR driver for Intel M.2 ModemDynamic BIOS SAR driver exposing dynamic SAR information from BIOSThe Dynamic SAR (Specific Absorption Rate) driver uses ACPI DSM(Device Specific
platform/x86: BIOS SAR driver for Intel M.2 ModemDynamic BIOS SAR driver exposing dynamic SAR information from BIOSThe Dynamic SAR (Specific Absorption Rate) driver uses ACPI DSM(Device Specific Method) to communicate with BIOS and retrievedynamic SAR information and change notifications. The driver usessysfs to expose this data to userspace via read and notify.Sysfs interface is documented in detail under:Documentation/ABI/testing/sysfs-driver-intc_sarSigned-off-by: Shravan S <s.shravan@intel.com>Link: https://lore.kernel.org/r/20210723211452.27995-2-s.shravan@intel.comReviewed-by: Hans de Goede <hdegoede@redhat.com>Signed-off-by: Hans de Goede <hdegoede@redhat.com>