Heiko Stübner | 4 Aug 21:36 2015
Picon

[PATCH 1/2 RESEND] PM / AVS: rockchip-io: depend on CONFIG_POWER_AVS

The rockchip io-domain driver currently only depends on ARCH_ROCKCHIP
itself. This makes it possible to select the power-domain driver, but
not the POWER_AVS class and results in the iodomain-driver not getting
build in this case.

So add the additional dependency, which also results in the driver
config option now being placed nicely into the AVS submenu.

Fixes: 662a958638bd ("PM / AVS: rockchip-io: add driver handling Rockchip io domains")
Signed-off-by: Heiko Stuebner <heiko <at> sntech.de>
Acked-by: Kevin Hilman <khilman <at> linaro.org>
---
Kevin wrote when he Acked the patch: "Rafael, feel free to queue this
up as a fix.  I don't have any other drivers/power/avs stuff queued up."

Although I don't know if this is the case anymore.

 drivers/power/avs/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/power/avs/Kconfig b/drivers/power/avs/Kconfig
index 7f3d389..a67eeac 100644
--- a/drivers/power/avs/Kconfig
+++ b/drivers/power/avs/Kconfig
 <at>  <at>  -13,7 +13,7  <at>  <at>  menuconfig POWER_AVS

 config ROCKCHIP_IODOMAIN
         tristate "Rockchip IO domain support"
-        depends on ARCH_ROCKCHIP && OF
+        depends on POWER_AVS && ARCH_ROCKCHIP && OF
(Continue reading)

Andreas Dannenberg | 4 Aug 18:36 2015
Picon

[PATCH RESEND] power: bq24190_charger: Fix charge type sysfs property

Access to the BQ24190's configurable charge type property (none, trickle,
fast) is being masked by an incorrect power_supply_property entry. After
applying this patch a new 'charge_type' property will appear in the
bq24190-charger sysfs folder backed up by getters/setters already
present in the driver.

Signed-off-by: Andreas Dannenberg <dannenberg <at> ti.com>
---
This is a RESEND of yesterday's patch that for some reason did not seem to
have gotten picked up correctly...

The current driver incorrectly tries to declare the charge type property
using POWER_SUPPLY_PROP_TYPE which is the wrong declaration for this
(actually POWER_SUPPLY_PROP_TYPE itself has been superseeded by
power_supply.type and isn't even used anymore as part of the power
supply property declarations).

After implementing the fix tested this aspect of the driver using an
actual BQ24190 device and could witness the impact the change of charge
type has on the battery (writing '1' to the new sysfs property means
charging off, '2' will do trickle charging, and '3' will result in
fast charging).

 drivers/power/bq24190_charger.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/power/bq24190_charger.c b/drivers/power/bq24190_charger.c
index 052db78..40ae47c 100644
--- a/drivers/power/bq24190_charger.c
+++ b/drivers/power/bq24190_charger.c
(Continue reading)

Dmitry Torokhov | 4 Aug 18:33 2015
Picon

[PATCH] thermal: power_allocator: do not use devm* interfaces

The code in question is called outside of standard driver
probe()/remove() callbacks and thus will not benefit from use of devm*
infrastructure.

Signed-off-by: Dmitry Torokhov <dmitry.torokhov <at> gmail.com>
---
 drivers/thermal/power_allocator.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/thermal/power_allocator.c b/drivers/thermal/power_allocator.c
index 13ccf00..e9ba29f 100644
--- a/drivers/thermal/power_allocator.c
+++ b/drivers/thermal/power_allocator.c
 <at>  <at>  -334,7 +334,7  <at>  <at>  static int allocate_power(struct thermal_zone_device *tz,
 				      max_allocatable_power, current_temp,
 				      control_temp - current_temp);

-	devm_kfree(&tz->device, req_power);
+	kfree(req_power);
 unlock:
 	mutex_unlock(&tz->lock);

 <at>  <at>  -426,7 +426,7  <at>  <at>  static int power_allocator_bind(struct thermal_zone_device *tz)
 		return -EINVAL;
 	}

-	params = devm_kzalloc(&tz->device, sizeof(*params), GFP_KERNEL);
+	params = kzalloc(sizeof(*params), GFP_KERNEL);
 	if (!params)
 		return -ENOMEM;
(Continue reading)

Adam Thomson | 4 Aug 18:16 2015

[PATCH v4 0/6] Add support for DA9150 Fuel-Gauge

