linaro-dev

linaro-dev@lists.linaro.org

4332 discussions

[PATCH] thermal: Fix for setting the thermal zone mode to enable/disable

by Amit Daniel Kachhap

Basically without this patch changing the mode of thermal zone is not possible as wrong string size is passed to strncmp. Signed-off-by: Amit Daniel Kachhap <amit.kachhap(a)linaro.org> --- drivers/thermal/thermal_sys.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/thermal/thermal_sys.c b/drivers/thermal/thermal_sys.c index 220ce7e..96da1af 100644 --- a/drivers/thermal/thermal_sys.c +++ b/drivers/thermal/thermal_sys.c @@ -152,9 +152,9 @@ mode_store(struct device *dev, struct device_attribute *attr, if (!tz->ops->set_mode) return -EPERM; - if (!strncmp(buf, "enabled", sizeof("enabled"))) + if (!strncmp(buf, "enabled", sizeof("enabled") - 1)) result = tz->ops->set_mode(tz, THERMAL_DEVICE_ENABLED); - else if (!strncmp(buf, "disabled", sizeof("disabled"))) + else if (!strncmp(buf, "disabled", sizeof("disabled") - 1)) result = tz->ops->set_mode(tz, THERMAL_DEVICE_DISABLED); else result = -EINVAL; -- 1.7.1

13 years, 3 months

ci.linaro.org is back and (hopefully) stable.

by James Tunnicliffe

Hi, The migration of ci.linaro.org to new hardware is complete. We hope that this will result in a more stable and responsive system. We have had a few builds run successfully so everything seems to be fine, but we will be keeping an eye on it. Please let the infrastructure team know of any problems that you see with the new set up and we will make sure they are fixed ASAP. Thanks, -- James Tunnicliffe

13 years, 3 months

[PATCH v8 0/8] Consolidate cpuidle functionality

by Robert Lee

This patch series moves various functionality duplicated in platform cpuidle drivers to the core cpuidle driver. Also, the platform irq disabling was removed as it appears that all calls into cpuidle_call_idle will have already called local_irq_disable(). These changes have been pulled into linux-next. Len, Andrew, can a request be made for Linus to pull these changes? Acked-by: Jean Pihet<j-pihet(a)ti.com> (v6) Tested-by: Jean Pihet<j-pihet(a)ti.com> (v6, omap3) Tested-by: Amit Daniel<amit.kachhap(a)linaro.org> (v6, Exynos4) Tested-by: Robert Lee<rob.lee(a)linaro.org> (imx51, imx6q) Reviewed-by: Kevin Hilman <khilman(a)ti.com> Reviewed-by: Daniel Lezcano <daniel.lezcano(a)linaro.org> Reviewed-by: Deepthi Dharwar<deepthi(a)linux.vnet.ibm.com> (core cpuidle only) v8 changes: * v7 testing in linux-next revealed a bug reported by Hugh Dickins on x86 platforms. Investigated and fixed by Daniel Lezcano. * Made a slight change to the defaut ARM WFI state macro as Daniel Lezcano suggested the previous interface was prone to mis-use by platforms that set power_specified to 1. * updated to kernel v3.3 These v8 fixes have been applied to the pull tree being used by linux-next: git://git.linaro.org/people/rob_lee/linux.git cpuidle_consol_pull v7 submission can be found here: http://www.spinics.net/lists/arm-kernel/msg162290.html v7 changes: * Made some struct whitespace alignment changes. * Fixed a coding style violation (thanks Jean Pihet) * Fixed a bug in davinci cpuidle (thanks Jean Pihet) * Corrected the common ARM cpuidle WFI state description to be ARM platform agnostic (thanks Kevin Hilman) * Fixed the problem causing x86 and PPC builds to fail (thanks Deepthi) * Re-added a line of code that was mistakenly removed (thanks Deepthi) v6 submission can be found here: http://www.spinics.net/lists/arm-kernel/msg162018.html v6 changes: * Fixed mindless bug in CONFIG_ARCH_HAS_RELAX code in drivers/cpuidle/cpuidle.c * Removed inline from wrapper function (thanks Mike Turquette and Rob Herring) * Add zeroing out of last_residency if error value is returned (thanks Mike) * Made drivers/cpuidle/cpuidle.c more intelligently handle en_core_tk_irqen flag allowing removal of the if (en_core_tk_irqen) in cpuidle_idle_call (thanks Daniel Lezcano) * Moved CPUIDLE_ARM_WFI_STATE macro to arch/arm/include/asm/cpuidle.h (thanks Jean Pihet) * Cleaned up some comments and a stray change (thanks Jean) v5 submission can be found here: http://www.spinics.net/lists/arm-kernel/msg161596.html v5 changes: * Added common cpu_do_idle function to core cpuidle * Added time keep irq en wrapper to core cpuidle * Removed pre/post enter * Re-added platforms that can use new common code. v4 submission can be found here: http://lists.infradead.org/pipermail/linux-arm-kernel/2012-January/082742.h… v4 changes: * Removed drivers/cpuidle/common.c ** Removed the initialization helper functions ** Removed the wrapper used to consolidate time keeping and irq enable/disable * Add time keeping and local_irq_disable handling in cpuidle_call_idle(). * Made necessary modifications to a few platforms that required the most changes ** Note on omap3: changed structure of omap3_idle_drvdata and added per_next_state and per_saved_state vars to accomodate new framework. v3 submission can be found here: http://www.spinics.net/lists/arm-kernel/msg156751.html v3 changes: * Made various code organization and style changes as suggested in v2 review. (thanks Mark Brown, Rob Herring, Mike Turquette, Kevin Hillman, Daniel Lezcano) * Removed at91 use of common code. A separate effort is underway to clean at91 code and the author has offered to convert to common interface as part of those changes (if this common interface is accepted in time). * Made platform cpuidle_driver objects __initdata and dynamically added one persistent instance of this object in common code. * Removed imx5 pm usage of gpc_dvfs clock as it is no longer needed after being enabled during clock initialization. * Re-organized patches. v2 submission can be found here: http://comments.gmane.org/gmane.linux.ports.arm.kernel/144199 v2 changes: * Common interface moved to drivers/cpuidle and made non arch-specific. * Made various fixes and suggested additions to the common cpuidle code from v1 review. (Thanks Rob Herring and Mark Brown) * Added callback for filling in driver_data field as needed. * Modified the various platforms with these changes. v1 submission can be found here: http://comments.gmane.org/gmane.linux.ports.arm.kernel/142791 Robert Lee (8): cpuidle: Add common time keeping and irq enabling ARM: at91: Consolidate time keeping and irq enable ARM: kirkwood: Consolidate time keeping and irq enable ARM: davinci: Consolidate time keeping and irq enable ARM: omap: Consolidate OMAP3 time keeping and irq enable ARM: omap: Consolidate OMAP4 time keeping and irq enable ARM: shmobile: Consolidate time keeping and irq enable SH: shmobile: Consolidate time keeping and irq enable arch/arm/include/asm/cpuidle.h | 30 ++++++++++++ arch/arm/kernel/Makefile | 2 +- arch/arm/kernel/cpuidle.c | 21 +++++++++ arch/arm/mach-at91/cpuidle.c | 67 ++++++++++----------------- arch/arm/mach-davinci/cpuidle.c | 82 +++++++++++++-------------------- arch/arm/mach-kirkwood/cpuidle.c | 72 +++++++++-------------------- arch/arm/mach-omap2/cpuidle34xx.c | 42 +++++++---------- arch/arm/mach-omap2/cpuidle44xx.c | 21 ++------- arch/arm/mach-shmobile/cpuidle.c | 31 +++---------- arch/sh/kernel/cpu/shmobile/cpuidle.c | 10 ++-- drivers/cpuidle/cpuidle.c | 66 +++++++++++++++++++++++--- include/linux/cpuidle.h | 13 +++++- 12 files changed, 231 insertions(+), 226 deletions(-) create mode 100644 arch/arm/include/asm/cpuidle.h create mode 100644 arch/arm/kernel/cpuidle.c -- 1.7.9.4

13 years, 3 months

ci.linaro.org planned downtime.

by James Tunnicliffe

Hi, It is my intention to take ci.linaro.org offline for about 15 minutes at 13:45 UTC (http://www.worldtimeserver.com/current_time_in_UTC.aspx) so we can duplicate the server and start moving it to a larger EC2 instance. Users will know that ci.linaro.org has been running very slowly for a while and we hope that this move will make it usable while we continue to debug the performance problems that we are seeing. If the downtime will cause you significant problems, please get in touch and we will arrange a better time. Thanks, -- James Tunnicliffe

13 years, 3 months

[PATCH] usb: gadget: s3c-hsotg: fix kernel panic

by Sangwook Lee

Fix kernel panic from s3c_hsotg_udc_stop. if udc_is_newstyle is true, s3c_hsotg_udc_stop should not call disconnect, unbind. As running rmmod g_mass_storage, kernel panic happens. (composite_unbind+0x14/0x164 [g_mass_storage]) from [<c023e950>] (s3c_hsotg_udc_stop) This patch is based on Lukasz Majewski's patches: [PATCH 0/9] USB: s3c-hsotg: USB S3C-HSOTG driver fixes and code cleanu in order to test g_mass_storage in Origen board: Signed-off-by: Sangwook Lee <sangwook.lee(a)linaro.org> --- drivers/usb/gadget/s3c-hsotg.c | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/usb/gadget/s3c-hsotg.c b/drivers/usb/gadget/s3c-hsotg.c index 4262df8..9925661 100644 --- a/drivers/usb/gadget/s3c-hsotg.c +++ b/drivers/usb/gadget/s3c-hsotg.c @@ -2883,16 +2883,12 @@ static int s3c_hsotg_udc_stop(struct usb_gadget *gadget, for (ep = 0; ep < hsotg->num_of_eps; ep++) s3c_hsotg_ep_disable(&hsotg->eps[ep].ep); - call_gadget(hsotg, disconnect); - - driver->unbind(&hsotg->gadget); s3c_hsotg_phy_disable(hsotg); regulator_bulk_disable(ARRAY_SIZE(hsotg->supplies), hsotg->supplies); hsotg->driver = NULL; hsotg->gadget.speed = USB_SPEED_UNKNOWN; - - device_del(&hsotg->gadget.dev); + hsotg->gadget.dev.driver = NULL; dev_info(hsotg->dev, "unregistered gadget driver '%s'\n", driver->driver.name); @@ -3526,7 +3522,10 @@ static int __devexit s3c_hsotg_remove(struct platform_device *pdev) s3c_hsotg_delete_debug(hsotg); - usb_gadget_unregister_driver(hsotg->driver); + if (hsotg->driver) { + /* should have been done already by driver model core */ + usb_gadget_unregister_driver(hsotg->driver); + } free_irq(hsotg->irq, hsotg); iounmap(hsotg->regs); @@ -3540,6 +3539,7 @@ static int __devexit s3c_hsotg_remove(struct platform_device *pdev) clk_disable(hsotg->clk); clk_put(hsotg->clk); + device_unregister(&hsotg->gadget.dev); kfree(hsotg); return 0; } -- 1.7.4.1

13 years, 3 months

Fwd: Re: Linux 2.6.35.3 Kernel for ARM and SATA problems

by Zygmunt Krynicki

Forwarding a post from debian-arm. I think I may be affected by this bug. Could anyone help me check if this still applies to 3.1.1-1400-linaro-lt-mx5. Best regards ZK ------ Wiadomość oryginalna ------ Temat: Re: Linux 2.6.35.3 Kernel for ARM and SATA problems Odesłano-Data: Tue, 20 Mar 2012 01:25:53 +0000 (UTC) Odesłano-Od: debian-arm(a)lists.debian.org Data: Mon, 19 Mar 2012 18:25:03 -0700 Nadawca: Mike Thompson <mpthompson(a)gmail.com> Adresat: Phil Endecott <spam_from_debian_arm(a)chezphil.org> Kopia: debian-arm(a)lists.debian.org On Sun, Mar 18, 2012 at 1:38 PM, Phil Endecott <spam_from_debian_arm(a)chezphil.org <mailto:spam_from_debian_arm@chezphil.org>> wrote: It works for me. I seem to recall a small amount of agro getting the kernel config right, but u-boot was always able to recognise the device. I suggest that you find (borrow) another SATA device to test with. Good luck! I was able to borrow another SATA drive and that works, thank heaven. I thought I was going crazy for a while -- don't ask how many times I re-compiled the kernel. I did trace the problems I having to the ahci code in the kernel not properly handling an ahci CONINIT event generated by my WD5000BEVT drive. Seems this drive has extra SATA features implemented so that it can be used in hot-plug arrays and these features aren't recognized by the kernel driver so it just seems to shut down the drive and ignore it. The other SATA drive that I do have working with the kernel doesn't implement the extra features so the kernel is happy. Presumably these problems were fixed in later kernels and the patches didn't make it into Freescales 2.6.35.3 branch. On the other hand, the kernel might be fine and the firmware in the drive isn't conforming to the ahci specs, but I think that wold cause problems with the drive on other systems. I'm going to keep looking into this as I do want to get my 500GB SATA drive working with the iMX53 Quick Start. Mike

13 years, 3 months

LAVA Downtime Planned

by Paul Larson

This is just an early notification that the Linaro validation farm will be physically moving to a new site next week. Unfortunately, the network cables won't stretch that far, so it will mean some downtime. :) Here's the tentative plan: Wednesday, March 21st - the rack with the toolchain server will be shut down, crated and sent off Thursday, March 22nd - pretty much everything else will go offline (main LAVA server, development boards) Friday, March 23rd - physical move will happen, and if all goes well (what could possibly go wrong?!) the main site and as many of the boards as possible will go back online in their new home Saturday, March 24th to Sunday, March 25th - finish configuring and bringing up cloud services, toolchain server, etc. There's another bit of good news here, that the lab will be getting a much needed upgrade in the internet connection. A partial (but significant one) at first, and a bigger one in about a month or so with redundant connections. Bear in mind that this is just the tentative plan, Dave or I will send out a reminder and update as the date gets closer, or if something changes. Thanks, Paul Larson

13 years, 3 months

Snowball V8 USB OTG broken

by adnan ali

Hi, I started working on snowball v8 development board to investigate usb otg. My initial effort didn't gave me any result. I started investigating otg driver it seems that it starts in idle mode and then update its status to peripheral mode based on line status. Which in this case should go into host mode as per cable Mini-A. I manually put the driver into host mode and using debug messages in driver. It started to detect memory stick being plugged in and plugged out but it wasn't appearing as block device. As AB8500 interface chip documentation for usb is not in public domain makes it nearly impossible to debug the driver further. As usb otg is bus power so only low power device can be used. Thanks Adnan

13 years, 3 months

Upcoming Dates for Android 12.03 Release

by Zach Pfeffer

Its that time of the month again. From, https://wiki.linaro.org/Cycles. Here's the plan: March 15th, Toolchain WG Release 2012.03 (Done) March 22nd, Kernel WG Freeze, WGs/LTs Release March 26th, Cut Android releases (Abhishek will select the last tip that boots to a UI) March 27th, QA Android releases March 29th, Release Linaro Android 12.03 If there is something you need to get in, please get it in now. If tips aren't booting please take a look now so we can stabilize things. We've had 2 RC this month. Take a look at the QA test sheets for the bootloader testing we've done. Origen: QA sheets: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDRDV… Snowball: QA Sheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadEF1N… iMX53/iMX6: QA Sheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadDE1M… Panda: (4430/4460) QA Sheet : https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadGVWd… Vexpress: QA Sheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AkxwyUNxNaAadExQd… -- 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

13 years, 3 months

Plan for changing the binary toolchain to 4.7 and hardfloat

by Michael Hope

Hi there. Over the next three months both GCC 4.7 and Ubuntu 12.04 'Precise' are coming out. We'll switch over to these pretty quickly which will affect our internal testing and anyone using the binary toolchain. The changeover plan including dates, details of what's happening, and backwards compatibility is at: https://wiki.linaro.org/MichaelHope/Sandbox/BinariesMigration Comments and concerns are welcome, -- Michael

13 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev