Viresh Kumar wrote:
On 24 July 2014 08:32, Saravana Kannan skan...@codeaurora.org wrote:
Ok, I think I've figured this out. But one question. Is it possible to
physically remove one CPU in a bunch of related cpus without also
unplugging the rest? Put another way, can you unplug one core from
Hi Stephen,
Yes, I have DT property qpnp-rtc-write set to 1 in my local kernel
sources. I have set it because I need write access to the clock.
I am aware that Android on Nexus 5 uses time_daemon utility to manage
time. I am trying to port Sailfish OS on Nexus 5 which uses a
different utility
On Wed, Jul 23, 2014 at 10:49:55AM -0700, Olav Haugan wrote:
Joerg, can you comment on what you envisioned when you suggested that we
add the fallback?
The problem is that we already have tons of IOMMU drivers in the tree
which don't provide these call-backs. So adding this API extension
On Wed, Jul 23, 2014 at 10:49:55AM -0700, Olav Haugan wrote:
On 7/22/2014 12:45 AM, Thierry Reding wrote:
On Mon, Jul 21, 2014 at 05:59:22PM -0700, Olav Haugan wrote:
On 7/17/2014 1:21 AM, Thierry Reding wrote:
On Wed, Jul 16, 2014 at 06:01:57PM -0700, Olav Haugan wrote:
[...]
On 18 July 2014 09:47, Viresh Kumar viresh.ku...@linaro.org wrote:
Before I apply anything in this area, I need a clear statement from the ARM
people as a group on what the approach is going to be.
@Rafael: The only patch which has blocked this set is:
cpufreq: cpu0: Extend support beyond CPU0
Hello all,
Changes since v2:
- 1/4 - added new line, signed-off-by / acked-by and module_authors.
- 3/4 - the subject has been changed.
The previous v2 can be found at [1].
I'm still waiting Acks for:
- 4/4 from Qualcomm folks.
- 2/4 and 3/4 from DT folks.
The patchset is ready to merge
From: Josh Cartwright jo...@codeaurora.org
The Qualcomm SPMI PMIC chips are components used with the
Snapdragon 800 series SoC family. This driver exists
largely as a glue mfd component, it exists to be an owner
of an SPMI regmap for children devices described in
device tree.
Signed-off-by:
The pm8921-core driver presently supports pm8921 and pm8058
Qualcomm PMICs. To avoid confusion with new generation PMICs
(like pm8941) rename the pm8921-core driver to more
appropriate name pm8xxx-ssbi, which reflects better that
those chips use SSBI interface.
Signed-off-by: Stanimir Varbanov
Document DT bindings used to describe the Qualcomm SPMI PMICs.
Currently the SPMI PMICs supported are pm8941, pm8841 and pma8084.
Signed-off-by: Stanimir Varbanov svarba...@mm-sol.com
---
.../devicetree/bindings/mfd/qcom,pm8xxx-spmi.txt | 49
1 files changed, 49
On Thu, Jul 24, 2014 at 1:47 AM, Stephen Boyd sb...@codeaurora.org wrote:
Please add these constants to the table of valid power-source values and use
something like I did to translate them to register values - it makes the DT
much more readable.
The DT could be similarly readable if we had
Since we no longer destroy/realloc policy during logical hotplug, most of
the policy save/restore code is dead code that doesn't get executed. Remove
those.
Signed-off-by: Saravana Kannan skan...@codeaurora.org
---
drivers/cpufreq/cpufreq.c | 82 +--
1
The ownership of the kobj doesn't need to match policy-cpu or change as
frequently. So, keep track of it separately.
Signed-off-by: Saravana Kannan skan...@codeaurora.org
---
drivers/cpufreq/cpufreq.c | 4 +++-
include/linux/cpufreq.h | 1 +
2 files changed, 4 insertions(+), 1 deletion(-)
There's no need to wait for the CPU going down to fully go offline to
restart the governor. We can stop the governor, change policy-cpus and
immediately restart the governor. This should reduce the time without any
CPUfreq monitoring and also help future patches with simplifying the code.
When CPUs are physically added/removed, its cpuX sysfs directory is
dynamically added/removed. To handle this correctly, the cpufreq sysfs
nodes also need to be added/removed dynamically.
Signed-off-by: Saravana Kannan skan...@codeaurora.org
---
drivers/cpufreq/cpufreq.c | 46
Series of patchs to simplify policy/sysfs/kobj/locking handling across
suspend/resume
The following have been tested so far on a 2x2 cluster environment:
- Boot with 2 cpus and no cpufreq driver.
- mod probe driver and see cpufreq sysfs files show up only for the 1st cluster.
- Online the rest of
This patch simplifies a lot of the hotplug/suspend code by not
adding/removing/moving the policy/sysfs/kobj during hotplug and just leaves
the cpufreq directory and policy in place irrespective of whether the CPUs
are ONLINE/OFFLINE.
Leaving the policy, sysfs and kobject in place also brings
On 23/07/14 23:58, Stephen Boyd wrote:
On 07/18/14 13:53, Srinivas Kandagatla wrote:
@@ -468,6 +473,11 @@ static void mmci_dma_setup(struct mmci_host *host)
if (max_seg_size host-mmc-max_seg_size)
host-mmc-max_seg_size = max_seg_size;
}
+
+
17 matches
Mail list logo