This patch set adds support for the Dialog DA9150 Fuel-Gauge.

In this patch set the following is provided:
 - MFD Core and DT bindings updates.
 - Power Supply Fuel-Gauge support and DT bindings documentation.

This patch set is baselined against the v4.2-rc5 kernel version.

Changes in v4:
 - MFD, Power, DT: Update DT compatible & driver name strings for Fuel Gauge,
                   in line with maintainers request.
 - Power: Update Kconfig and Makefile to use BATTERY_* for config entry instead
          of FG_*. Also fuel-gauge module now depends on MFD not Charger.
 - Power: Added helper function to simplify single attribute accesses using QIF
          interface of fuel-gauge.
 - Power: Use of devm_* functions for IRQ and power_supply registration.
 - Power: Added checking of result from platform_get_irq_byname().

Changes in v3:
 - MFD: Some tidy up of code (gotos, dropped FG header, DEFINE_RES_IRQ_NAMED)
 - MFD & Power: Drop use of callback function for temperature reading, as
                requested by Lee Jones.
 - MFD (DT): Binding doc update to flesh out example text.
 - MFD (DT): New patch to change MFD binding doc to use relative paths.
 - MFD: New patch to use DEFINE_RES_IRQ_NAMED for all other IRQ resources.

Changes in v2:
 - Moved temp callback function prototype to be part of power fuel-gauge patch,
   as requested by Lee Jones.

(Continue reading)

Kukjin Kim | 4 Aug 09:45 2015

[PATCH] cpufreq: exynos: Fix for memory leak in case SoC name does not match

From: Shailendra Verma <shailendra.capricorn <at> gmail.com>

During probe free the memory allocated to "exynos_info" in case of
unknown SoC type.

Signed-off-by: Shailendra Verma <shailendra.capricorn <at> gmail.com>
Acked-by: Viresh Kumar <viresh.kumar <at> linaro.org>
Acked-by: Lukasz Majewski <l.majewski <at> samsung.com>
[k.kozlowski: Rebased the patch around if(of_machine_is_compatible)]
Signed-off-by: Krzysztof Kozlowski <k.kozlowski <at> samsung.com>
Signed-off-by: Kukjin Kim <kgene <at> kernel.org>
---
Hi Rafael and Viresh,

Since this is a fix to prevent memory leak, it would be better if
this could be sent to linus during -rc via cpufreq tree.

Thanks,
Kukjin

 drivers/cpufreq/exynos-cpufreq.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
index ae5b2bd..fa3dd84 100644
--- a/drivers/cpufreq/exynos-cpufreq.c
+++ b/drivers/cpufreq/exynos-cpufreq.c
 <at>  <at>  -180,7 +180,7  <at>  <at>  static int exynos_cpufreq_probe(struct platform_device *pdev)
 		ret = exynos5250_cpufreq_init(exynos_info);
 	} else {
(Continue reading)

Xunlei Pang | 4 Aug 07:48 2015

[PATCH v2 1/3] cpuidle/coupled: Remove cpuidle_device::safe_state_index

From: Xunlei Pang <pang.xunlei <at> linaro.org>

cpuidle_device::safe_state_index need to be initialized before
use, it should be the same as cpuidle_driver::safe_state_index.

We tackled this issue by removing the safe_state_index from the
cpuidle_device structure and use the one in the cpuidle_driver
structure instead.

Suggested-by: Daniel Lezcano <daniel.lezcano <at> linaro.org>
Signed-off-by: Xunlei Pang <pang.xunlei <at> linaro.org>
---
 drivers/cpuidle/coupled.c | 4 ++--
 include/linux/cpuidle.h   | 1 -
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/cpuidle/coupled.c b/drivers/cpuidle/coupled.c
index 7936dce..6493e40 100644
--- a/drivers/cpuidle/coupled.c
+++ b/drivers/cpuidle/coupled.c
 <at>  <at>  -473,7 +473,7  <at>  <at>  int cpuidle_enter_state_coupled(struct cpuidle_device *dev,
 			return entered_state;
 		}
 		entered_state = cpuidle_enter_state(dev, drv,
-			dev->safe_state_index);
+			drv->safe_state_index);
 		local_irq_disable();
 	}

 <at>  <at>  -521,7 +521,7  <at>  <at>  retry:
(Continue reading)

Zhang Rui | 4 Aug 07:29 2015
Picon

[PATCH V2] thermal: Add Intel PCH thermal driver

