CC'ing linaro-dev
On Tue, Jan 4, 2011 at 1:18 PM, Yong Shen <yong.shen(a)linaro.org> wrote:
> hi there,
>
> In last weekly meeting, we talked about the real time display of clock
> information in powerdebug.
What do you mean by real-time display?
powerdebug will only refresh it's information every 'n' seconds. At
that point, the 'show' function for the sysfs rate entry should call
get_rate() for the clock.
> Actually, this feature can be easily supported. if you found some
> clocks' information stay unchanged after your drivers change clock
> setting, it may be caused by the wrong way of clock information
> exposing.
>
> In the last several weeks, Jeremy and I reviewed the clock debug code
> based on common clock struct. In this code, I used below code to
> expose clock information:
>
>
> +static int clk_debug_rate_get(void *data, u64 *val)
> +{
> + struct clk *clk = data;
> +
> + *val = (u64)clk_get_rate(clk);
> + return 0;
> +}
> +DEFINE_SIMPLE_ATTRIBUTE(clk_debug_rate_fops, clk_debug_rate_get, NULL,
> + "%llu\n");
> +
> .....
> + d = debugfs_create_file("rate", S_IRUGO, clk->dentry, (void *)clk,
> + &clk_debug_rate_fops);
>
> Therefore, whenever the clock information is accessed, it can reflect
> the truth, since it calls clk interface like clk_get_rate() to get the
> right value.
Why is it called clk_debug_rate_get()? Is there not a standard
clk_rate_get() that we can use?
> Previously, some of you might use a variable to store clock
> information like rate or count, and expose these variable to sysfs,
> which is why they are not updated when the real clock information is
> changing.
Right, storing in variables will give wrong results if you're in the
middle of a rate refresh.
The following changes since commit a581cf741c49c220d159fac1fdbde28255c2e7e3:
Merge branch 'linaro-stable' into linaro-packaged (2011-01-03 14:41:56 -0700)
are available in the git repository at:
git://git.linaro.org/boot/u-boot-linaro-stable.git packaged
John Rigby (2):
debian/rules: remove -Bsymbolic-functions from LDFLAGS
u-boot-linaro-2010.12-0ubuntu1
debian/changelog | 17 ++++++++++++-----
debian/rules | 4 ++++
2 files changed, 16 insertions(+), 5 deletions(-)
Greetings,
Enclosed you'll find a link to the agenda, minutes and actions from the
Linaro kernel working group weekly meeting of December 13, 2010.
https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Meetings/2010-12-…<https://wiki.linaro.org/WorkingGroups/KernelConsolidation/Meetings/2010-11-…>
== Summary ==
* Reviewed Freescale BSP. Many drivers are close to being upstreamable.
* eMMC performance improvement, initial numbers shows 5% performance gains
for large writes and 10% performance gains for large reads.
* USB patches for 8500 have been accepted into Greg KH's tree, and Felipe
Balbi's tree.
* u-boot is in the final phases of the 2010-12 release. Patch from last
week (environment code would incorrectly report correctable errors) accepted
in mainline.
* Working RTC issues: timer list and timer queue which are precursors to
getting the Android alarms upstreamed. Patches in -tip slated for 2.6.38.
LWN article for timers and alarms.
* Working IRQ code in core code in support of virtual IRQ. Working on QEMU
model of Versatile Express and the Nvidia Tegra (Serial port and eMMC).
Dusting off u-boot work that John Rigby has done so that device tree is
passed correctly to kernel. Kernel configuration management solution in the
works -- "Kconfig fragment". Configuration process loads an alternative
per-board Kconfig file that sets defaults for Kconfig, and then sets up with
the full Kconfig, so that you can have definitions set up for a family of
SoCs or boards.
* Looked at gitdm tool, considering sending in a patch to list Linaro
people as belonging to Linaro instead of to whatever gitdm currently
accounts them to.
* Finished kexec() blueprint specification, will get it reviewed next.
* Progress on RCU priority boosting, additional energy-management tasks and
scalability tasks look to be easily handled.
Regards,
Mounir
This might be of interest to the wider Linaro developer community.
---------- Forwarded message ----------
From: igep-platform.com <admin(a)igep.es>
Date: Thu, Dec 30, 2010 at 2:28 AM
Subject: IGEPv2 board based on new DM3730@1GHz running Linaro Distribution
To: admin(a)igep.es
Hi IGEP users, We have prepared some nice demos showing IGEPv2 board
based on new DM3730@1GHz running Linaro Distribution: Internet
navigation, youtube, source code compilation, video playing and many
more (search for "Linaro omap" on youtube).
http://www.youtube.com/watch?v=GHx0jCJ1PRghttp://www.youtube.com/watch?v=yhglD0mJiLkhttp://www.youtube.com/watch?v=RnvDWQaZ4p8http://www.youtube.com/watch?v=xG88QxJp8Zghttp://www.youtube.com/watch?v=MXPTs7xzx0A Linaro™ is a Not For Profit
(NFP) organization that aims to make embedded open source development
easier and faster. Linaro will create a common software foundation for
software stacks and distributions to land on and provide the best open
source tools for developers to develop on. The focus is on low level
software around the Linux kernel that touches the silicon, key pieces
of middleware that enable new markets and tools that help the
developer write and debug code. Linaro aims to maximize the potential
of the latest features of ARM-based processors, helping provide
optimized performance in a lower power envelope. Linaro is both a
community and a supported project with engineering teams spread
globally. ISEE will provide this Linaro Demo on a microSD-card on
1Q-2011. Regards, ISEE Sales
All,
The weekly report for the Linaro Infrastructure team may be found at:-
Status report: https://wiki.linaro.org/Platform/Infrastructure/Status/2010-12-23
Burndown chart: This link is awaiting the production of new burndown charts.
The Infrastructure related blueprints from the maverick cycle, of which currently there are 4 active ones (4 from the last report), are showing that there are 9 work items in progress (8 last report), and 10 work items to undertake (11 last report). These are to be moved into the natty cycle if still required.
* arm-m-validation-dashboard; 0 work items completed (1 last report); 4 in progress (3 last report); 6 to do (6 last report); 0 work item added (1 last report)
* arm-m-image-building-console; no change in status from last report; 3 in progress; 3 to do
* arm-m-automated-testing-framework; no change in status from last report; 1 in progress; 0 to do
* arm-m-testsuites-and-profilers; no change in status from last report; 1 in progress; 1 to do
In the natty cycle, the following lists the current active Blueprints, or Blueprints planned and not started. Currently there are 5 active Blueprints (4 from the last report), which are showing that there are 9 work items in progress (8 last report), 43 work items to undertake (41 last report), 2 work items postponed in total (2 last report) and 0 work items added (1 item added last report).
* other-linaro-n-improve-linaro-media-create: 8 work items completed in total (7 last week); 2 work items in progress (3 last week); 8 work items to do (8 last week); 1 work item added this week (1 last week).
* other-linaro-n-test-result-display-in-launch-control: 0 work items completed (0 last week); 1 work item in progress (1 last week); 10 work items to do (10 last week); 0 work items added (0 last week)
* other-linaro-n-patch-tracking: 0 work item completed (0 last week); 2 work items in progress (2 last week); 9 work items to do (9 last week)
* other-linaro-n-image-building: 2 work items in progress (2 last week); 5 work items to do (5 last week); 2 work items postponed (2 last week); 0 work items added (0 last week)
* other-linaro-n-continuous-integration: Not started - awaiting a Hudson build server (RT#42278).
* other-linaro-n-package-development-tools: Not Started; 9 work items to do
* other-linaro-n-benchmark-reports-in-launch-control: 2 work item completed (2 last week); 2 work items in progress (2 last week); 2 work items to do (2 last week)
Specifics accomplished this week include:-
* Reports have indicated reduced accomplishments due to people being on leave.
* Work on a comprehensive MX51 test plan than headless one: https://wiki.linaro.org/Platform/QA/TestCases/IMX51EVK - Adding SATA, Backlight, Touchscreen, Keypad, etc.
* [ImproveLinaroMediaCreate] port check_device to python:DONE.
* Submitted the hardware pack licence request to the TSC for approval.
Please let me know if you have any comments or questions.
Kind Regards,
Ian
Hi
The bug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46883 files
against GCC trunk also happens with linaro gcc 4.5
My guess is that there is a backported patch from trunk into linaro
4.5 tree thats causing this ICE
This ICE does not happen on upstream gcc-4.5 branch
I havent figured out the commit yet. Should you need a bug in linaro
bug tracker I will be happy to file one
Thanks
-Khem