== Zach Pfeffer pfefferz ==
=== Highlights ===
* Integrated TI LT 1080P fix
* Helped get the 11.06 release out the door
* Got Android/LT PoC sync-ups kicked offour individual plans for the
coming week(s).
* Got manual CI process underway
=== Plans ===
* Onboard Botao Sun, Tony Mansson, Chao Yang
* Help fix 39 tip
* Help fix TI tip
* Work with each WG to land their technology this month
=== Issues ===
* None
Corrected the ACTIVITY date range.
On 5 July 2011 08:03, Zach Pfeffer <zach.pfeffer(a)linaro.org> wrote:
> Original at: https://wiki.linaro.org/Platform/Android/Status/2011-06-30
>
> == Key Points for wider discussion ==
> * The Android Team now has dedicated Points-of-Contact for each
> landing team, WG PoCs coming based on resources
> * Upgraded baselines to AOSP 2.3.4
>
> == Team Highlights ==
>
> * Started helping hook LAVA to the autobuilder
> * Planning 0xbench maintenance
> * Fixed EDID parser issue on TI LEB
> * Started AOSP upstreaming planning
> * Created an Android Multimedia test bench
> (https://wiki.linaro.org/MultimediaTest)
>
> == Risks / Issues ==
> * Need lots of Pandaboards
>
> == Miscellaneous ==
> * Bernhard Rosenkraenzer and Frans Gifford joined the Android team
> (welcome email to follow)
>
Original at: https://wiki.linaro.org/Platform/Android/Status/2011-06-30
== Key Points for wider discussion ==
* The Android Team now has dedicated Points-of-Contact for each
landing team, WG PoCs coming based on resources
* Upgraded baselines to AOSP 2.3.4
== Team Highlights ==
* Started helping hook LAVA to the autobuilder
* Planning 0xbench maintenance
* Fixed EDID parser issue on TI LEB
* Started AOSP upstreaming planning
* Created an Android Multimedia test bench
(https://wiki.linaro.org/MultimediaTest)
== Risks / Issues ==
* Need lots of Pandaboards
== Miscellaneous ==
* Bernhard Rosenkraenzer and Frans Gifford joined the Android team
(welcome email to follow)
Can someone explain why uboot copies the initrd and device tree data to
higher memory when we boot panda with a dtb? I'm assuming there's a
reason, but it seems a problematic thing to do (potentially even without
>3/4GB SDRAM present).
-dl
Last meeting minutes:
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/Notes/2011-06-29
Status report:
https://wiki.linaro.org/WorkingGroups/Middleware/Graphics/WeeklyReport
== Key Points for wider discussion ==
* Getting on to the monthly cycles - best practices and lessons learned.
Perhaps we need a common wiki to track the best suggestions coming from
all the groups.
== Team Highlights ==
* Release 11.06 highlights are in official 11.06 Graphics components
release announcement:
https://wiki.linaro.org/Cycles/1106/Release?action=show&redirect=Cycles%2F1…
* Discussing through the implementation of the monthly cycle mechanics
in terms of blueprints and releases.
== Upcoming Deliverables ==
* 11.07 planned deliverables in Launchpad (blueprints, milestone pages)
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
Follow Linaro:
Last meeting minutes: https://wiki.linaro.org/OfficeofCTO/2011-06-28
Status report: https://wiki.linaro.org/OfficeofCTO/WeeklyReport
== Key Points for wider discussion ==
* Dropping linux-linaro kernel tree (Nicolas' tree and, for example,
what is its value and how does it relate to Android kernel) - relevant
thread:
http://lists.linaro.org/pipermail/linaro-dev/2011-June/005522.html.
Consolidation of kernel trees can take a fair amount of time. Kernel
developers are not using linux-linaro tree, but the upstream kernel tree
instead, and there are no other consumers of that tree. On the other
hand, the value of the linux-linaro tree can be apparent when needing a
reasonably stable kernel particularly for "lumpy" upstream patches such
as device tree related ones. More opinions are needed in the ongoing
list discussion.
== Team Highlights ==
* ARMHF: working on the documentation work items (see blueprint -
https://blueprints.launchpad.net/linaro/+spec/linaro-octo-armhf-benchmarks
for the 11.06 work items). Related to porting Java is now fixed and java
packages can be compiled - new obstacle for packages compilation is
Haskell (boostrapping of which is being attempted now). Javascript
benchmarks are being looked at (trying to do with a basic webkit-based
browser - something like midori - to see if there is any performance
difference between hard- and soft- float).
* Boot architecture: SIG weekly meetings have started, trying to nail
down a document related to what we care about in boot architecture.
* Device tree: work has been progressing mostly reviewing the
documentation being used - still need to address the reviewers'
comments. Also started looking at the initialization order of devices -
the init order of kernel modules - with a submitted patch which allows
the device drivers to request deferral on probing devices : if the
resource cannot be granted immediately then the driver requests the
deferral of the probing for a later point in time. Request of a resource
actually creates also a resource reference for the driver, which can be
used for power management purposes. The patch is being reviewed now, and
could simplify some of the performance problems we have now.
* Java work (https://wiki.linaro.org/OfficeofCTO/OptimizedJavaVM): plan
progress including a chat with George getting in agreement on the next
steps. Regarding the long term plan, it requires some project sponsor as
the plan is not sustainable by Linaro alone anymore.
* Other - Participation to Dublin event for Ubuntu: focus on
discussions related to ARMHF, and server images.
== Miscellaneous ==
* David back from vacation. Ilias will be on vacation from 11July - 31July.
* Linaro Connect is around the corner: Please check the
https://wiki.linaro.org/Events/LinaroConnectQ3.11 for updates and
instructions!
--
Ilias Biris ilias.biris(a)linaro.org
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs
Follow Linaro:
Currently, ramp_delay variable is used uninitialzed in
max8997_set_voltage_ldobuck which gets called through
regulator_register calls.
To fix the problem, in max8997_pmic_probe, ramp_delay initialization
code is moved before calls to regulator_register.
Cc: Liam Girdwood <lrg(a)ti.com>
Cc: Mark Brown <broonie(a)opensource.wolfsonmicro.com>
Cc: MyungJoo Ham <myungjoo.ham(a)samsung.com>
Cc: Kyungmin Park <kyungmin.park(a)samsung.com>
Cc: Samuel Ortiz <sameo(a)linux.intel.com>
Signed-off-by: Tushar Behera <tushar.behera(a)linaro.org>
---
drivers/regulator/max8997.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/regulator/max8997.c b/drivers/regulator/max8997.c
index 10d5a1d..0fc7b8c 100644
--- a/drivers/regulator/max8997.c
+++ b/drivers/regulator/max8997.c
@@ -1124,6 +1124,10 @@ static __devinit int max8997_pmic_probe(struct platform_device *pdev)
0x3f);
}
+ /* Misc Settings */
+ max8997->ramp_delay = 10; /* set 10mV/us, which is the default */
+ max8997_write_reg(i2c, MAX8997_REG_BUCKRAMP, (0xf << 4) | 0x9);
+
for (i = 0; i < pdata->num_regulators; i++) {
const struct voltage_map_desc *desc;
int id = pdata->regulators[i].id;
@@ -1148,10 +1152,6 @@ static __devinit int max8997_pmic_probe(struct platform_device *pdev)
}
}
- /* Misc Settings */
- max8997->ramp_delay = 10; /* set 10mV/us, which is the default */
- max8997_write_reg(i2c, MAX8997_REG_BUCKRAMP, (0xf << 4) | 0x9);
-
return 0;
err:
for (i = 0; i < max8997->num_regulators; i++)
--
1.7.4.1
Hello,
We're currently at 80% usage of the filesystem for builds and may hit
issues later. So, with 11.06 release out, I'd like to ask anyone who's
using https://android-build.linaro.org to go and over your jobs and/or
specific builds in them and remove anything old and unneeded.
To do so, go https://android-build.linaro.org/ , select "My Builds"
tab, open unneeded jobs and click "Delete...".
I'm also going to enforce garbage-collection settings for all personal
jobs at keep max 30 days or latest 5 builds (well, I'll start with 10
builds, but if we'll hit 90% space usage, that will need to be
tightened). (Official builds remain at 90days/last 100 builds.)
If you have specific builds which you'd like to keep longer for some
reason/not be subject of automatic deletion, please explicitly mark
these as "Keep this build forever":
1. Log in to Jenkins at https://android-build.linaro.org/jenkins/
2. Open job, then the build in question.
3. Click "Keep this build forever" button in the top right corner.
4. For each such build, it would be nice if you provided
reason/description: on build's page (not on job's page), click
"add description" in the top right corner and write short description.
Example of the above can be seen at
https://android-build.linaro.org/jenkins/job/linaro-android_leb-panda/ ,
where #99 is marked as last build with kernel 2.6.35 and #100 as first
with 2.6.38.
Please let me know if there're any suggestions and thanks for
cooperation.
--
Best Regards,
Paul