linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

by Mike Turquette

Hi all, Some of you may have heard of a tool we use inside TI for debugging on OMAP. It's a nice userspace tool which can inspect many aspects of hardware state called "omapconf". The tool has just been open sourced and can be found at: https://github.com/omapconf/omapconf Regards, Mike

13 years, 1 month

[PATCH][V2] cpuidle : rename function name "__cpuidle_register_driver"

by Daniel Lezcano

The function __cpuidle_register_driver name is confusing because it suggests, conforming to the coding style of the kernel, it registers the driver without taking a lock. Actually, it just fill the different power field states with a decresing value if the power has not been specified. Clarify the purpose of the function by changing its name and move the condition out of this function. This patch fix nothing and does not change the behavior of the function. It is just for the sake of clarity. IHMO, reading in the code: + if (!drv->power_specified) + set_power_states(drv); is much more explicit than: - __cpuidle_register_driver(drv); Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- drivers/cpuidle/driver.c | 15 +++++++++------ 1 files changed, 9 insertions(+), 6 deletions(-) diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c index 424bc81..87db387 100644 --- a/drivers/cpuidle/driver.c +++ b/drivers/cpuidle/driver.c @@ -18,9 +18,10 @@ static struct cpuidle_driver *cpuidle_curr_driver; DEFINE_SPINLOCK(cpuidle_driver_lock); int cpuidle_driver_refcount; -static void __cpuidle_register_driver(struct cpuidle_driver *drv) +static void set_power_states(struct cpuidle_driver *drv) { int i; + /* * cpuidle driver should set the drv->power_specified bit * before registering if the driver provides @@ -35,10 +36,8 @@ static void __cpuidle_register_driver(struct cpuidle_driver *drv) * an power value of -1. So we use -2, -3, etc, for other * c-states. */ - if (!drv->power_specified) { - for (i = CPUIDLE_DRIVER_STATE_START; i < drv->state_count; i++) - drv->states[i].power_usage = -1 - i; - } + for (i = CPUIDLE_DRIVER_STATE_START; i < drv->state_count; i++) + drv->states[i].power_usage = -1 - i; } /** @@ -58,8 +57,12 @@ int cpuidle_register_driver(struct cpuidle_driver *drv) spin_unlock(&cpuidle_driver_lock); return -EBUSY; } - __cpuidle_register_driver(drv); + + if (!drv->power_specified) + set_power_states(drv); + cpuidle_curr_driver = drv; + spin_unlock(&cpuidle_driver_lock); return 0; -- 1.7.5.4

13 years, 1 month

[PATCH v3 0/3] devfreq: Add support for devices which can idle

by Rajagopal Venkat

This patchset updates devfreq core to add support for devices which can idle. When device idleness is detected perhaps through runtime-pm, need some mechanism to suspend devfreq load monitoring and resume when device is back online. patch 1 introduce core design changes - per device work, decouple delayed work from core and event based interaction. patch 2 add devfreq suspend and resume apis. patch 3 add new sysfs attribute for governor predicted next target frequency and callback for current device frequency. The existing devfreq apis are kept intact. Two new apis devfreq_suspend_device() and devfreq_resume_device() are added to support suspend/resume of device devfreq. Changes since v1: - revised locking mechanism - added kerneldoc comments for load monitoring helper functions - Fixed minor review comments Changes since v2: - added new helper function for polling interval update - Handled work suspend/resume contention between devfreq driver and sysfs -- Rajagopal Venkat (3): devfreq: Core updates to support devices which can idle devfreq: Add suspend and resume apis devfreq: Add current freq callback in device profile Documentation/ABI/testing/sysfs-class-devfreq | 15 +- drivers/devfreq/devfreq.c | 469 ++++++++++++-------------- drivers/devfreq/governor.h | 13 + drivers/devfreq/governor_performance.c | 16 +- drivers/devfreq/governor_powersave.c | 16 +- drivers/devfreq/governor_simpleondemand.c | 33 ++ drivers/devfreq/governor_userspace.c | 23 +- include/linux/devfreq.h | 49 +-- 8 files changed, 341 insertions(+), 293 deletions(-) -- 1.7.11.3

13 years, 1 month

Test Result Summary for Calendar Week 38.

by Botao Sun

Calendar Week 38: Here is test result summary for Linaro ubuntu platform on following boards: 1) ARM Versatile Express A9; 2) Samsung Origen; 3) TI Panda Board 4430; 4) TI Panda Board 4460. *Synopsis: YouTube works on Panda 4460 but failed on all the other boards. All DS5 test passed on above 4 boards after pre-installed "arm-ds5-target" package.* 1. vexpress A9 + ubuntu (Column Z): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdFNmV… Device tree blob files have disappeared for 6 weeks, and 480p video playback doesn't work for 2 months. Application debug in DS5 suite works well now, by pre-install "arm-ds5-target" package on target. YouTube totally doesn't work, only preview picture shows. 2. Origen + ubuntu (Column V): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEowN… Dead lock error exists for 9 weeks, Unity 3D is unavailable from the beginning, Mini HDMI output never works either. WiFi is unavailable for 4 weeks and Bluetooth is even broken for a longer time. 480p video playback doesn't work for 2 months, however, DS5 works well on all features with "arm-ds5-target" package pre-installed. 3. Panda 4430 + ubuntu (Column W): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… YouTube HTML5 video playback failed again, it will hang the system. 480p video playback is unavailable for 2 months. Bluetooth headset works, but can't be powered off in paired condition, otherwise, it will hang the board. DS5 works. 4. Panda 4460 + ubuntu (Column W): https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AroPySpr4FnEdEwwZ… YouTube HTML5 video playback works well. However, 480p video playback from SD card is still unavailable for 9 weeks. Bluetooth works except file transfer failed, and a paired device can be shut down without any side effect. DS5 works. For the previous week (Calendar week 37) summary, please refer to attachment. Thank you. BR Botao Sun

13 years, 1 month

[PATCH 0/2] Thermal patches to deactive cooling devices when needed

by zhanghongbo

From: "hongbo.zhang" <hongbo.zhang(a)linaro.com> This patch set contains two patches. [PATCH 1/2] A new interface is introduced to deactive all the referenced cooling devices when thermal zone is disabled. Because the cooling device list is maintained in the generic thermal layer, the thermal driver cannot walk through the list and cannot deactive its cooling devices either. This interface is needed in the .set_mode callback when the thermal zone mode is set to "disabled". [PATCH 2/2] When a cooling device is unbound it should be deactived, otherwise cooling device will keep active after unbinding, this isn't what we expect. hongbo.zhang (2): Thermal: Add interface to deactive cooling devices. Thermal: Deactive cooling device when unbind it. drivers/thermal/thermal_sys.c | 24 ++++++++++++++++++++++++ include/linux/thermal.h | 1 + 2 files changed, 25 insertions(+) -- 1.7.11.3

13 years, 1 month

[PATCH 1/2][RFC] cpuidle : move driver's refcount to cpuidle

by Daniel Lezcano

In the next patch, we will support different cpuidle drivers tied with a cpu. In this case we should move the refcount to the cpuidle_driver structure to handle several drivers at a time. Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- drivers/cpuidle/driver.c | 11 ++++++----- include/linux/cpuidle.h | 1 + 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c index 87db387..676febd 100644 --- a/drivers/cpuidle/driver.c +++ b/drivers/cpuidle/driver.c @@ -16,7 +16,6 @@ static struct cpuidle_driver *cpuidle_curr_driver; DEFINE_SPINLOCK(cpuidle_driver_lock); -int cpuidle_driver_refcount; static void set_power_states(struct cpuidle_driver *drv) { @@ -92,7 +91,7 @@ void cpuidle_unregister_driver(struct cpuidle_driver *drv) spin_lock(&cpuidle_driver_lock); - if (!WARN_ON(cpuidle_driver_refcount > 0)) + if (!WARN_ON(drv->refcnt > 0)) cpuidle_curr_driver = NULL; spin_unlock(&cpuidle_driver_lock); @@ -106,7 +105,7 @@ struct cpuidle_driver *cpuidle_driver_ref(void) spin_lock(&cpuidle_driver_lock); drv = cpuidle_curr_driver; - cpuidle_driver_refcount++; + drv->refcnt++; spin_unlock(&cpuidle_driver_lock); return drv; @@ -114,10 +113,12 @@ struct cpuidle_driver *cpuidle_driver_ref(void) void cpuidle_driver_unref(void) { + struct cpuidle_driver *drv = cpuidle_curr_driver; + spin_lock(&cpuidle_driver_lock); - if (!WARN_ON(cpuidle_driver_refcount <= 0)) - cpuidle_driver_refcount--; + if (drv && !WARN_ON(drv->refcnt <= 0)) + drv->refcnt--; spin_unlock(&cpuidle_driver_lock); } diff --git a/include/linux/cpuidle.h b/include/linux/cpuidle.h index 279b1ea..a4ff9f8 100644 --- a/include/linux/cpuidle.h +++ b/include/linux/cpuidle.h @@ -131,6 +131,7 @@ static inline int cpuidle_get_last_residency(struct cpuidle_device *dev) struct cpuidle_driver { const char *name; struct module *owner; + int refcnt; unsigned int power_specified:1; /* set to 1 to use the core cpuidle time keeping (for all states). */ -- 1.7.5.4

13 years, 1 month

Re: Linaro Website Contact

by Amber Graner

Hi Christoph, Thank you so much for contacting us. I am forwarding your question to our graphics team and CC'ing their Tech Lead. More information on the Linaro Graphics team can be found at: https://wiki.linaro.org/WorkingGroups/Middleware/Graphics You can also send future questions to the linaro-dev mailing list or you may ask in the #linaro IRC channel on irc.freenode.net. Please let me know if there if I can be of further assistance to you. All the best, Amber On 18 September 2012 19:21, Linaro Content Management System < linaro(a)freshleafmedia.co.uk> wrote: > ** > Linaro Website Form Submission - *Contact Form* > A user has submitted the following information on the Linaro website: > > Name Christoph Stadelmann Email christoph.stadelmann(a)gmx.de Message Dear > Sir or Madam, I just got the snowball board. I want to know if there is > something similar to the libvga in the linaro OS in order to map and have > direct write access to the HDMI frame buffer. Thank you very much. > Christoph Stadelmann Form Url http://www.linaro.org/contact > > This enquiry was received via the *Contact Form* on the website: > http://www.linaro.org/contact > > Thank you, > > Linaro > -- Amber Graner User Experience and Community Specialist Linaro.org <http://www.linaro.org/>* **│ *Open source software for ARM SoCs* *** Follow *Linaro: *Facebook <http://www.facebook.com/pages/Linaro> | Twitter<http://twitter.com/#%21/linaroorg> | Blog <http://www.linaro.org/linaro-blog/> *+1.828.582.9469* cell *+1.828.395.1049* office irc: akgraner amber.graner(a)linaro.org (email and Google chat)

