There were few sparse warnings due to mismatch of type on function arguments.
Two types were used u64 and cputime64_t. Both are actually u64, so use u64 only.
Reported-by: Fengguang Wu
Signed-off-by: Viresh Kumar
---
This solution was discussed here:
http://www.mail-archive.com/linaro-dev@list
cpufreq_disabled() is a local function, so should be marked static.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index f552d5f..261ef65 100644
--- a/drivers/cpuf
On Tue, 2012-10-23 at 22:56 -0400, Nicolas Pitre wrote:
> I
> still recommend to read the following pages to get familiar with this
> beast:
>
> https://wiki.linaro.org/PawelMoll/BootingVEMadeEasy
> https://wiki.linaro.org/ARM/VersatileExpressSetup
>
> This page shows how to install U-Boot
在 2012-10-09二的 17:40 +0100，Morten Rasmussen写道：
> On Thu, Oct 04, 2012 at 07:27:00AM +0100, Viresh Kumar wrote:
> > On 22 September 2012 00:02, wrote:
> >
> > > +config SCHED_HMP_PRIO_FILTER
> > > + bool "(EXPERIMENTAL) Filter HMP migrations by task priority"
> > > + depends on SCHED_
On 24 October 2012 09:29, Jon Medhurst (Tixy) wrote:
> On Tue, 2012-10-23 at 22:56 -0400, Nicolas Pitre wrote:
>> I
>> still recommend to read the following pages to get familiar with this
>> beast:
>>
>> https://wiki.linaro.org/PawelMoll/BootingVEMadeEasy
>
>> https://wiki.linaro.org/ARM/Ver
From: "hongbo.zhang"
V1->V2 Changes:
DB8500 thermal dirver: Accept comments from Francesco Lavra and Viresh Kumar,
and split platform and driver parts into separate patches.
Thermal layer: Cancel the patch for deferring bind due to new patch for generic
cpu cooling layer to fix this issue.
CPU
From: "hongbo.zhang"
The curly bracket should be aligned with corresponding if else statements.
Signed-off-by: hongbo.zhang
Reviewed-by: Viresh Kumar
---
drivers/thermal/cpu_cooling.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/cpu_cooling.c b/drivers/t
From: "hongbo.zhang"
The cpufreq works as a cooling device, so the cooling layer should check if the
cpufreq driver is initialized or not.
Signed-off-by: hongbo.zhang
---
drivers/thermal/cpu_cooling.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/thermal/cpu_cooling.c b/drive
From: "hongbo.zhang"
Problem of using this list is that the cpufreq_get_max_state callback will be
called when register cooling device by thermal_cooling_device_register, but
this list isn't ready at this moment. What's more, there is no need to maintain
such a list, we can get cpufreq_cooling_de
From: "hongbo.zhang"
In the while loop for counting cpu frequencies, if table[i].frequency equals
CPUFREQ_ENTRY_INVALID, index i won't be increased, so this leads to an endless
loop, what's more the index i cannot be referred as cpu frequencies number if
there is CPUFREQ_ENTRY_INVALID case.
Sign
From: "hongbo.zhang"
This diver is based on the thermal management framework in thermal_sys.c. A
thermal zone device is created with the trip points to which cooling devices
can be bound, the current cooling device is cpufreq, e.g. CPU frequency is
clipped down to cool the CPU, and other cooling
From: "hongbo.zhang"
This patch adds device tree properties for ST-Ericsson DB8500 thermal driver,
also adds the platform data to support the old fashion.
Signed-off-by: hongbo.zhang
---
.../devicetree/bindings/thermal/db8500-thermal.txt | 40 ++
arch/arm/boot/dts/dbx5x0.dtsi
Hi All,
Due to a glitch with UEFI and the latest kernels, we are forced to leave the
TC2s offline until the issue is resolved. Ryan Harkin and I have been working
to try and resolve this, but the best we could do is to get them to pass their
health check (using sticking plaster, string and a la
On 24 October 2012 17:28, hongbo.zhang wrote:
> From: "hongbo.zhang"
>
> In the while loop for counting cpu frequencies, if table[i].frequency equals
> CPUFREQ_ENTRY_INVALID, index i won't be increased, so this leads to an endless
> loop, what's more the index i cannot be referred as cpu frequenc
Hi all!
An user reported problems cloning a tree from git.linaro.org today with
a /git-ro URL:
git clone http://git.linaro.org/git-ro/people/foo/bar.git
He was getting:
fatal: http://git.linaro.org/git-ro/people/foo/bar.git/info/refs not found:
did you run git update-server-info
On 24 October 2012 17:28, hongbo.zhang wrote:
> From: "hongbo.zhang"
>
> This diver is based on the thermal management framework in thermal_sys.c. A
> thermal zone device is created with the trip points to which cooling devices
> can be bound, the current cooling device is cpufreq, e.g. CPU frequ
On Wed, 2012-10-24 at 19:58 +0800, hongbo.zhang wrote:
> This patch adds device tree properties for ST-Ericsson DB8500 thermal driver,
> also adds the platform data to support the old fashion.
Just a trivial note:
> diff --git a/arch/arm/mach-ux500/board-mop500.c
> b/arch/arm/mach-ux500/board-mo
On 24 October 2012 17:28, hongbo.zhang wrote:
> From: "hongbo.zhang"
>
> This patch adds device tree properties for ST-Ericsson DB8500 thermal driver,
> also adds the platform data to support the old fashion.
>
> Signed-off-by: hongbo.zhang
> ---
> .../devicetree/bindings/thermal/db8500-thermal
Vincent,
Few comments/questions.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
This new flag SD SHARE_POWERLINE reflects the sharing of the power rail
between the members of a domain. As this is the current assumption of the
scheduler, the flag is added to all sched_domain
Signed-
Vincent,
Few comments/questions.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
During sched_domain creation, we define a pack buddy CPU if available.
On a system that share the powerline at all level, the buddy is set to -1
On a dual clusters / dual cores system which can powerga
$subject is bit confusing here.
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
The atomic update of runnable_avg_sum and runnable_avg_period are ensured
by their size and the toolchain. But we must ensure to not read an old value
for one field and a newly updated value for the other
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
Look for an idle CPU close the pack buddy CPU whenever possible.
s/close/close to
The goal is to prevent the wake up of a CPU which doesn't share the power
line of the pack CPU
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c
On Sunday 07 October 2012 01:13 PM, Vincent Guittot wrote:
The ARM platforms take advantage of packing small tasks on few cores.
This is true even when the cores of a cluster can't be powergated
independently.
Signed-off-by: Vincent Guittot
---
arch/arm/kernel/topology.c |5 +
1 file
Use the new __HVC macro in hypercall.S.
Signed-off-by: Stefano Stabellini
---
arch/arm/xen/hypercall.S | 14 +-
1 files changed, 5 insertions(+), 9 deletions(-)
diff --git a/arch/arm/xen/hypercall.S b/arch/arm/xen/hypercall.S
index 074f5ed..71f7239 100644
--- a/arch/arm/xen/hyper
On Wed, 24 Oct 2012, Viresh Kumar wrote:
> Nice article!
Thanks.
> On 24 October 2012 08:26, Nicolas Pitre wrote:
> >
> > When working on low level kernel code, the indication that something
> > went wrong is often noticed as a kernel oops, or even a totally silent
> > system. This usually imp
On Wed, 24 Oct 2012, Jon Medhurst (Tixy) wrote:
> The official release pages will include _some_ similar (and more up to
> date information), however you won't find any mention of any bootloader
> other than UEFI.
Another bootloader to hate. Joy!
> And, at least for now, no mention of how to bo
On Tue, 2012-10-23 at 22:56 -0400, Nicolas Pitre wrote:
> The script to generate a boot script to generate an ATAGS block is a
> rather nice hack.
These days are, fortunately, long gone :-) New-ish Boot Monitors (5.x.x
versions in particular) speak initrd, ATAG _and_ DTB "natively", so one
can b
On Tue, 2012-10-23 at 18:43 +0100, Steven Rostedt wrote:
> > <...>212.673126: hwmon_attr_update: hwmon4 temp1_input 34361
> >
> > One issue with this is that some external knowledge is required to
> > relate a number to a processor core. Or maybe it's not an issue at all
> > because it should be l
On Wed, 24 Oct 2012, Ryan Harkin wrote:
> On 24 October 2012 09:29, Jon Medhurst (Tixy) wrote:
>
> > Personally (and unofficially), I find that the simplest and most
> > reliable way to use vexpress is to flash the kernel/dtb/initrd images
> > into NOR flash and use the bootmonitor supplied with
On Tue, 2012-10-23 at 19:49 +0100, Andy Green wrote:
> A thought on that... from an SoC perspective there are other interesting
> power rails than go to just the CPU core. For example DDR power and
> rails involved with other IP units on the SoC such as 3D graphics unit.
> So tying one number
On Wed, 24 Oct 2012, Pawel Moll wrote:
> On Tue, 2012-10-23 at 22:56 -0400, Nicolas Pitre wrote:
> > The script to generate a boot script to generate an ATAGS block is a
> > rather nice hack.
>
> These days are, fortunately, long gone :-)
I deduced as much, given your example boot log reported
On Tue, 2012-10-23 at 23:02 +0100, Guenter Roeck wrote:
> > Traditionally such data should be exposed to the user via hwmon sysfs
> > interface, and that's exactly what I did for "my" platform - I have
> > a /sys/class/hwmon/hwmon*/device/energy*_input and this was good
> > enough to draw pretty gr
On Wed, 2012-10-24 at 01:40 +0100, Thomas Renninger wrote:
> > More and more of people are getting interested in the subject of power
> > (energy) consumption monitoring. We have some external tools like
> > "battery simulators", energy probes etc., but some targets can measure
> > their power usag
On Wednesday 24 of October 2012 11:37:13 Viresh Kumar wrote:
> On 22 October 2012 14:16, Viresh Kumar wrote:
> > On 20 October 2012 01:42, Viresh Kumar wrote:
> >> Initially ondemand governor was written and then using its code
> >> conservative
> >> governor is written. It used a lot of code fr
On Wednesday 24 of October 2012 21:43:46 Rafael J. Wysocki wrote:
> On Wednesday 24 of October 2012 11:37:13 Viresh Kumar wrote:
> > On 22 October 2012 14:16, Viresh Kumar wrote:
> > > On 20 October 2012 01:42, Viresh Kumar wrote:
> > >> Initially ondemand governor was written and then using its
On Wednesday 24 of October 2012 13:15:58 Viresh Kumar wrote:
> There were few sparse warnings due to mismatch of type on function arguments.
> Two types were used u64 and cputime64_t. Both are actually u64, so use u64
> only.
>
> Reported-by: Fengguang Wu
> Signed-off-by: Viresh Kumar
This ser
On Wed, Oct 24, 2012 at 05:37:27PM +0100, Pawel Moll wrote:
> On Tue, 2012-10-23 at 23:02 +0100, Guenter Roeck wrote:
> > > Traditionally such data should be exposed to the user via hwmon sysfs
> > > interface, and that's exactly what I did for "my" platform - I have
> > > a /sys/class/hwmon/hwmon*
On Wednesday 17 of October 2012 12:03:31 Viresh Kumar wrote:
> On 17 October 2012 11:56, Joe Perches wrote:
> > Oh good, but please use a space between KBUILD_MODNAME
> > and the quoted ": ".
>
> Anything technical behind it or just for code formatting? As output is
> same in both cases :)
>
> -
On Saturday 20 of October 2012 10:12:07 Viresh Kumar wrote:
> On Oct 20, 2012 3:37 AM, "Rafael J. Wysocki" wrote:
> >
> > On Saturday 20 of October 2012 01:42:05 Viresh Kumar wrote:
> > > There is no need to do cpufreq_get_cpu() and cpufreq_put_cpu() for
> drivers that
> > > don't support getavg()
On 25 October 2012 02:44, Rafael J. Wysocki wrote:
> On Wednesday 24 of October 2012 13:15:58 Viresh Kumar wrote:
>> There were few sparse warnings due to mismatch of type on function arguments.
>> Two types were used u64 and cputime64_t. Both are actually u64, so use u64
>> only.
>>
>> Reported-
On 24 October 2012 22:32, Joe Perches wrote:
> On Wed, 2012-10-24 at 19:58 +0800, hongbo.zhang wrote:
>> This patch adds device tree properties for ST-Ericsson DB8500 thermal driver,
>> also adds the platform data to support the old fashion.
>
> Just a trivial note:
>
>> diff --git a/arch/arm/mach
[...]
>> /*
>> + * Thermal Sensor
>> + */
>> +
>> +static struct resource db8500_thsens_resources[] = {
>> + {
>> + .name = "IRQ_HOTMON_LOW",
>> + .start = IRQ_PRCMU_HOTMON_LOW,
>> + .end= IRQ_PRCMU_HOTMON_LOW,
>> + .flags = IORES
From: "Rajanikanth H.V"
This patch adds device tree support for charging algorithm
driver
Signed-off-by: Rajanikanth H.V
---
.../bindings/power_supply/ab8500/chargalg.txt | 16 ++
arch/arm/boot/dts/dbx5x0.dtsi |5 ++
drivers/mfd/ab8500-core.c
From: "Rajanikanth H.V"
This patch adds device tree support for ab8500-charger
driver
Signed-off-by: Rajanikanth H.V
---
Documentation/devicetree/bindings/mfd/ab8500.txt | 14
.../bindings/power_supply/ab8500/charger.txt | 25 +++
arch/arm/boot/dts/dbx5x0.dtsi
From: "Rajanikanth H.V"
This patch-set adds device tree binding for ab8500 battery-managed
devices. Removes the redundant platform structure maintained
across bm devices and implements common DT probe routine across all the
modules.
Test status:
a) Tested across 'legacy platform data' and DT bin
From: "Rajanikanth H.V"
This patch adds device tree support for
battery-temperature-monitor driver
Signed-off-by: Rajanikanth H.V
---
Documentation/devicetree/bindings/mfd/ab8500.txt |6 ++
.../bindings/power_supply/ab8500/btemp.txt | 16 +
arch/arm/boot/dts/dbx5x0.dtsi
From: "Rajanikanth H.V"
- This patch adds device tree support for fuelgauge driver
- optimize bm devices platform_data usage and of_probe(...)
Note: of_probe() routine for battery managed devices is made
common across all bm drivers.
- test status:
- interrupt numbers assigned differs betwe
Hi Rafael,
__cpufreq_driver_target() must not pass target frequency beyond the limits of
current policy.
Today most of cpufreq platform drivers are doing this check in their target
routines. Why not move it to __cpufreq_driver_target().
I wanted to get your opinion on this before making changes
48 matches
Mail list logo
