Re: [PATCH powerdebug] clock: show only active clocks

2013-05-08 Thread Sanjay Singh Rawat

thanks Sebastian

On Wednesday 08 May 2013 04:12 AM, Sebastian Capella wrote:

Hi Sanjay,

Also, clock tree dump (using powerdebug -dc) does not show the clock
info anymore with this change.

Thanks,

Ack, will take care in next patch.


Sebastian


On 7 May 2013 15:05, Sebastian Capella mailto:sebastian.cape...@linaro.org>> wrote:

The original clock display in powerdebug would expand and collapse
subtrees in the clock heirarchy using the enter key.  If we continue
along the lines you're following, you'll want to override the
actions in clock_select to do nothing as they're currently trying to
expand the subtree which is causing the segfault we see now.

ditto


You may instead want to change it so that the new active clock
display works as you've done, but the unfiltered display works like
the original version with expanded and collapsed subtrees.  This
will require a bit more rework, but as it stands, the addition of
the active clock view substantially changes the behavior of the full
clock view.  Was this intentional?
The requirement as per the blueprint is to show *ONLY* the active clocks 
in the window. I thought it will be good to keep all clock info also, so 
added that part.


Thanks,

Sebastian



On 7 May 2013 10:19, Sanjay Singh Rawat mailto:sanjay.ra...@linaro.org>> wrote:

On Monday 06 May 2013 09:36 PM, Mike Turquette wrote:

Quoting Sanjay Singh Rawat (2013-05-04 13:27:58)

- use the clk_summary file of CCF for showing clocks
- add option to show active or all clocks

Signed-off-by: Sanjay Singh Rawat
mailto:sanjay.ra...@linaro.org>>


clk_dump gives a JSON-formatted description of the clock
tree, so it is
a bit more machine readable than clk_summary.  Also if you
wanted to
actually represent a tree structure then clk_dump would be a
better
starting point than using clk_summary, which does not include
parent-child relationship information.

Regards,
Mike

thanks Mike
- The way the clocks are displayed with this patch, the
alignment takes care of the parent/child relationship.
- The format of the content doesn't matter here IIUC, as anyway
we have to parse the content and show it in the clock window.


---
   clocks.c  |   62

++__+++---__-
   display.c |3 +++
   display.h |1 +
   3 files changed, 54 insertions(+), 12 deletions(-)

diff --git a/clocks.c b/clocks.c
index 95acf57..a0510b4 100644
--- a/clocks.c
+++ b/clocks.c
@@ -287,9 +287,8 @@ static int clock_print_header(void)
  int ret;

  if(clock_fw == CCF) {
-   if (asprintf(&buf, "%-35s %-10s %-12s
%-10s %-11s %-15s %-14s %-14s",
-"Name", "Flags", "Rate",
"Usecount", "Children", "Prepare_Count",
-"Enable_Count", "Notifier_Count") < 0)
+   if (asprintf(&buf, "%-30s %-10s %-12s
%-10s (clock toggle key-'c')",
+"Name", "Enable_Count",
"Prepare_Count", "Rate") < 0)
  return -1;
  }
  else {
@@ -297,23 +296,57 @@ static int clock_print_header(void)
   "Name", "Flags", "Rate",
"Usecount", "Children") < 0)
  return -1;
  }
-
  ret = display_column_name(buf);
-
  free(buf);

  return ret;
   }

+/*
+ * Display clocks by refering the clk_summary file of CCF
+ */
+static int display_clk_summary()
+{
+FILE *fp;
+char line[256];
+int afterheader;
+char clock[30];
+int enable_cnt,prepare_cnt,rate;
+
+afterheader = 0;
+fp =
fopen("/sys/kernel/debug/clk/__clk_summary","r");
+if (fp == NULL) {
+printf("error: failed to open clock
tree file\n");
+return -1;
+}
+
+while (NULL != fgets(line,256,fp)) {

Upcoming release.linaro.org migration

2013-05-08 Thread Paul Sokolovsky
Hello,

ITS and LAVA teams are finishing preparations to migrate our official
releases server, http://releases.linaro.org/ , to the Linaro Cloud.
We've scheduled to perform switchover first half of day on Friday, May
10th.

This migration probably doesn't affect many people inside Linaro, as
day-to-day file publishing activity is centered around
http://snapshots.linaro.org/ . There may be some changes which affect
Release Team process, and will be communicated separately (please feel
free to reply to this mail to be included in the discussion).


Thanks,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


[ANNOUNCE] Linaro Ubuntu is now based on Ubuntu 13.04 (Raring)

2013-05-08 Thread Fathi Boudra
Hi,

Linaro Ubuntu baseline is now migrated to latest Ubuntu release (13.04
- Raring).
Daily hardware packs and rootfs are available as usual on
http://snapshots.linaro.org/raring
Pre-built images aren't available yet. They will show up soon.

Note: Quantal based images won't receive any updates anymore.

Cheers,
--
Fathi Boudra
Builds and Baselines Manager | Release Manager
Linaro.org | Open source software for ARM SoCs

___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


dev boards

2013-05-08 Thread Jonathan Aquilina
I have a quick question can the development boards be used in production
environments?

-- 
Jonathan Aquilina
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: dev boards

2013-05-08 Thread Renato Golin
On 8 May 2013 18:21, Jonathan Aquilina  wrote:

> I have a quick question can the development boards be used in production
> environments?
>

Depends on what you consider "production" environment. I have a couple of
"production" buildbots using Pandas which is public and a crucial part of
continuous integration for LLVM, though I'd never use a Panda to drive
robots on a factory floor. ;)

cheers,
--renato
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev


Re: [ANNOUNCE] linux-linaro kernel schedule for 13.05 published

2013-05-08 Thread Andrey Konovalov

On 05/06/2013 11:06 PM, Andrey Konovalov wrote:

https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelSchedule

The 13.05 linux-linaro release will be v3.10-rc2 based,


May 08: ll rebuild based on llct-20130506.0
 * Skipped: "make dtbs" broken in llct-20130506.0

May 08: v3.9 based linux-linaro-core-tracking (llct) rebuild (if there 
are changes to the topics)

 * Done: the tag is llct-20130508.0
 * Changes:
   - linaro-android-3.9-experimental-fixes topic added to revert commit 
5e94686 "ARM: convert build of appended dtb zImage to list of dtbs"

   - linux-3.9.y topic added to pull the v3.9.1 stable tree updates

The next step is:
May 10: ll rebuild based on llct-20130508.0


The last llct update for this cycle is scheduled on May 21,
The last linux-linaro update for this cycle is scheduled on May 23.
May 23 is the linux-linaro code freeze for 13.05 (only bug fixes allowed
after this date).


Thanks,
Andrey


___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev