Fix it by setting 'name' string to
> > proper value for !prop cases.
> >
> > Cc: Viresh Kumar <viresh.ku...@linaro.org>
> > Cc: Lee Jones <lee.jo...@linaro.org>
> > Cc: Rafael J. Wysocki <rafael.j.wyso...@intel.com>
> > Fixes: 01fb4d3c39d3 ("
On Sunday, December 13, 2015 06:57:09 PM Paul Gortmaker wrote:
> This series of commits is a part of a larger project to ensure
> people don't reference modular support functions in non-modular
> code. Overall there was roughly 5k lines of dead code in the
> kernel due to this. So far we've
On Wednesday, November 11, 2015 08:10:58 AM Viresh Kumar wrote:
> OPP bindings got updated to name OPP nodes this way, make changes
> according to that.
>
> Reviewed-by: Krzysztof Kozlowski
> Signed-off-by: Viresh Kumar
> ---
>
On Tuesday, November 24, 2015 12:04:00 AM Rafael J. Wysocki wrote:
> On Wednesday, November 11, 2015 08:10:58 AM Viresh Kumar wrote:
> > OPP bindings got updated to name OPP nodes this way, make changes
> > according to that.
> >
> > Reviewed-by: Krzysztof Kozlows
On Monday, November 16, 2015 10:26:43 PM Arnd Bergmann wrote:
> s3c2410_plls_add is a device notifier that may be called at runtime and
> is correctly not marked __init. However it calls s3c_plltab_register()
> which is marked __init, and that triggers a build error when we are
> checking for
10",
> -#ifdef CONFIG_PM
> .suspend= cpufreq_generic_suspend,
> .resume = cpufreq_generic_suspend, /* We need to set SLEEP FREQ
> again */
> -#endif
> };
>
> static struct notifier_block s5pv210_cpufreq_reboot_notifier = {
>
--
I speak only
On Tuesday, September 08, 2015 06:41:00 PM Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> This patch series adds suspend frequency support (using opp-v2
> bindings and suspend-opp functionality) to cpufreq-dt driver and
> then adds suspend opp for Exynos4412 based boards.
>
> This patch series fixes
On Saturday, August 08, 2015 04:36:34 PM Krzysztof Kozlowski wrote:
W dniu 06.08.2015 o 09:23, Rafael J. Wysocki pisze:
On Tuesday, August 04, 2015 04:45:16 PM Kukjin Kim wrote:
From: Shailendra Verma shailendra.capric...@gmail.com
During probe free the memory allocated to exynos_info
On Friday, August 07, 2015 05:26:27 PM Viresh Kumar wrote:
On 07-08-15, 13:47, Bartlomiej Zolnierkiewicz wrote:
Hmm, wait. Patch 6/6 depends on earlier changes. I cannot remove
the config option in question now as it is currently used by
exynos-cpufreq specific boost support. Patch 1/6
On Friday, August 07, 2015 05:07:39 PM Viresh Kumar wrote:
On 07-08-15, 13:12, Bartlomiej Zolnierkiewicz wrote:
From 993ebb6fc632ec7b61654c9610c90ff4dca4be34 Mon Sep 17 00:00:00 2001
From: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
Date: Fri, 7 Aug 2015 13:07:51 +0200
Subject:
On Tuesday, August 04, 2015 04:45:16 PM Kukjin Kim wrote:
From: Shailendra Verma shailendra.capric...@gmail.com
During probe free the memory allocated to exynos_info in case of
unknown SoC type.
Signed-off-by: Shailendra Verma shailendra.capric...@gmail.com
Acked-by: Viresh Kumar
On Saturday, August 01, 2015 04:45:37 PM Viresh Kumar wrote:
On 31-07-15, 20:49, Bartlomiej Zolnierkiewicz wrote:
Remove no longer needed CPU_FREQ_BOOST_SW config option.
As a result scaling_boost_freqs sysfs attribute is available
when cpufreq-dt driver is used and boost support is
@@
*/
#include linux/kernel.h
+#include linux/module.h
#include linux/err.h
#include linux/clk.h
#include linux/io.h
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body
.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wednesday, February 18, 2015 09:54:01 PM Arnd Bergmann wrote:
This is an unmodified re-send of two patches I originally submitted
on January 28. Both patches were Acked by Viresh, while a third patch
got replaced with a better fix. Please merge these through the cpufreq
tree for 3.20 and
On Thursday, February 19, 2015 06:33:14 AM Rafael J. Wysocki wrote:
On Wednesday, February 18, 2015 09:54:01 PM Arnd Bergmann wrote:
This is an unmodified re-send of two patches I originally submitted
on January 28. Both patches were Acked by Viresh, while a third patch
got replaced
-attach_dev() callback
drivers/base/power/domain.c | 137
+---
include/linux/pm_domain.h | 2 -
2 files changed, 65 insertions(+), 74 deletions(-)
Whole series queued up for 3.20, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source
only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Friday, December 19, 2014 09:13:29 AM Geert Uytterhoeven wrote:
On Fri, Dec 19, 2014 at 3:03 AM, Rafael J. Wysocki r...@rjwysocki.net wrote:
--- linux-pm.orig/arch/mips/configs/lemote2f_defconfig
+++ linux-pm/arch/mips/configs/lemote2f_defconfig
@@ -37,7 +37,7 @@ CONFIG_MIPS32_N32=y
On Friday, December 19, 2014 01:49:34 PM Kevin Hilman wrote:
Rafael J. Wysocki r...@rjwysocki.net writes:
[...]
Fixed up patch is appended, thanks!
---
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Subject: PM: Eliminate CONFIG_PM_RUNTIME
Having switched over all
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Having switched over all of the users of CONFIG_PM_RUNTIME to use
CONFIG_PM directly, turn the latter into a user-selectable option
and drop the former entirely from the tree.
Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
---
arch
On Thursday, December 18, 2014 11:05:18 AM Sylwester Nawrocki wrote:
On 18/12/14 01:58, Rafael J. Wysocki wrote:
What's needed to solve this problem is a generalized way to have runtime
PM dependencies between devices. Runtime PM already automatically
handles parent devices as one type
by default? Second, if we do that, how do we
figure out the initial value of runtime PM status in general? Finally,
what about drivers that need to work with and without PM domains (for example,
some systems they run on have PM domains, while some other don't)?
--
I speak only for myself.
Rafael J
proposed approach, but work for
any devices in any PM domains.
Plus, it is not limited to runtime PM, really. It affects system suspend
too.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung
Hansson (3):
PM / Domains: Initial PM clock support for genpd
ARM: shmobile: Convert to genpd flags for PM clocks for r8a7779
ARM: shmobile: Convert to genpd flags for PM clocks for R-mobile
All queued up for 3.19-rc1, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source
On Thursday, December 04, 2014 04:08:40 PM Mauro Carvalho Chehab wrote:
Em Wed, 03 Dec 2014 03:13:55 +0100
Rafael J. Wysocki r...@rjwysocki.net escreveu:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
selected
...@vger.kernel.org
+L: linux-samsung-soc@vger.kernel.org
+S: Supported
+F: drivers/cpuidle/cpuidle-exynos.c
+F: arch/arm/mach-exynos/pm.c
+
CPUIDLE DRIVERS
M: Rafael J. Wysocki r...@rjwysocki.net
M: Daniel Lezcano daniel.lezc...@linaro.org
--
To unsubscribe from this list: send the line
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
CONFIG_PM is defined as the alternative of CONFIG_PM_RUNTIME and
CONFIG_PM_SLEEP, so it can be used instead of that.
Besides, after commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if
PM_SLEEP is selected) PM_RUNTIME is always set if PM is set
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
selected) PM_RUNTIME is always set if PM is set, so #ifdef blocks
depending on CONFIG_PM_RUNTIME may now be changed to depend on
CONFIG_PM.
Replace CONFIG_PM_RUNTIME
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
After commit b2b49ccbdd54 (PM: Kconfig: Set PM_RUNTIME if PM_SLEEP is
selected) PM_RUNTIME is always set if PM is set, so #ifdef blocks
depending on CONFIG_PM_RUNTIME may now be changed to depend on
CONFIG_PM.
The alternative of CONFIG_PM_SLEEP
(struct dev_pm_domain *pd)
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
,
struct device *dev,
struct gpd_timing_data *td);
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord
__pm_genpd_add_device(struct generic_pm_domain *genpd,
struct device *dev,
struct gpd_timing_data *td);
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line
) /* PM domain uses PM clk */
};
static inline struct generic_pm_domain *pd_to_genpd(struct dev_pm_domain *pd)
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body
On Thursday, November 20, 2014 11:13:01 AM Ulf Hansson wrote:
On 20 November 2014 01:35, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Wednesday, November 19, 2014 09:54:00 AM Ulf Hansson wrote:
[...]
Scenario 5), a platform driver with/without runtime PM callbacks.
-probe
On Wednesday, November 19, 2014 09:54:00 AM Ulf Hansson wrote:
[...]
Scenario 5), a platform driver with/without runtime PM callbacks.
-probe()
- do some initialization
- may fetch handles to runtime PM resources
- pm_runtime_enable()
Well, and now how the driver knows if the
On Tuesday, November 18, 2014 09:55:15 AM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 12:44:22PM -0500, Alan Stern wrote:
On Tue, 18 Nov 2014, Dmitry Torokhov wrote:
OK. Another question then: pm_runtime_get_noresume() does literally this:
atomic_inc(dev-power.usage_count);
On Tuesday, November 18, 2014 03:05:08 PM Ulf Hansson wrote:
[...]
It would not be the same for all buses. Each bus will have its
own way
of recognizing whether or not a driver has been probed (i.e., by
checking some field in the bus-specific part of the device
On Tuesday, November 18, 2014 12:04:38 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 09:14:56PM +0100, Rafael J. Wysocki wrote:
On Tuesday, November 18, 2014 09:55:15 AM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 12:44:22PM -0500, Alan Stern wrote:
On Tue, 18 Nov 2014, Dmitry
On Tuesday, November 18, 2014 10:03:18 PM Rafael J. Wysocki wrote:
On Tuesday, November 18, 2014 12:04:38 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 09:14:56PM +0100, Rafael J. Wysocki wrote:
On Tuesday, November 18, 2014 09:55:15 AM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014
On Tuesday, November 18, 2014 01:02:29 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 10:17:46PM +0100, Rafael J. Wysocki wrote:
On Tuesday, November 18, 2014 10:03:18 PM Rafael J. Wysocki wrote:
On Tuesday, November 18, 2014 12:04:38 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014
On Tuesday, November 18, 2014 10:58:17 PM Rafael J. Wysocki wrote:
On Tuesday, November 18, 2014 01:02:29 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 10:17:46PM +0100, Rafael J. Wysocki wrote:
On Tuesday, November 18, 2014 10:03:18 PM Rafael J. Wysocki wrote:
On Tuesday, November
On Monday, November 17, 2014 02:17:00 PM Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 05:12:35PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry Torokhov wrote:
Except buses
usually call pm_generic_runtime_resume() which ends up fetching
driver's
callbacks. Maybe
On Monday, November 17, 2014 03:26:04 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 12:28:26AM +0100, Rafael J. Wysocki wrote:
On Monday, November 17, 2014 02:17:00 PM Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 05:12:35PM -0500, Alan Stern wrote:
On Mon, 17 Nov 2014, Dmitry
On Tuesday, November 18, 2014 01:26:38 AM Rafael J. Wysocki wrote:
On Monday, November 17, 2014 03:26:04 PM Dmitry Torokhov wrote:
On Tue, Nov 18, 2014 at 12:28:26AM +0100, Rafael J. Wysocki wrote:
On Monday, November 17, 2014 02:17:00 PM Dmitry Torokhov wrote:
On Mon, Nov 17, 2014 at 05
On Wednesday, November 05, 2014 03:11:23 PM Kevin Hilman wrote:
Rafael J. Wysocki r...@rjwysocki.net writes:
On Wednesday, November 05, 2014 02:43:31 PM Kevin Hilman wrote:
Dmitry Torokhov dmitry.torok...@gmail.com writes:
On Thu, Oct 30, 2014 at 01:38:30PM -0700, Kevin Hilman wrote
notifier_block nb;
struct mutex lock;
unsigned int refcount;
- bool need_restore;
+ int need_restore;
};
#ifdef CONFIG_PM_GENERIC_DOMAINS
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line
RPM core.
That I can't parse really, sorry.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wednesday, November 05, 2014 02:43:31 PM Kevin Hilman wrote:
Dmitry Torokhov dmitry.torok...@gmail.com writes:
On Thu, Oct 30, 2014 at 01:38:30PM -0700, Kevin Hilman wrote:
Rafael J. Wysocki r...@rjwysocki.net writes:
On Thursday, October 30, 2014 01:02:49 PM Ulf Hansson wrote
On Wednesday, November 05, 2014 03:11:23 PM Kevin Hilman wrote:
Rafael J. Wysocki r...@rjwysocki.net writes:
On Wednesday, November 05, 2014 02:43:31 PM Kevin Hilman wrote:
Dmitry Torokhov dmitry.torok...@gmail.com writes:
On Thu, Oct 30, 2014 at 01:38:30PM -0700, Kevin Hilman wrote
On Tuesday, November 04, 2014 09:20:44 AM Geert Uytterhoeven wrote:
On Tue, Nov 4, 2014 at 2:43 AM, Rafael J. Wysocki r...@rjwysocki.net wrote:
That is quite simple to address, though. You can register a bus type
notifier that will power up the domain on BUS_NOTIFY_ADD_DEVICE events
(where
and unset, so -probe() can always make the
device is accessible assumption.
- Bus types may need to do more on top of that in their -probe(), so the
driver's -probe() can make that assumption too in all cases.
Does that make sense to you?
--
I speak only for myself.
Rafael J. Wysocki, Intel
On Tuesday, November 04, 2014 01:05:21 AM Dmitry Torokhov wrote:
On Tue, Nov 04, 2014 at 09:54:19AM +0100, Ulf Hansson wrote:
[...]
Generally, there are two or even three levels of runtime PM handling,
driver, (possibly) bus type and (possibly) PM domain (and multiple levels
of
On Tuesday, November 04, 2014 10:24:35 AM Ulf Hansson wrote:
On 4 November 2014 10:05, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
On Tue, Nov 04, 2014 at 09:54:19AM +0100, Ulf Hansson wrote:
[...]
Generally, there are two or even three levels of runtime PM handling,
driver,
On Tuesday, November 04, 2014 10:29:20 AM Dmitry Torokhov wrote:
On Tue, Nov 04, 2014 at 06:01:44PM +0100, Ulf Hansson wrote:
Devices that are created while discoverable buses are being probed
can't be attached to a PM domain before the probing is done, because
those simply doesn't
filters out the unregistered pd's requesting notification.
Cc: Rafael J. Wysocki rafael.j.wyso...@intel.com
Reviewed-by: Pankaj Dubey pankaj.du...@samsung.com
Signed-off-by: Amit Daniel Kachhap amit.dan...@samsung.com
---
drivers/base/power/domain.c | 112
On Monday, November 03, 2014 09:00:29 AM Kevin Hilman wrote:
Rafael J. Wysocki r...@rjwysocki.net writes:
On Saturday, November 01, 2014 02:08:57 AM Rafael J. Wysocki wrote:
On Saturday, November 01, 2014 01:20:38 AM Rafael J. Wysocki wrote:
On Friday, October 31, 2014 10:16:14 AM Ulf
On Monday, November 03, 2014 03:03:46 PM Ulf Hansson wrote:
On 1 November 2014 01:20, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote:
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
Ulf Hansson ulf.hans...@linaro.org
On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote:
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
Changes in v3:
-Rework the entire intermediate step which was suggested in v2.
That means solving the race
On Friday, October 31, 2014 10:23:00 AM Ulf Hansson wrote:
On 31 October 2014 01:07, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
On Thu, Oct 30, 2014 at 01:47:27PM -0700, Kevin Hilman wrote:
Ulf Hansson ulf.hans...@linaro.org writes:
To sucessfully probe some devices their
On Saturday, November 01, 2014 01:20:38 AM Rafael J. Wysocki wrote:
On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote:
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
[cut]
1)
It's bad practice to use pm_runtime_get_sync() in the -probe() path,
Honestly, I'm
On Saturday, November 01, 2014 02:08:57 AM Rafael J. Wysocki wrote:
On Saturday, November 01, 2014 01:20:38 AM Rafael J. Wysocki wrote:
On Friday, October 31, 2014 10:16:14 AM Ulf Hansson wrote:
On 24 October 2014 18:12, Kevin Hilman khil...@kernel.org wrote:
[cut]
1)
It's bad
callbacks.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
are not used and not needed. While we're trying to decrease the
power consumption in any possible way this doesn't help at all.
Agreed (as stated before).
And I'm wondering why that comment of mine was ignored?
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center
...@linaro.org
My understanding is that this is for the whole series.
Which I'm queuing up for 3.18, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message
hurt either I suppose?
Anyway, Ulf, are you going to update this patch?
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More
int s5pv210_cpu_init(struct cpufreq_policy *policy)
{
unsigned long mem_type;
int ret;
Acked-by: Viresh Kumar viresh.ku...@linaro.org
Queued up for 3.17-rc3, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from
of this script.
how it does that.
Is this information required in the commit message or can it stay in
the README file created in the same commit?
There should be *some* information in the changelog too.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center
.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
SWITCHING
+echo ##
+test_freqs2 $T_PATCH/scaling_available_frequencies
+
+echo ##
+echo ERRORS: $ERRORS
+echo ##
+
+restore
+exit 0
--
I speak only for myself.
Rafael J. Wysocki
On Monday, June 09, 2014 08:49:17 PM Mark Brown wrote:
On Fri, Jun 06, 2014 at 11:15:06PM +0200, Rafael J. Wysocki wrote:
On Friday, June 06, 2014 02:08:50 PM Mark Brown wrote:
Yes, the conversion to make ARCH_HAS_OPP unused is in Raphael's tree for
the merge window.
Perhaps already
On Monday, June 09, 2014 11:51:42 PM Mark Brown wrote:
--fYgRtaZIy+F1uhp1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Jun 10, 2014 at 12:22:07AM +0200, Rafael J. Wysocki wrote:
On Monday, June 09, 2014 08:49:17 PM Mark Brown wrote:
Yes, looks like
On Friday, June 06, 2014 02:08:50 PM Mark Brown wrote:
--cU9XODsizZBnwgll
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Jun 06, 2014 at 09:50:06PM +0900, Simon Horman wrote:
On Fri, Jun 06, 2014 at 09:14:01PM +0900, Magnus Damm wrote:
I'm not sure
only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Friday, May 30, 2014 02:19:06 PM Rafael J. Wysocki wrote:
On Friday, May 30, 2014 02:31:15 PM Thomas Abraham wrote:
Changes since v5:
- Fixes for checkpatch warnings with --strict option as suggested by
Nishanth Menon.
Changes since v4:
- Code improvements suggested by Viresh
On Friday, May 30, 2014 11:37:58 PM Thomas Abraham wrote:
On Fri, May 30, 2014 at 8:17 PM, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Friday, May 30, 2014 02:19:06 PM Rafael J. Wysocki wrote:
On Friday, May 30, 2014 02:31:15 PM Thomas Abraham wrote:
Changes since v5:
- Fixes
On Saturday, May 17, 2014 01:04:29 AM Rafael J. Wysocki wrote:
On Friday, May 16, 2014 07:54:01 PM Kukjin Kim wrote:
Jonghwan Choi wrote:
Commit 7da83a80 (ARM: EXYNOS: Migrate Exynos specific macros from plat to
mach) which lands in samsung tree causes build breakage
for cpufreq
breakage with enabling exynos
cpufreq?
Please go ahead.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
(-)
I'm assuming that the Exynos maintainers will take care of this, correct?
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More
On Thursday, January 16, 2014 10:40:08 AM Lukasz Majewski wrote:
Hi Rafael,
On Wed, 2014-01-08 at 01:35 +0100, Rafael J. Wysocki wrote:
On Tuesday, January 07, 2014 07:58:24 AM Lukasz Majewski wrote:
Hi Rafael,
Hi,
This patch series introduces support for CPU
On Saturday, January 11, 2014 01:37:29 AM Rafael J. Wysocki wrote:
On Friday, December 20, 2013 07:47:22 PM Bartlomiej Zolnierkiewicz wrote:
Hi,
Some cpuidle drivers assume that cpuidle core will handle cases where
device-state_count is smaller than driver-state_count, unfortunately
On Tuesday, January 07, 2014 07:58:24 AM Lukasz Majewski wrote:
Hi Rafael,
Hi,
This patch series introduces support for CPU overclocking technique
called Boost.
It is a follow up of a LAB governor proposal. Boost is a LAB
component:
+-
drivers/idle/intel_idle.c | 140
+---
include/linux/cpuidle.h | 1 -
7 files changed, 51 insertions(+), 194 deletions(-)
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center
On Sunday, December 08, 2013 01:41:08 PM Borislav Petkov wrote:
On Sun, Dec 08, 2013 at 01:34:36AM +0100, Rafael J. Wysocki wrote:
On Saturday, December 07, 2013 04:24:09 PM Paul Bolle wrote:
On Sat, 2013-12-07 at 12:01 +0100, Bjørn Mork wrote:
Sorry to be making noise here again, but I
On Saturday, December 07, 2013 04:24:09 PM Paul Bolle wrote:
On Sat, 2013-12-07 at 12:01 +0100, Bjørn Mork wrote:
Sorry to be making noise here again, but I was eager to verify that the
fixes in v3.13-rc3 were OK on my system. Unfortunately it seems this
patch completely broke suspend for
*
*/
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
On Thursday, November 28, 2013 07:49:29 PM Viresh Kumar wrote:
On 28 November 2013 19:53, Rafael J. Wysocki r...@rjwysocki.net wrote:
I don't think that the Nishanth's issue is fixed by this particular version
of
the patch, so I modified the changelog and removed a the comment above
On Tuesday, November 26, 2013 07:56:19 AM Viresh Kumar wrote:
On 26 November 2013 04:59, Rafael J. Wysocki r...@rjwysocki.net wrote:
@@ -1259,6 +1262,8 @@ int dpm_suspend(pm_message_t state)
might_sleep();
+ cpufreq_suspend();
+
mutex_lock(dpm_list_mtx
On Tuesday, November 26, 2013 09:23:15 PM Rafael J. Wysocki wrote:
On Tuesday, November 26, 2013 07:56:19 AM Viresh Kumar wrote:
On 26 November 2013 04:59, Rafael J. Wysocki r...@rjwysocki.net wrote:
@@ -1259,6 +1262,8 @@ int dpm_suspend(pm_message_t state)
might_sleep
);
+void cpufreq_suspend(void);
+void cpufreq_resume(void);
+
const char *cpufreq_get_current_driver(void);
static inline void cpufreq_verify_within_limits(struct cpufreq_policy
*policy,
Thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center
register device failed\n);
+ dev_err(pdev-dev, failed to register cpuidle
device\n);
return ret;
}
}
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line
...@samsung.com
Cc: Amit Daniel Kachhap amit.dan...@samsung.com
---
Acked-by: Daniel Lezcano daniel.lezc...@linaro.org
Queued up for 3.13, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux
On Tuesday, August 27, 2013 02:26:41 PM Eduardo Valentin wrote:
On 23-08-2013 19:08, Rafael J. Wysocki wrote:
On Friday, August 23, 2013 06:03:14 PM Eduardo Valentin wrote:
When registering a new thermal_device, the thermal framework
will always add a hwmon sysfs interface.
This patch
, bool);
void thermal_zone_device_unregister(struct thermal_zone_device *);
int thermal_zone_bind_cooling_device(struct thermal_zone_device *, int,
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe
On Wednesday, August 07, 2013 05:03:59 PM Viresh Kumar wrote:
On 7 August 2013 17:00, Sudeep KarkadaNagesha
sudeep.karkadanage...@arm.com wrote:
Any particular reason we need this check in all drivers after your
commit: 5a1c0228 cpufreq: Avoid calling cpufreq driver's target()
routine if
On Tuesday, May 14, 2013 09:36:42 PM Kukjin Kim wrote:
Viresh Kumar wrote:
On 13 May 2013 16:21, Rafael J. Wysocki r...@sisk.pl wrote:
That doesn't matter I suppose. I can take it, but please rebase it on
top
of current linux-next.
I have already done that (attached). But i
On Monday, May 13, 2013 11:35:22 AM Viresh Kumar wrote:
On 23 April 2013 20:55, Kukjin Kim kgene@samsung.com wrote:
On 04/05/13 20:36, Rafael J. Wysocki wrote:
On Friday, April 05, 2013 12:36:34 PM Viresh Kumar wrote:
On 5 April 2013 12:18, Kukjin Kimkgene@samsung.com wrote
On Friday, April 26, 2013 01:48:19 AM Kukjin Kim wrote:
On 04/24/13 07:59, Rafael J. Wysocki wrote:
[...]
Rafael, please take this patch with my ack in your tree, sorry for noise.
Acked-by: Kukjin Kimkgene@samsung.com
If any problems, please kindly let me know.
Well, I
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-samsung-soc in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
1 - 100 of 159 matches
Mail list logo