show_bios_limit is mistakenly written as show_scaling_driver in a comment
describing purpose of show_bios_limit() routine.
Fix it.
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/cp
Following is the declaration of name field in struct cpufreq_driver:
char name[CPUFREQ_NAME_LEN];
where CPUFREQ_NAME_LEN is 16.
So, length of drivers name must be <=15 (one position for '\0').
Current name is crossing this limit and so name doesn't get printed properly
when we do:
$ cat /sys/dev
On 09/10/12 08:10, Viresh Kumar wrote:
Following is the declaration of name field in struct cpufreq_driver:
char name[CPUFREQ_NAME_LEN];
where CPUFREQ_NAME_LEN is 16.
So, length of drivers name must be <=15 (one position for '\0').
Current name is crossing this limit and so name doesn't get pri
On Tue, 2012-10-09 at 09:27 +0100, Sudeep KarkadaNagesha wrote:
> On 09/10/12 08:10, Viresh Kumar wrote:
> > Following is the declaration of name field in struct cpufreq_driver:
> > char name[CPUFREQ_NAME_LEN];
> >
> > where CPUFREQ_NAME_LEN is 16.
> >
> > So, length of drivers name must be <=15 (o
On Tue, Oct 9, 2012 at 2:13 PM, Jon Medhurst (Tixy) wrote:
> On Tue, 2012-10-09 at 09:27 +0100, Sudeep KarkadaNagesha wrote:
>> On 09/10/12 08:10, Viresh Kumar wrote:
>> > Following is the declaration of name field in struct cpufreq_driver:
>> > char name[CPUFREQ_NAME_LEN];
>> >
>> > where CPUFREQ
On 09/10/12 11:33, Amit Kucheria wrote:
On Tue, Oct 9, 2012 at 2:13 PM, Jon Medhurst (Tixy) wrote:
On Tue, 2012-10-09 at 09:27 +0100, Sudeep KarkadaNagesha wrote:
On 09/10/12 08:10, Viresh Kumar wrote:
Following is the declaration of name field in struct cpufreq_driver:
char name[CPUFREQ_NAME
On Tue, 2012-10-09 at 11:42 +0100, Sudeep KarkadaNagesha wrote:
> Robin raised a valid point that this driver is TC2 specific and bL is
> not appropriate name for it including the file name(my bad choice at first).
Just to be painfully precise ;-) I must say it's not TC2 specific, but
V2P-CA15_A7
On 9 October 2012 16:24, Pawel Moll wrote:
> On Tue, 2012-10-09 at 11:42 +0100, Sudeep KarkadaNagesha wrote:
>> Robin raised a valid point that this driver is TC2 specific and bL is
>> not appropriate name for it including the file name(my bad choice at first).
>
> Just to be painfully precise ;-)
On Tue, 2012-10-09 at 12:34 +0100, Viresh Kumar wrote:
> On 9 October 2012 16:24, Pawel Moll wrote:
> > On Tue, 2012-10-09 at 11:42 +0100, Sudeep KarkadaNagesha wrote:
> >> Robin raised a valid point that this driver is TC2 specific and bL is
> >> not appropriate name for it including the file nam
On 8 October 2012 14:59, Jon Medhurst (Tixy) wrote:
> This mostly boils down to initialising the Cache Coherent Interconnect
> (CCI). We do this by looking in the device-tree for a CCI node, that way
> the same semihosting bootwrapper binary can be used on both the
> big.LITTLE models and on the A
On Mon, Oct 08, 2012 at 02:59:18PM +0100, Jon Medhurst (Tixy) wrote:
> From: Jon Medhurst
>
> A subsequent patch will also need to obtain address-cells and
> size-cells, so lets factor out this code into a handy function.
The code looks ok. There are a couple of stylistic things that could be
t
On Mon, Oct 08, 2012 at 02:59:19PM +0100, Jon Medhurst (Tixy) wrote:
> From: Jon Medhurst
>
> The A15xA7 models simulate a Cache Coherent Interconnect (CCI) and this
> needs to be initialised correctly for Linux to boot.
>
> To perform this initiation we add the new function configure_from_fdt()
On Mon, Oct 08, 2012 at 02:59:17PM +0100, Jon Medhurst (Tixy) wrote:
> From: Jon Medhurst
>
> Check all the CPU affinity fields of MPIDR, so we select only
> the first CPU of the first cluster as the one to boot on.
Shame, we can't run this on pre-v7 CPUs now ;)
(Well, v6T2).
The chance of us w
On Tue, Oct 09, 2012 at 01:31:55PM +0100, Peter Maydell wrote:
> On 8 October 2012 14:59, Jon Medhurst (Tixy) wrote:
> > This mostly boils down to initialising the Cache Coherent Interconnect
> > (CCI). We do this by looking in the device-tree for a CCI node, that way
> > the same semihosting boot
On 9 October 2012 14:06, Dave Martin wrote:
> On Tue, Oct 09, 2012 at 01:31:55PM +0100, Peter Maydell wrote:
>> Patch 2 made git complain about trailing whitespace in one place
>> but I'll just zap that in passing when I apply these.
>
> Thanks
>
>> Dave, unless you have any further review comment
On Tue, 2012-10-09 at 11:42 +0100, Sudeep KarkadaNagesha wrote:
> On 09/10/12 11:33, Amit Kucheria wrote:
> > On Tue, Oct 9, 2012 at 2:13 PM, Jon Medhurst (Tixy) wrote:
> >> On Tue, 2012-10-09 at 09:27 +0100, Sudeep KarkadaNagesha wrote:
> >>> On 09/10/12 08:10, Viresh Kumar wrote:
> Followin
Hi Viresh,
On Thu, Oct 04, 2012 at 07:02:03AM +0100, Viresh Kumar wrote:
> Hi Morten,
>
> On 22 September 2012 00:02, wrote:
> > From: Morten Rasmussen
> >
> > This patch introduces the basic SCHED_HMP infrastructure. Each class of
> > cpus is represented by a hmp_domain and tasks will only be
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_HMP
>
> Should it depend on EXPERIMENTAL?
>
> > + h
On 9 October 2012 21:02, Jon Medhurst (Tixy) wrote:
> Considering the confusion over what the correct naming should be, I
> don't think it's worth me apply the renaming patch at the moment ;-)
This thread went into another direction, than the one it was intended for :)
Looks correct, would be be
(12:25:28 PM) hongbo_: amitk: good afternoon. need I push u8500 thermal driver to
linux-linaro?>
problems I found is that both the AmitDK's generic cpu cooling
code and the generic thermal layer code
are so old in this tree, if u8500 thermal driver has to be pushed
On 9 October 2012 21:26, Morten Rasmussen wrote:
> On Thu, Oct 04, 2012 at 07:02:03AM +0100, Viresh Kumar wrote:
>> On 22 September 2012 00:02, wrote:
>> > SCHED_HMP requires that the platform implements arch_get_hmp_domains()
>> > which should set up the platform specific list of hmp_domains.
On Tue, 2012-10-09 at 22:15 +0530, Viresh Kumar wrote:
> On 9 October 2012 21:02, Jon Medhurst (Tixy) wrote:
> > Considering the confusion over what the correct naming should be, I
> > don't think it's worth me apply the renaming patch at the moment ;-)
>
> This thread went into another direction
On 9 October 2012 22:30, Jon Medhurst (Tixy) wrote:
> Perhaps I misunderstood the bug, I though it was just a name getting
> truncated and was otherwise harmless. If it's causing real problems then
> I'll apply the original suggested patch and not worry about other
> cosmetic renaming issues.
No
Hi Viresh,
Please pull the following changes(v2) for the multiple CPU PMU support
(re-based to v3.6).
Changes v1->v2:
1. Incorporated review comments from Will for few patches(which he will
be queuing for v3.8)
2. Dropped "ARM: perf: register the init functions with the bindings",
still lo
On 9 October 2012 23:16, Sudeep KarkadaNagesha
wrote:
> Hi Viresh,
>
> Please pull the following changes(v2) for the multiple CPU PMU support
> (re-based to v3.6).
Thanks.. Will be included in this release.
--
viresh
___
linaro-dev mailing list
linaro
Greetings,
On 10/06/2012 01:07 AM, Andrey Konovalov wrote:
Greetings,
Minor change to the plan:
* The current llct is *llct-20121006.0*
* October 9: ll rebuild based on llct-20121006.0
ll-20121010.0 has been pushed to linux-linaro-tracking.git.
The pinned manifest is:
http://git.linaro.o
Please take a look at:
https://wiki.linaro.org/Platform/Android/Meetings/2012-10-10
Feel free to add to the agenda and join us in #linaro-meeting on
irc.freenode.net at 13:00 UTC on 2012/10/10.
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software f
On 9 October 2012 23:16, Sudeep KarkadaNagesha
wrote:
> Please pull the following changes(v2) for the multiple CPU PMU support
> (re-based to v3.6).
http://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=shortlog;h=refs/heads/arm-multi_pmu_v2
___
linar
Arrays for governer and driver name are of size CPUFREQ_NAME_LEN or 16.
i.e. 15 bytes for name and 1 for trailing '\0'.
When cpufreq driver print these names (for sysfs), it includes '\n' or ' ' in
the fmt string and still passes length as CPUFREQ_NAME_LEN. If the driver or
governor names are usin
29 matches
Mail list logo