From d0a12625d2ff2c63321b3cf48c48184748ab577a Mon Sep 17 00:00:00 2001
From: Tushar Dave <tushar.n.dave <at> intel.com>
Date: Wed, 10 Jun 2015 13:34:24 -0700
Subject: [PATCH V2] thermal: Add Intel PCH thermal driver

This change adds a thermal driver for Wildcat Point platform controller
hub. This driver register PCH thermal sensor as a thermal zone and
associate critical and hot trips if present.

Signed-off-by: Tushar Dave <tushar.n.dave <at> intel.com>
Reviewed-by: Pandruvada, Srinivas <srinivas.pandruvada <at> intel.com>
Signed-off-by: Zhang Rui <rui.zhang <at> intel.com>
---
 drivers/thermal/Kconfig             |   8 +
 drivers/thermal/Makefile            |   1 +
 drivers/thermal/intel_pch_thermal.c | 286 ++++++++++++++++++++++++++++++++++++
 3 files changed, 295 insertions(+)
 create mode 100644 drivers/thermal/intel_pch_thermal.c

diff --git a/drivers/thermal/Kconfig b/drivers/thermal/Kconfig
index 118938e..0390044 100644
--- a/drivers/thermal/Kconfig
+++ b/drivers/thermal/Kconfig
 <at>  <at>  -340,6 +340,14  <at>  <at>  config ACPI_THERMAL_REL
 	tristate
 	depends on ACPI

+config INTEL_PCH_THERMAL
+	tristate "Intel PCH Thermal Reporting Driver"
+	depends on X86 && PCI
(Continue reading)

kbuild test robot | 4 Aug 02:09 2015
Picon

[PATCH] thermal: pch_dev_ops_wpt can be static


Signed-off-by: Fengguang Wu <fengguang.wu <at> intel.com>
---
 intel_pch_thermal.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/thermal/intel_pch_thermal.c b/drivers/thermal/intel_pch_thermal.c
index d9e07fd..a1393e1 100644
--- a/drivers/thermal/intel_pch_thermal.c
+++ b/drivers/thermal/intel_pch_thermal.c
 <at>  <at>  -137,7 +137,7  <at>  <at>  struct pch_dev_ops {

 
 /* dev ops for Wildcat Point */
-struct pch_dev_ops pch_dev_ops_wpt = {
+static struct pch_dev_ops pch_dev_ops_wpt = {
 	.hw_init = pch_wpt_init,
 	.get_temp = pch_wpt_get_temp,
 };
Srinivas Pandruvada | 3 Aug 13:13 2015
Picon

[PATCH v1] thermal: kconfig: select THERMAL_WRITABLE_TRIPS for x86 thermal

v1
Amended commit message to be clear that RW trips are required for the user space
thermal tools for x86.

v0
base version

Srinivas Pandruvada (1):
  thermal: kconfig: select THERMAL_WRITABLE_TRIPS for x86 thermal

 drivers/thermal/Kconfig | 3 +++
 1 file changed, 3 insertions(+)

--

-- 
2.4.3

--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Rafael J. Wysocki | 3 Aug 16:17 2015
Picon

[Notice] ACPI+PM maintenance in vacation mode Aug 8 - Aug 23

Hi All,

FYI, I will be out of office and traveling between August 8 and 23, and it will
be rather hard for me to reply to email during (the majority of) that time, so
if you have new core ACPI/PM material for me to queue up for 4.3, please send
it this week (and rather not of Friday if you will).

Urgent fixes will still be processed as usual.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-pm" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

MyungJoo Ham | 3 Aug 08:32 2015

[PULL REQUEST] PM / devfreq, for Next-RC (fix, drv update)

Dear Rafael,

Here goes a pull request from devfreq:
1. Added PPMUv2 hardware support (for recent Exynos series)
2. Corrected documentation


Cheers,
MyungJoo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The following changes since commit 74d33293e467df61de1b1d8b2fbe29e550dec33b:

  Linux 4.2-rc5 (2015-08-02 18:34:55 -0700)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git tags/pull_req_20150803

for you to fetch changes up to a622789aeebdeaa52d68bbc3930edbc3e820b54a:

  PM / devfreq: exynos-ppmu: Update documentation to support PPMUv2 (2015-08-03 14:33:52 +0900)

- ----------------------------------------------------------------
Pull Request of Devfreq Tree to Rafael from MyungJoo

- - Device driver update to support additional hardare
- - Documentation error fix

(Continue reading)


Gmane