13 years, 1 month

fastmodel run over ubuntu 64bit machine

by Lei Wen

Hi, Does anyone try to run the fastmodel over ubuntu 64bit machine? I try to run the simulation over Cortex-A15 model, but get below error message when start: "Fatal Error: No CreateCADIBroker entry point found. Not a CADI 2.0 model ?" Anyone knows what this message means? Do I need any additional configuration to bring up the fastmodel over 64bit ubuntu? Thanks, Lei

13 years, 1 month

[PATCH 1/3] cpuidle : remove unused ref count function

by Daniel Lezcano

These two functions are never used. Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- drivers/cpuidle/driver.c | 29 +---------------------------- include/linux/cpuidle.h | 4 ---- 2 files changed, 1 insertions(+), 32 deletions(-) diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c index 58bf3b1..40cd3f3 100644 --- a/drivers/cpuidle/driver.c +++ b/drivers/cpuidle/driver.c @@ -16,7 +16,6 @@ static struct cpuidle_driver *cpuidle_curr_driver; DEFINE_SPINLOCK(cpuidle_driver_lock); -int cpuidle_driver_refcount; static void __cpuidle_register_driver(struct cpuidle_driver *drv) { @@ -90,34 +89,8 @@ void cpuidle_unregister_driver(struct cpuidle_driver *drv) } spin_lock(&cpuidle_driver_lock); - - if (!WARN_ON(cpuidle_driver_refcount > 0)) - cpuidle_curr_driver = NULL; - + cpuidle_curr_driver = NULL; spin_unlock(&cpuidle_driver_lock); } EXPORT_SYMBOL_GPL(cpuidle_unregister_driver); - -struct cpuidle_driver *cpuidle_driver_ref(void) -{ - struct cpuidle_driver *drv; - - spin_lock(&cpuidle_driver_lock); - - drv = cpuidle_curr_driver; - cpuidle_driver_refcount++; - - spin_unlock(&cpuidle_driver_lock); - return drv; -} - -void cpuidle_driver_unref(void) -{ - spin_lock(&cpuidle_driver_lock); - - if (!WARN_ON(cpuidle_driver_refcount <= 0)) - cpuidle_driver_refcount--; - - spin_unlock(&cpuidle_driver_lock); -} diff --git a/include/linux/cpuidle.h b/include/linux/cpuidle.h index 279b1ea..5abf62b 100644 --- a/include/linux/cpuidle.h +++ b/include/linux/cpuidle.h @@ -145,8 +145,6 @@ extern void disable_cpuidle(void); extern int cpuidle_idle_call(void); extern int cpuidle_register_driver(struct cpuidle_driver *drv); extern struct cpuidle_driver *cpuidle_get_driver(void); -extern struct cpuidle_driver *cpuidle_driver_ref(void); -extern void cpuidle_driver_unref(void); extern void cpuidle_unregister_driver(struct cpuidle_driver *drv); extern int cpuidle_register_device(struct cpuidle_device *dev); extern void cpuidle_unregister_device(struct cpuidle_device *dev); @@ -169,8 +167,6 @@ static inline int cpuidle_idle_call(void) { return -ENODEV; } static inline int cpuidle_register_driver(struct cpuidle_driver *drv) {return -ENODEV; } static inline struct cpuidle_driver *cpuidle_get_driver(void) {return NULL; } -static inline struct cpuidle_driver *cpuidle_driver_ref(void) {return NULL; } -static inline void cpuidle_driver_unref(void) {} static inline void cpuidle_unregister_driver(struct cpuidle_driver *drv) { } static inline int cpuidle_register_device(struct cpuidle_device *dev) {return -ENODEV; } -- 1.7.5.4

13 years, 1 month

[ANNOUNCE] Requesting work for the LAVA Lab

by David Zinman

In an effort to structure the demands on the LAVA lab as Linaro continues to grow and requests become more frequent, the LAVA team has put in place a process for requesting work in the LAVA lab. More platforms and devices are being added to the LAVA lab and the demands on the LAVA team are growing. With this process we hope to be able to accommodate all work requests as quickly as possible. Please see https://wiki.linaro.org/Platform/LAVA/DevOps/LavaLabProcess This is a work in progress and we invite all to comment. -- David Zinman Linaro Release Manager | Project Manager Linaro.org | Open source software for ARM SoCs

13 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev