linaro-dev March 2012

linaro-dev@lists.linaro.org

152 participants
126 discussions

Start a nNew thread

jenkins really broken right now

by John Rigby

Looks like initial git clones always fail. I tried a simple job that just trys to run git and it fails.

12 years, 1 month

[PATCH] Regulator: anatop-regulator: patching to device-tree property "reg".

by Ying-Chun Liu (PaulLiu)

From: "Ying-Chun Liu (PaulLiu)" <paul.liu(a)linaro.org> Change "reg" to "anatop-reg-offset" due to there is a warning of handling no size field in reg. This patch also adds the missing device-tree binding documentation. Signed-off-by: Ying-Chun Liu (PaulLiu) <paul.liu(a)linaro.org> Cc: Shawn Guo <shawn.guo(a)linaro.org> Cc: Mark Brown <broonie(a)opensource.wolfsonmicro.com> Cc: Liam Girdwood <lrg(a)ti.com> --- .../bindings/regulator/anatop-regulator.txt | 29 ++++++++++++++++++++ drivers/regulator/anatop-regulator.c | 5 ++- 2 files changed, 32 insertions(+), 2 deletions(-) create mode 100644 Documentation/devicetree/bindings/regulator/anatop-regulator.txt diff --git a/Documentation/devicetree/bindings/regulator/anatop-regulator.txt b/Documentation/devicetree/bindings/regulator/anatop-regulator.txt new file mode 100644 index 0000000..357758c --- /dev/null +++ b/Documentation/devicetree/bindings/regulator/anatop-regulator.txt @@ -0,0 +1,29 @@ +Anatop Voltage regulators + +Required properties: +- compatible: Must be "fsl,anatop-regulator" +- anatop-reg-offset: Anatop MFD register offset +- anatop-vol-bit-shift: Bit shift for the register +- anatop-vol-bit-width: Number of bits used in the register +- anatop-min-bit-val: Minimum value of this register +- anatop-min-voltage: Minimum voltage of this regulator +- anatop-max-voltage: Maximum voltage of this regulator + +Any property defined as part of the core regulator +binding, defined in regulator.txt, can also be used. + +Example: + + regulator-vddpu { + compatible = "fsl,anatop-regulator"; + regulator-name = "vddpu"; + regulator-min-microvolt = <725000>; + regulator-max-microvolt = <1300000>; + regulator-always-on; + anatop-reg-offset = <0x140>; + anatop-vol-bit-shift = <9>; + anatop-vol-bit-width = <5>; + anatop-min-bit-val = <1>; + anatop-min-voltage = <725000>; + anatop-max-voltage = <1300000>; + }; diff --git a/drivers/regulator/anatop-regulator.c b/drivers/regulator/anatop-regulator.c index 17499a5..53969af 100644 --- a/drivers/regulator/anatop-regulator.c +++ b/drivers/regulator/anatop-regulator.c @@ -138,9 +138,10 @@ static int __devinit anatop_regulator_probe(struct platform_device *pdev) rdesc->type = REGULATOR_VOLTAGE; rdesc->owner = THIS_MODULE; sreg->mfd = anatopmfd; - ret = of_property_read_u32(np, "reg", &sreg->control_reg); + ret = of_property_read_u32(np, "anatop-reg-offset", + &sreg->control_reg); if (ret) { - dev_err(dev, "no reg property set\n"); + dev_err(dev, "no anatop-reg-offset property set\n"); goto anatop_probe_end; } ret = of_property_read_u32(np, "anatop-vol-bit-width", -- 1.7.9.1

12 years, 1 month

[PATCH] EXYNOS: Detect cpuid based on Exynos product codes

by Chander Kashyap

Exynos based SoC's have two different naming conventions. One is S5PC_XXXX and other is EXXX_XXXX. This patch adds generic code to handle EXXX_XXXX connvention. Signed-off-by: Chander Kashyap <chander.kashyap(a)linaro.org> --- arch/arm/include/asm/arch-exynos/cpu.h | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/arch/arm/include/asm/arch-exynos/cpu.h b/arch/arm/include/asm/arch-exynos/cpu.h index 89f2c2e..da89ccf 100644 --- a/arch/arm/include/asm/arch-exynos/cpu.h +++ b/arch/arm/include/asm/arch-exynos/cpu.h @@ -105,10 +105,13 @@ static inline void s5p_set_cpu_id(void) } } +#define EXYNOS_ID ((readl(EXYNOS4_PRO_ID) & (0xF << 24)) >> 24) #define IS_SAMSUNG_TYPE(type, id) \ static inline int cpu_is_##type(void) \ { \ - return s5p_cpu_id == id ? 1 : 0; \ + return ((s5p_cpu_id == id) \ + || (EXYNOS_ID == (#type[sizeof(#type) - 2] - '0'))) \ + ? 1 : 0; \ } IS_SAMSUNG_TYPE(exynos4, 0xc210) -- 1.7.5.4

12 years, 1 month

Linaro-linux Kernel Release 2012.03

by Andrey Konovalov

Greetings, The Linaro Kernel Working Group (KWG) and the Linaro Platform Group are excited to announce the availability our March 2012 development snapshot: linux-linaro-3.3-2012.03-2 As the word "snapshot" implies, these are meant as development kernels and have not been fully validated. You should expect issues and to help us deliver a better kernel in the future, please file bugs in Launchpad at https://bugs.launchpad.net/linux-linaro. The source tarball is available at: https://launchpad.net/linux-linaro/devtrack/12.03/+download/linux-linaro-3.… The kernel sources can also be accessed using git at: git://git.linaro.org/kernel/linux-linaro-tracking.git tag: linux-linaro-3.3-2012.03-2 This kernel includes the following changes from the 2012.02 kernel: - Update to 3.3 - Various patches from Linaro * Versatile Express patches from ARM LT * Gator module for ARM's Streamline Performance Ananlyzer from ARM LT * updated irq_domain patch set from Grant L. * cpuidle core consolidation, cpuidle support for i.MX5/6 and ST-E u8500 from PM WG * updated patch set support for common save and restore code to the Samsung exynos platform from PM WG * updated thermal_cpu_cooling patch set from the power management WG * UFS patches from kernel WG * eMMC4.5 patches from kernel WG * initial dma-buf patch set and some related components for UMM - AOSP 3.3 android patch set A full change log against the 3.3 release is available at: https://launchpad.net/linux-linaro/devtrack/12.03 High Priority Known Issues: - ANDROID_RAM_CONSOLE must be disabled for the android kernel to boot.

12 years, 1 month

Brave 12.03 testers, a call to action

by Zach Pfeffer

Here are our bold volunteers! Annamalai https://android-build.linaro.org/builds/~linaro-android/origen-ics-gcc46-sa… Bero https://android-build.linaro.org/builds/~linaro-android/imx6-ics-gcc46-free… https://android-build.linaro.org/builds/~linaro-android/imx6-ics-gcc47-free… Mathieu https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc46-… Abhishek https://android-build.linaro.org/builds/~linaro-android/vexpress-ics-gcc46-… Botao https://android-build.linaro.org/builds/~linaro-android/imx53-ics-gcc46-fre… Vishal 4460 Chenglie 4430 https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-til… (4430 and 4460) https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-til… (4430 and 4460) https://android-build.linaro.org/builds/~linaro-android/panda-master-gcc44-… (4430 and 4460) Amber 4430, Tony 4460 https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc44-kwg… (4430 and 4460) https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-kwg… (4430 and 4460) <clap> <clap> <clap> <clap> <clap> <clap> Here's the process: Abhishek will cut the builds on Monday 3/26, India Morning. He will boottest each tip. Please watch email or IRC in case he needs some help. After the builds are done he will enter the released build to test into the test spreadsheets (build row) listed here. Please test this build exactly. __Test Spreadsheets__ iMX53, iMX6 https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDE1M… Snowball https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadEF1N… Origen https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDRDV… Panda https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… Vexpress https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… __Process__ STarting on Tuesday, please program the builds and boot um up. The tests are documented at the "Test Description" link on each test sheet. Run through the tests starting with tests that were red in the last release, then tests that were yellow, then the rest and enter in the new results in the spreadsheet in the right column. In this case r12.03. It'll be the column with the build listed in the build row. note which tab you're on. You should see the build name. Also make sure you put the kernel and toolchain that the build is run against. and the build number. Also, and this is new from last time, look at all the bugs in the linaro-android project in launchpad that are marked Fix Committed and if they're fixed, mark them Fix Released with the build you tested. If they're not, please update the bug and set it back to In Progress. When you run into a new issue, please file a bug with the test that was run and the build that it was tested on. For existing issues, please update the bug with the build link that was tested, with a note, "still an issue on http://....#123," etc. If you have any questons, call, email or IRC me. -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams 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

12 years, 1 month

[Question] How To Log QEMU Memory Access

by 周春华

Dear linus.walleij, I am sorry to trouble you. Would you mind give a hand? I got a job that should log the RAM memory access in the QEMU. First, I should find out the code line in QEMU to trap all RAM memory access. After some efforts, I have some conclusions: 1. I have found the function dealing with the translation from the virtual address to physical address in the guest of QEMU, such as [target-arm/helper.c:get_phys_addr], and the page fault handler function [target-arm/helper.c:cpu_arm_handle_mmu_fault]. However, we have not found out the routine of accessing physical address from MMU TLB entry. 2. We have understood the relation of the guest physical address and host virtual address, and found the function [exec.c:qemu_get_ram_ptr] translating the guest physical address to host virtual address. I am pressed for time. Would you mind to help me to check it? If you know the location of the code lines or related messages, please tell me. Thank you for your kindness. The QEMU I used getting from [* http://lists.linaro.org/pipermail/linaro-announce/2012-February/000095.html* ]. Thanks, Jerry Zhou

12 years, 1 month

ARM port of google-talkplugin

by Matt Waddel

Hi, Does anybody know if google-talkplugin has been ported to ARM? This package is required to run Google Hangouts and there are proprietary libraries in the plugin that appear to be compiled for x86 only. I found some old references that these libraries might eventually be ported to ARM and was just wondering if anybody had heard of this work being done. TIA, Matt

12 years, 1 month

Call for Submissions: Linaro Connect Q2.12 Plenaries

by Amber Graner

Hi all! The submission process for Linaro Connect Q2.12 plenaries is now open! There will be 30 minutes of plenary talks daily from Tuesday through Friday at Linaro Connect Q2.12 which is being held from 28 May - 1 June at the Gold Coast Hotel in Hong Kong. These plenary sessions will give Linaro Connect attendees an opportunity to address Linaro, its current and potential Member and Partner representatives as well as the community as a whole. These sessions are broken up into two(2)-15 minute sessions for a total of eight (8) Plenary Slots available for the Linaro Connect Q2.12 event. Do you have a great idea you would like to present to the Linaro Connect Q2.12 attendees? Want to share a Linaro success story and motivate, inspire, excite or educate attendees? Then this is an opportunity for you to get involved in this Linaro Connect event. Plenary Submissions and suggested plenary sessions can be added to the wiki<https://wiki.linaro.org/Events/LinaroConnectQ2.12/Plenaries>; however, for your submission to be considered it needs to be emailed to David Rusling, Linaro CTO <david.rusling(a)linaro.org>, and should include the following information: ** Plenary Title:* * * 3-5 Sentence abstract about what this talk will be about and how it is connected to Linaro.* * * Presenters Name, Company* *The deadline for plenary submissions is 4 May 2012*. This way presenters have time to finish their slide decks *prior* to arriving at Linaro Connect Q2.12 and will allow event planners time for to finalized the schedule ahead of time. More information about the plenary sessions and the selection process can be found on the wiki<https://wiki.linaro.org/Events/LinaroConnectQ2.12/Plenaries> [0]. Questions, comments or feedback concerning the plenary session maybe sent to events(a)linaro.org or to David Rusling <david.rusling(a)linaro.org>. [0] - https://wiki.linaro.org/Events/LinaroConnectQ2.12/Plenaries -- 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)

12 years, 1 month

[PATCH 1/3] cpuidle: use the driver's state_count as default

by Daniel Lezcano

If the state_count is not initialized for the device use the driver's state count as the default. That will prevent to add it manually in the cpuidle driver initialization routine and will save us from duplicate line of code. Signed-off-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> --- drivers/cpuidle/cpuidle.c | 2 +- drivers/cpuidle/driver.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c index 27f77a4..b8a1faf 100644 --- a/drivers/cpuidle/cpuidle.c +++ b/drivers/cpuidle/cpuidle.c @@ -268,7 +268,7 @@ int cpuidle_enable_device(struct cpuidle_device *dev) if (!drv || !cpuidle_curr_governor) return -EIO; if (!dev->state_count) - return -EINVAL; + dev->state_count = drv->state_count; if (dev->registered == 0) { ret = __cpuidle_register_device(dev); diff --git a/drivers/cpuidle/driver.c b/drivers/cpuidle/driver.c index 284d7af..40cd3f3 100644 --- a/drivers/cpuidle/driver.c +++ b/drivers/cpuidle/driver.c @@ -47,7 +47,7 @@ static void __cpuidle_register_driver(struct cpuidle_driver *drv) */ int cpuidle_register_driver(struct cpuidle_driver *drv) { - if (!drv) + if (!drv || !drv->state_count) return -EINVAL; if (cpuidle_disabled()) -- 1.7.5.4

12 years, 1 month

How to install OpenCV in Linaro Android on Pandaboard

by Wijden Gargouri

Hi, I'm doing a project using OpenCV 2.3.1 and I want to embedded this on a pandaboard. So I'm looking for someone who can help me to instal opencv on Pandabord using Linaro Android 11.11 . If you have some link or if you can advise me I would appreciate. Thanks in advance. Best Regards

12 years, 1 month

← Newer
1
2
3
4
5
6
7
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev March 2012