- linaro-kernel - lists.linaro.org

[ACTIVITY] (Deepak Saxena) March 25 - 31

by Deepak Saxena

== Deepak Saxena <dsaxena> == === Highlights === * Worked on article on "Kernel Upstreaming Challenges" for executive member update. Ended up writing one version and completely throwing it away as it was too introductory but hope to use that to write a larger white-paper type of document on the topic. Update article draft @ http://goo.gl/9SBpT. * Self-review, engineer review. (Do we really need to do these every 3-4 months?) * Worked with Mounir on 12.04 blueprint updates * Submitted talk proposal on "One zImage to Rule Them All" to LinuxCon Japan * Regular 1:1s and meetings === Plans === * Finish review cycle work * Finish patch tracking spreadsheet for upstream kernel work * Connect planning * Roadmap cards === Issues === * No major ones, though still feeling behind on everything due to being sick earlier in the month. :/ === Travel/Time Off === * Off May 4th and following week, back to work on Monday the 13th. Will have no interwebs and limited phone access. * Connect Q2, possibly with follow up

13 years, 2 months

2
1
0 0

[ACTIVITY] (Rajendra Nayak) Mar 19 - Mar 30

by Rajendra Nayak

== Rajendra Nayak <rnayak> == === Highlights === * Worked on patches to make OMAP transition to common clk one SoC family at a time and also maintaining git-bisect. Turned out much ugly than I initially thought. Shared the patches along with a few minor fixes with Mike. * Started working on optimizing (reducing) OMAP4 common clk data on top of Mikes' initial work. Mostly done manual cleanups for now. Need to update the autogen scripts. * Started validating OMAP5 common clk using Mikes' framework changes and autogen updates. === Plans === * Autogen updates for OMAP4 data, OMAP5 validation and fixes to framework changes. === Misc === * Planning to take off on 2,9,10 April due to some personal emergency travel.

13 years, 2 months

2
1
0 0

[ACTIVITY](John Stultz) Mar 26-30

by John Stultz

=== Highlights === * Sent out last bits of timekeeping changes for 3.4 & got them merged. * Spent a bit of time re-installing & reconfiguring my system environment per new internal policies: http://www.codinghorror.com/.a/6a0120a85dcdae970b016301e98de2970d-800wi * Sent out first pass at config fragment integration into the linaro kernel. Got some good feedback & patches from Tixy and Tushar. * Ran Android Subteam phone meeting & set up recurring phone meeting biweekly. * Reviewed Danial Walkers performance comparision between shm based and android logger based logging. Got into a longish discussion off-list discussion with him about Android's design requirements. Hopefully will see another iteration from Daniel. * At Tixy's prodding, contacted Dima to see about the earlysuspend removal in 3.3 and what fixes for the log flooding that caused are recommended. Got a quick response that they have a fix, and are looking to push it out soon. Tixy suggested a fix in the meantime. * Did a first pass fwd port of the Android 3.3 patch stack to 3.4. Messed up some of the mmc items and will likely have to try again. * Got a first pass at reworking the fadvise volatile code to store tree roots in a hash rather then bloat the address_space structure. It seems to be working, but I kind of don't believe it. === Plans === * More testing on fadvise volatile hash rework & send to lkml * Get all of Tushar's changes merged into the config fragment tree * Take another shot at fwd porting the Android tree to 3.4 === Issues === * NA

13 years, 2 months

1
0
0 0

[ACTIVITY] (Arnd Bergmann) March 19 - March 30th

by Arnd Bergmann

== Arnd Bergmann == === Highlights === * Merge window, part two: everything we had queued is now in mainline * Discussed swap on flash with a few people, sent out first proposal * Continued DT discussion for spear, kirkwood, shmobile === Plans === * more review for DT conversions * regression testing post merge window * getting my build server back running * dig out my CONFIG_NO_IOPORT patch set and get that into linux-next

13 years, 2 months

1
0
0 0

[ACTIVITY] (Venkatraman S) March 19 - March 30th

by Venkatraman S

== Venkatraman S svenkatr == == Highlights == * Sent out pull request for UFS and eMMC features for Linaro Kernel release * Coding up eMMC foreground HPI code. Sent a rough first cut to Storage folks. * Studies UFS implementation. Plan to abstract out the PCI specific part of driver files == Plans == * More HPI coding and do some stress tests * Test eMMC Power off notify with OMAP. == Misc == * Was on leave for 2 days

13 years, 2 months

1
0
0 0

[ACTIVITY] (Saugata Das) March 26th - March 30th

by Saugata Das

== Saugata Das sdas == === Activity Summary === * Tested cases for < 4KB sector and EFI partition, with native sector support patch (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-native-sector) * Power OFF notify patch submitted === Plans === * Work on context ID patch (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-context-id) * Submit a proposal on the implementation of large block size (https://blueprints.launchpad.net/linux-linaro/+spec/vfs-larger-than-4k-bloc…) === Issues === * None

13 years, 2 months

1
0
0 0

[ACTIVITY] (Linus Walleij) 2012-03-26 - 2012-03-30

by Linus Walleij

== Linus Walleij linusw == === Highlights === * Applied and pushed the DT patch from Stephen, effectively making it possible to create DT- based pinctrl drivers in the 3.5 release cycle for the kernel. * Attended the Embedded Systems Conference in San Jose and had a "platform perimeter" seminar, paper and slides available here: http://www.df.lth.se/~triad/papers/ESC-400Paper_Walleij.pdf http://www.df.lth.se/~triad/papers/ESC-400Slides_Walleij.pdf Apart from running the seminar I count this as education and competence building === Plans === * Easter vacation april 2-5th. expect next report on april 13th * Review incoming pinctrl patches. * Prepare to convert ux500 (gpio-nomadik) to pinctrl for the kernel 3.5 timeframe. * Attending the Embedded Systems Conference in San Jose 27th thru 30th of march. * Test the U9540 core patches on real hardware and rework as outlined by Arnd. * Test the PL08x patches on the Ericsson Research PB11MPCore and submit platform data for using pl08x DMA on that platform. * Look into other Ux500 stuff in need of mainlining... like - Ux500 clocks - the HWMON stuff. === Issues === * N/A Thanks, Linus Walleij

13 years, 2 months

1
0
0 0

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.

13 years, 2 months

1
0
0 0

[ACTIVITY] (Arnd Bergmann) Week of Mar 19

by Arnd Bergmann

=== Highlights === * Merge window, preparing and sending pull requests * Some coaching of DT ports (spear, kirkwood, lpc3xxx) === Plans for this week === * Second half of merge window

13 years, 2 months

1
0
0 0

[ACTIVITY] (Shawn Guo) Week of Mar 19

by Shawn Guo

=== Highlights === * Converting imx6 clock code to common clk. (80% done with the non-dt part) * Reviewed imx_v4_v5 common clk series from Sascha * Reviewed and acked Saravana's patch moving init fields from clk to clk_hw * Suggested Mike change clk API a bit to have parent rate passed into .round_rate and .set_rate, and he acked it. * Tested imx6 anatop regulator patch from Paul and report some little problem. Have to wait for solving the it before I can merge the imx6q dts change. * Reviewed snvs-rtc patch from Paul. It's far away from the good state. -- Regards, Shawn

13 years, 2 months

1
0
0 0

[ACTIVITY] (Linus Walleij) 2012-03-19 - 2012-03-28

by Linus Walleij

== Linus Walleij linusw == === Highlights === * Sent a pull request for pinctrl. Torvalds pulled in the patch queue for kernel 3.4 and even quipped about it, as pointed out to me by Nico, see commit 7fc86a7908a4e9eb2da4b6498f86193d113842d3: (*) What is it with all these Linuses these days? There's a Linus at google too. Some day I will get myself my own broadsword, and run around screaming "There can be only one". I used to be _special_ dammit. Snif. * Fixed up my own screwups trying to stabilize the PL011 serial driver. Extracted another PL011 patch from inside ST-Ericsson. * Looked at some regulator patches. * DT patches for pinctrl are floated by Stephen on the LKML. === Plans === * Review incoming pinctrl patches. * Prepare to convert ux500 (gpio-nomadik) to pinctrl for the kernel 3.5 timeframe. * Attending the Embedded Systems Conference in San Jose 27th thru 30th of march. * Easter vacation april 2-5th. * Test the U9540 core patches on real hardware and rework as outlined by Arnd. * Test the PL08x patches on the Ericsson Research PB11MPCore and submit platform data for using pl08x DMA on that platform. * Look into other Ux500 stuff in need of mainlining... like - Ux500 clocks - the HWMON stuff. === Issues === * Git real ill middle of last week so things got to a standstill and not much happened. Unplanned absence. Still recovering somewhat. Thanks, Linus Walleij

13 years, 2 months

1
0
0 0

[ACTIVITY] (Saugata Das) March 19th - March 23rd

by Saugata Das

== Saugata Das sdas == === Activity Summary === * mmc-util updated for native sector (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-native-sector) * Context ID patch rework ongoing * Worked on power OFF notify patch === Plans === * Work on context ID patch (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-context-id) * Work on specific test cases related to native sector support (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-native-sector) * Submit a proposal on the implementation of large block size (https://blueprints.launchpad.net/linux-linaro/+spec/vfs-larger-than-4k-bloc…) === Issues === * None

13 years, 2 months

1
0
0 0

[ACTIVITY] (John Stultz) Mar 19-23

by John Stultz

=== Highlights === * Got some feedback and sent out another iteration of the fadvise volatile work. * Implemented first pass at integrating config-fragments into the linaro kernel tree. * Sent out additional features to the merge_config.sh script to kconfig maintainer * Got Android Alarm driver and ramconsole rework pushed into 3.4 merge window via staging * Got other timekeeping changes merged into 3.4 merge window * Did an initial review of Anton's ulmkd code * Did some digging through my mail backlog, applying patches and sending out test fixes * Did rypple self evaluation === Plans === * Get first-pass radixtree fadvise volatile implementation working * Try to get a few more timekeeping changes merged for 3.4 === Issues === * NA

13 years, 2 months

1
0
0 0

[ACTIVITY] (Deepak Saxena) March 12 - March 23

by Deepak Saxena

== Deepak Saxena <dsaxena> == I was out sick for about a week, behind on everything right now. :/ === Highlights === * Started work on member's update article on understanding upstream kernel development. * Started work on patch tracking spreadsheet for Android lowmem-related patches as a POC for better understanding status of how upstream is doing. === Plans === * 1:1s * Complete member newsletter article * Complete patch tracking spreadsheet for Android lowmem patches * Review cycle work, including my own self-review * Put together proposed schedule for kernel training @ Connect. * Review roadmap card status * Review latest updates to KWG wiki pages. * Start thinking about KWG @ Linaro connect === Travel/Time Off === * Possibly off May 4-10th. * Connect Q2 * Possibly attending Linux Con Japan right after Connect

13 years, 2 months

2
1
0 0

[ACTIVITY] (Dong Aisheng) March 12-16

by Dong Aisheng

=== Pinctrl === * Pinctrl core patch review. * sent mx28 basic dt support patches including imx28 dt core, irq domain, fec, mmc, dma supports. * sent a dt core patch fixing the potential issue of of_device_is_availabe * sent a fec patches fixing the potential no phy found issue. * sent a net phylib patch fixing the length limitation of mii bus id * discussed a lot with Grant and Lathar on how to get mac address from dt which is a common issue on all imx platfroms. === Plan === * Review pinctrl core dt binding patches sent recently by Stephen Warren * mx6q pinctrl driver dt support * mx28 dt support patch comments addressing and more devices support

13 years, 2 months

2
4
0 0

[ACTIVITY] (Dong Aisheng) March 19-23

by Dong Aisheng

=== Pinctrl === * Review pinctrl core dt binding patches sent by Stephen Warren Reviewed and provided my ack for most of them. I guess it's close to be merged. Count on Linus. :) * mx28 dt support v2 patch. * mx6 pinctrl driver dt support (INPROGRESS) * convert mxs-dma driver to be platform independent since mx50 and mx6 also use it. === Plan === * Keep tracking pinctrl core dt binding patches * mx6q pinctrl driver dt support * mx28 dt support

13 years, 2 months

1
0
0 0

[ACTIVITY] (Anton Vorontsov) 2012-03-12 - 2012-03-16

by Anton Vorontsov

== Highlights == * Reviewed and merged a bunch of battery-tree related patches. Not actually Android-related work, but community; * Revised memory management fixes I've made during work on LMK kernel driver improvements. * Trying to wrap head around Android images/build process, and how to add a custom daemon; Familiarizing with Android's internal userland structure. -- Anton Vorontsov Email: cbouatmailru(a)gmail.com

13 years, 2 months

1
0
0 0

[ACTIVITY] (Anton Vorontsov) 2012-03-05 - 2012-03-09

by Anton Vorontsov

== Highlights == * Familiarized with Android NDK, this was needed to build and test ulmkd on a real Android setup; * Successfully built ulmkd w/ NDK, a few changes were needed since Android's libc is quite limited; * Reworked ulmkd makefile so that it is suitable for NDK; * Added shm backend and demo utility for the userspace LMK daemon; * Made a few bugfixes for the userspace LMK daemon; -- Anton Vorontsov Email: cbouatmailru(a)gmail.com

13 years, 2 months

1
0
0 0

[ACTIVITY] (Shawn Guo) Week of Mar 12

by Shawn Guo

=== Highlights === * Another 3 iterations of adding imx-sgtl5000 machine driver working with fsl_ssi. The v5 of the series just got merged by Mark. But unfortunately it does not catch v3.4 merge window, and will have to be in v3.5. * Tested DMA engine cookie handling cleanups from Russell King on imx-sdma and mxs-dma drivers. * Reviewed imx pwm framework migration patch from Sascha. * Reviewed a bit imx28 device tree support series from Aisheng. * Reviewed common clk framework v7 post. * Start porting imx6 clock driver to common clk framework -- Regards, Shawn

13 years, 2 months

2
2
0 0

[ACTIVITY] (Rajendra Nayak) Mar 12 - Mar 16

by Rajendra Nayak

== Rajendra Nayak <rnayak> == === Highlights === * Reposted v3 of mmc-dt patches. Chris pulled them in for 3.4. With this OMAP should have *all* basic drivers DT adapted. * More mmc driver cleanups, will post once 3.4-rc1 comes out. Too late and not too critical to go in this merge window. * Review pinctrl dt, and common clk patches. Also had a chat with Tony about the pinctrl dt bindings and he plans to update pinctrl- simple with the latest bindings quite soon. * After some discussions with Tony on moving the mmc pbias platform calls to SCM driver, it turns out he prefers it being handled in some way via the pinctrl driver. With mmc-dt patches already in 3.4 moving this task to a lower priority. * Started looking at Mike's *OMAP4 only* migration to common clock to get it working on all OMAPs'. Still figuring out if I can do this one OMAP family at a time, to avoid a big bang change across board. === Plans === * Focus mainly on common clk conversion for all OMAPs. === Misc === * Planing to take off the 1st week of May. From 1st to 7th May. Will update Linaro leaves.

13 years, 2 months

1
0
0 0

[ACTIVITY] (Thomas Abraham) 2012-03-12 - 2012-03-16

by Thomas Abraham

== Thomas Abraham <thomas-ab> == === Highlights === * Posted v2 of patches that rework platform data of display controller driver which is prerequisite for dt support. === Plans === * Post next version of dt support patches for interrupt combiner, wakeup interrupts, regulator and display controller driver. === Misc === * Was on leave on 14th, 15th and 16th March.

13 years, 2 months

1
0
0 0

[ACTIVITY] (Rajendra Nayak) Feb 27 - Mar 02

by Rajendra Nayak

== Rajendra Nayak <rnayak> == === Highlights === * Repost of twl regulator DT support clubbing all other changes to the same driver from Tero K and Peter U. Mark pulled patches into his -next. dts file changes pushed via Tony. * Review/testing of card detect for MMC cleanup patches from Tony. * System control module driver, adding MMC quirks needed for pbias, currently the driver resides in drivers/platform/arm/omap. Not sure whats the right place. More work needed for OMAP3 and OMAP2 support. * Continue work on System control module driver. * Start working on 'static data' cleanup for hwmod. === Misc === * Misc review/test of patches on linux-omap for IO daisy/CORE ret support and some hwmod fixes for keypad. === Plans === * Get all MMC cleanups in. * Continue work on System control module driver. * Start working on 'static data' cleanup for hwmod. === Misc === * None

13 years, 2 months

2
1
0 0

[ACTIVITY] (Linus Walleij) 2012-03-10 - 2012-03-18

by Linus Walleij

== Linus Walleij linusw == === Highlights === * Grant merged the SPI message queue core patch, also Mark Browns patch moving the Samsung SPI driver to use this central message queue. * Discussed dmaengine. This is pretty important, it looks like someone needs to step up and look into the channel mapping problem which is a pretty big piece of work. * Pushed out an interesting core driver patch that was harvested from Rabin inside ST-Ericsson. * Pushed out a new set of three MFD patches for AB8500 trying to keep things in sync. * Reviewed and ACK:ed a set of 7 device tree patches for ux500 by Lee Jones, now probably merged by Arnd. * Reviewed and ACK:ed the v7 clk patches from Mike Turquette. * Volunteered for the MMCI driver maintenanceship. Russell will keep it for now even though it's marked "orphaned" in MAINTAINERS. * Discussed a bit around ALSA SoC AB8500 codec implementation driven by Ola LILJA from ST-Ericsson. * Discussed some LED patches from Bryan Wu. === Plans === * Get ready to issue pull request for pinctrl this coming merge window. * Prepare to convert ux500 (gpio-nomadik) to pinctrl for the kernel 3.5 timeframe. * Attending the Embedded Systems Conference in San Jose 27th thru 30th of march. * Tentative easter vacation first week april. * Test the U9540 core patches on real hardware and rework as outlined by Arnd. * Test the PL08x patches on the Ericsson Research PB11MPCore and submit platform data for using pl08x DMA on that platform. * Look into other Ux500 stuff in need of mainlining... like - Ux500 clocks - the HWMON stuff. === Issues === * We really need someone to look at dmaengine for member SoCs. Thanks, Linus Walleij

13 years, 2 months

1
0
0 0

[ACTIVITY] (Saugata Das) March 12th - March 16

by Saugata Das

== Saugata Das sdas == === Activity Summary === * Supporting native sector patch prepared. Internal review ongoing The BP (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-native-sector) is updated * Context ID patch rework ongoing. Identifying mechanisms of extracting inode from the information passed to MMC layer === Plans === * Work on context ID patch (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-context-id) * Submit disable emulation mode patch to community * Follow up on power OFF notify patch for a fix on mmci driver * Submit a proposal on the implementation of large block size (https://blueprints.launchpad.net/linux-linaro/+spec/vfs-larger-than-4k-bloc…) === Issues === * None

13 years, 2 months

1
0
0 0

[ACTIVITY] (John Stultz) Mar 12-16

by John Stultz

=== Highlights === * Spent a large chunk of time on fadvise volatile work. Fixed circular locking issues and simplified things a bit. Polished up the code and submitted to lkml for review. Researching some alternative approaches. * Was alerted to a locking issue in the timekeeping code, sent an RFC fix to address the problem. * Iterated a few times on clocksource switching bug patches and sent a pull request for my current queue of fixes to tglx * Did some internal IBM assistance & internal IBM process items. * Was late, but sent out Android Subteam meeting email. === Plans === * Try to get a first pass at a page-tag approach to the volatile pages implementation. * Working on presentation abstract for plumbers === Issues === * Frustrated by my slow progress.

13 years, 2 months

1
0
0 0

[ACTIVITY] (Arnd Bergmann) March 12-16

by Arnd Bergmann

== Arnd Bergmann (arnd) == === Highlights === * Took over arm-soc merging from Olof again * accepted heaploads of patches into arm-soc, now closed * DT conversion for spear6xx, kirkwood, ux500, at91 * driver changes for davinci, lpc32xx, exynos * ep93xx cleanup * numerous smaller fixes * exynos5 Soc support * common struct clk * assisted DT conversion on a lot of platforms

13 years, 2 months

1
0
0 0

i2c support for samsung s5pv310 in u-boot

by Avinash H.M.

Hi Guys , I am working on a samsung sp5v310 development kit. I wanted to read a peripheral register (battery charger) in u-boot. This device is interfaced on i2c0. I am working with the u-boot in git://git.linaro.org/boot/u-boot-linaro-stable.git I wanted to do i2c_read in the code, but as i understand the i2c support is not there in u-boot for s5pv310 SOCs. Please confirm, if this is correct or i am wrong. If there is support to do i2c operations on s5pv310 SOCs, please point me to the right file, where i can find i2c configurations for s5pv310 SOCs. thanks, - Avinash PS: 1. There are no i2c macros in include/configs/smdkv310.h. 2. After adding,below macros to enable i2c support for smdkv310, /* I1C */ #define CONFIG_HARD_I2C 1 #define CONFIG_SYS_I2C_SPEED 100000 #define CONFIG_SYS_I2C_SLAVE 1 #define CONFIG_SYS_I2C_BUS 0 #define CONFIG_SYS_I2C_BUS_SELECT 1 #define CONFIG_I2C_MULTI_BUS 1 i get below error: /media/data/avinash/c.labs/ git.clones/bootloader/uboot/arch/arm/lib/board.c:189: undefined reference to `i2c_init' common/libcommon.o: In function `stdio_init': /media/data/avinash/c.labs/git.clones/bootloader/uboot/common/stdio.c:215: undefined reference to `i2c_init' And there are no i2c related support inside the u-boot for samsung smdkv310. avinash@avinash-desktop:/media/data/avinash/c.labs/git.clones/bootloader-new/uboot$ grep -inlr 'v310' . > v310.files.txt avinash@avinash-desktop:/media/data/avinash/c.labs/git.clones/bootloader-new/uboot$ cat v310.files.txt | xargs grep -inr 'i2c_init' Binary file ./uboot.PS matches avinash@avinash-desktop:/media/data/avinash/c.labs/git.clones/bootloader-new/uboot$

13 years, 2 months

1
1
0 0

[Activity] (Niklas Hernaeus) 2012-03-05 - 2012-03-09

by Niklas Hernaeus

== Niklas Hernaeus <nhe> == === General activity === * DT-work started on the RTC, PL031. * Due to non-synchronization among us, some work has been duplicated. * A google document is now used for synchronization and status. * There seem to be no patches ready for PL180, Saugata Das is probably assigned (?). * Arnd helped out with an integration of my previous patch and Lee's patches. Thanks. * There is now a working DT environment for Snowball. Work continues with new drivers.

13 years, 2 months

1
0
0 0

[ACTIVITY] (Rajendra Nayak) Mar 5 - Mar 9

by Rajendra Nayak

== Rajendra Nayak <rnayak> == === Highlights === * mmc platform callback cleanups posted. Ground work before these callbacks get moved into a system control module driver. * More mmc driver general cleanups while working on DT. * mmc dt series v2 with minor comments from Grant. Found an issue with the previous series which seemed to work only with MMC_DEBUG enabled. Issue root caused to OMAP4 controllers needing a special reset mechanism. * Worked some more on the system control module driver adding support for omap2 and omap3. The SCM driver is still limited to adding only mmc functionality. === Plans === * Get mmc-dt patches merged. * Post all mmc driver cleanups accumulated. * Make System control module driver work with multiple SCM hmwod instances added (latest series from Paul W) === Misc === * None

13 years, 2 months

1
0
0 0

[ACTIVITY] (svenkatr) 2012-03-05--2012-03-09

by Venkatraman S

== Venkatraman S <svenkatr> == == Highlights == * Code review / testing for various omap MMC patches * Developing abort request for sending eMMC HPI (High Priority Interrupt) * Attended Discussions about HPI timing and compliance == Plans == * Continue working on eMMC HPI / BKOPS * Study UFS & Unipro specifications

13 years, 2 months

1
0
0 0

ACTIVITY] (John Stultz) Mar 5-9

by john stultz

=== Highlights === * Reviewed the current android common/android-3.3 branch and pulled out updates to the already upstream items in staging, and submitted them to Greg for staging-next, so they'll be ready when the 3.4 window opens soon. These efforts got some positive press here: http://www.phoronix.com/scan.php?page=news_item&px=MTA2ODA * Discussed androidization topic branch for Andrey's linaro linux kernel. Sent the current AOSP 3.3 branch to Andrey for the 12.3 release. * Reworked my range-tree code for fadvise volatile to use a rbtree for better balancing & to simplify the code. Also spent time trying to work out dual-list locking issues. * Got pulled into some community timekeeping bug reports, I've tried, but haven't been able to reproduce yet. * Verified PaulW's omap resume fix patch * Got pulled into a sched_clock issue. Reviewed and acked a fix on lkml. * Updated my rtc, timekeeping and clocksource queues for 3.4. === Plans === * Continue implementing solution to fadvise volatile dual-list locking issue * Likely a few other timekeeping issues & trying to make sure everything I have pending for 3.4 is queued upstream. === Issues === * NA

13 years, 2 months

1
0
0 0

[ACTIVITY] (Arnd Bergmann) 2012-03-03 - 2012-03-09

by Arnd Bergmann

== Arnd Bergmann <arnd> == === Highlights === * Merged tons of patches into the arm-soc tree, then handed over to Olof for the meantime but will probably take over again for the merge window * Sent out status of the arm-soc tree report for the 3.4 merge window * Worked with Jason Cooper to get Kirkwood DT conversion started * Worked with Roland Stigge to get him established as lpc32xx maintainer and get his code for that platform in, he will work on lpc32xx DT stuff in the v3.5 cycle. * Worked with Alan Ott and Mathieu Poirier to start getting my randconfig patches merged. * Worked with Niklas Hernaeus and Lee Jones to speed up the ux500 DT conversion. * Code review: pxa/mmp DT patches, bmp085 driver, at91, dreamplug, ... === Plans === * Keep watching over various DT conversions * Dig out my old series for inb/outb elimination and get that into shape for -next after the merge window

13 years, 3 months

1
0
0 0

[ACTIVITY] (Linus Walleij) 2012-03-03 - 2012-03-09

by Linus Walleij

== Linus Walleij linusw == === Highlights === * Merged pin control patches from Stephen Warren, finalizing the API transition. * Sent a patch series converting U300 over to using pin control. * Updated pinctrl blueprints, created work for myself by opening a ux500 pinctrl transition blueprint. * Sent some AB8500 updates including AB8505 support to Sam for MFD. * Looking over some other internal patches, particularly patches touching the core kernel outside our own drivers, posting a cpufreq-ondemand patch today. * Discussed dmaengine. * Discussed internal alignment of Linaro activities for two issues as requested by Andrea. === Plans === * Test the U9540 patches on real hardware and rework as outlined by Arnd. * Accumulate pinctrl patches for kernel v3.4 merge window. * Work on the blueprint for ux500 pinctrl. * Test the PL08x patches on the Ericsson Research PB11MPCore and submit platform data for using pl08x DMA on that platform. * Look into other Ux500 stuff in need of mainlining... like - Ux500 clocks - the HWMON stuff. === Issues === * None! Thanks, Linus Walleij

13 years, 3 months

1
0
0 0

[RFC] Scheduler recorder and playback

by Pantelis Antoniou

Hi there, There's considerable activity in the subject of the scheduler lately and how to adapt it to the peculiarities of the new class of hardware coming out lately, like the big.LITTLE class of devices from a number of manufacturers. The platforms that Linux runs are very diverse, and run differing workloads. For example most consumer devices will very likely run something like Android, with common use cases such as audio and/or video playback. Methods to achieve lower power consumption using a power aware scheduler are under investigation. Similarly for server applications, or VM hosting, the behavior of the scheduler shouldn't have adverse performance implications; any power saving on top of that would be a welcome improvement. The current issue is that scheduler development is not easily shared between developers. Each developer has their own 'itch', be it Android use cases, server workloads, VM, etc. The risk is high of optimizing for one's own use case and causing severe degradation on most other use cases. One way to fix this problem would be the development of a method with which one could perform a given use-case workload in a host, record the activity in a interchangeable portable trace format file, and then play it back on another host via a playback application that will generate an approximately similar load which was observed during recording. The way that the two hosts respond under the same load generated by the playback application can be compared, so that the performance of the two scheduler implementations measured in various metrics (like performance, power consumption etc.) can be evaluated. The fidelity of the this approximation is of great importance but it is debatable if it is possible to have a fully identical load generated, since details of the hosts might differ in such a way that such a thing is impossible. I believe that it should be possible at least to simulate a purely CPU load, and the blocking behavior of tasks, in such a way that it would result in scheduler decisions that can be compared and shared among developers. The recording part I believe can be handled by the kernel's tracing infrastructure, either by using the existing tracepoints, or need be adding more; possibly even creating a new tracer solely for this purpose. Since some applications can adapt their behavior according to insufficient system resources (think media players that can drop frames for example), I think it would be beneficial to record such events to the same trace file. The trace file should have a portable format so that it can be freely shared between developers. An ASCII format like we currently use should be OK, as long as it doesn't cause too much of an effect during execution of the recording. The playback application can be implemented via two ways. One way, which is the LinSched way would be to have the full scheduler implementation compiled as part of said application, and use application specific methods to evaluate performance. While this will work, it won't allow comparison of the two hosts in a meaningful manner. For both scheduler and platform evaluation, the playback application will generate the load on the running host by simulating the source host's recorded work load session. That means emulating process activity like forks, thread spawning, blocking on resources etc. It is not clear to me yet if that's possible without using some kind of kernel level helper module, but not requiring such is desirable. Since one would have the full trace of scheduling activity: past, present and future; there would be the possibility of generating a perfect schedule (as defined by best performance, or best power consumption), and use it as a yardstick of evaluation against the actual scheduler. Comparing the results, you would get an estimate of the best case improvement that could be achieved if the ideal scheduler existed. I know this is a bit long, but I hope this can be a basis of thinking on how to go about developing this. Regards -- Pantelis

13 years, 3 months

4
6
0 0

[ACTIVITY] (Anton Vorontsov) 2012-02-27 - 2012-03-02

by Anton Vorontsov

== Highlights == * Debugged cgroups inaccuracy when calculating memory usage, prepared a hack that fixes the issue, sent an RFC. A proper fix needs to be implemented though; * Reviewing/comparing various low memory notifications: the one from Minchan Kim (http://lwn.net/Articles/475791/), Nokia's memory meter (http://lkml.org/lkml/2012/1/4/208) and vmevent (http://lkml.org/lkml/2012/1/17/370). Feature and reception-wise VM event framework looks like a winner; * Tried vmevents notifications framework, prepared a few fixes; * Added two-way notifications to vmevents; * Added vmevents support for the ulmkd. -- Anton Vorontsov Email: cbouatmailru(a)gmail.com

13 years, 3 months

1
0
0 0

What is bug of OMAP4460 that make oprofile can not run normally

by Kyler Zhang

Hi all, We are know that the OMAP4460's PMU is buggy, which loses PMU interrupt always. But I do not know what the real bug is, the HW bug or Software bug? What the bug is? Could some one give a point? Kyler Zhang

13 years, 3 months

3
2
0 0

[ACTIVITY] (Deepak Saxena) Feb 26 - Mar 3

by Deepak Saxena

== Deepak Saxena <dsaxena> == === Highlights === * Lots of catching up on emails from pre-ELC * 1-on-1's * Discussions on kernel upstreaming and roadmap process * Review of big.LITTLE Task Migration test plan === Plans === * Work on kernel wiki page updates * 1-on-1's, sub-team meetings * Working on roadmap cards * Start outline of porting guide that was discussed @ Connect * Continue looking at kernel upstreaming and roadmap process * Start outline of member's update on how kernel development process differs from traditional software development. * Dive deeper into big.LITTLE switcher project === Issues === *** I have lost all wiki access permissions (can't edit or create pages, *** *** can't acces /Internal). RT ticket filed last week but no progress. *** === Travel/Time Off === * Taking Monday March 12th mostly off, might be online parts of the day * Possible off May 4-10th. * Connect Q2

13 years, 3 months

1
0
0 0

re: What is bug of OMAP4460 that make oprofile can not run normally

by David Long

>Hi all, >We are know that the OMAP4460's PMU is buggy, which loses PMU interrupt always. >But I do not know what the real bug is, the HW bug or Software bug? >What the bug is? Kyler, This is a hardware problem in the ARM core. It is not specific to the 4460, for instance it also occurs in the 4430 (and presumably non-TI SoCs). The result of this bug is that PMU counter overflow interrupts are sometimes lost. The affect can be reduced by paralleling PMU counters, but this only reduces the problem statistically somewhat. There is no complete workaround. The problem is described in ARM errata, but I do not believe that information is generally available. I think it can be found on a Freescale site though. I suggest googling for ARM errata 628216. I believe this will be fixed in a future iteration of the design, but I do not know when this will be released. -dl David Long Linaro

13 years, 3 months

1
0
0 0

[ACTIVITY] (Shawn Guo) Week of Feb 27

by Shawn Guo

=== Device Tree === * Sent the full series (20 patches) adding DT support for IMX audio. - Covert audmux driver to a platform driver and move it into ASoC - Consolidate PowerPC SSI driver and make it work for IMX - Add imx-sgtl5000 machine driver (DT only) === Misc === * Reviewed ANATOP MFD and Regulator series (v7) from Paul Liu -- Regards, Shawn

13 years, 3 months

1
0
0 0

[Activity] (Niklas Hernaeus) 2012-02-27 - 2012-03-02

by Niklas Hernaeus

== Niklas Hernaeus <nhe> == === General activity === * Made the initial DT system to build and boot reliably. * Sent out a patch for this initial DT system. /nhe

13 years, 3 months

2
1
0 0

[PATCH 3/3] vmevent: Should not grab mutex in the atomic context

by Anton Vorontsov

There is not need to grab mutex in the atomic context, moreover this is wrong and causes the following bug: BUG: sleeping function called from invalid context at kernel/mutex.c:271 in_atomic(): 1, irqs_disabled(): 1, pid: 1056, name: m no locks held by m/1056. irq event stamp: 58768 hardirqs last enabled at (58767): [<ffffffff8101ca35>] do_page_fault+0x275/0x450 hardirqs last disabled at (58768): [<ffffffff81325a2b>] apic_timer_interrupt+0x6b/0x80 softirqs last enabled at (58676): [<ffffffff81038def>] __do_softirq+0x10f/0x160 softirqs last disabled at (58671): [<ffffffff813262ac>] call_softirq+0x1c/0x26 Pid: 1056, comm: m Not tainted 3.2.0+ #3 Call Trace: <IRQ> [<ffffffff81062530>] ? print_irqtrace_events+0xd0/0xe0 [<ffffffff8102f5da>] __might_sleep+0x12a/0x1e0 [<ffffffff81321dbc>] mutex_lock_nested+0x3c/0x340 [<ffffffff81053a8c>] ? __run_hrtimer+0x4c/0x100 [<ffffffff810bd920>] ? vmevent_read+0x100/0x100 [<ffffffff810bd79e>] vmevent_sample+0x6e/0xf0 [<ffffffff810bd946>] vmevent_timer_fn+0x26/0x60 [<ffffffff81053a92>] __run_hrtimer+0x52/0x100 [<ffffffff81054463>] hrtimer_interrupt+0xf3/0x220 [<ffffffff810166d4>] smp_apic_timer_interrupt+0x64/0xa0 [<ffffffff81325a30>] apic_timer_interrupt+0x70/0x80 <EOI> [<ffffffff8101ca3a>] ? do_page_fault+0x27a/0x450 [<ffffffff8101ca35>] ? do_page_fault+0x275/0x450 [<ffffffff810036bf>] ? do_softirq+0x6f/0xc0 [<ffffffff8132485d>] ? retint_restore_args+0xe/0xe [<ffffffff8132484a>] ? retint_swapgs+0xe/0x13 [<ffffffff8116b31d>] ? trace_hardirqs_off_thunk+0x3a/0x3c [<ffffffff81324a3f>] page_fault+0x1f/0x30 Signed-off-by: Anton Vorontsov <anton.vorontsov(a)linaro.org> --- The patch is for git://github.com/penberg/linux.git vmevent/core. mm/vmevent.c | 4 ---- 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/mm/vmevent.c b/mm/vmevent.c index 1375f9d..1dbefb5 100644 --- a/mm/vmevent.c +++ b/mm/vmevent.c @@ -71,8 +71,6 @@ static void vmevent_sample(struct vmevent_watch *watch) if (!vmevent_match(watch, &event)) return; - mutex_lock(&watch->mutex); - watch->pending = true; if (watch->config.event_attrs & VMEVENT_EATTR_NR_AVAIL_PAGES) @@ -85,8 +83,6 @@ static void vmevent_sample(struct vmevent_watch *watch) watch->attr_values[n++] = event.nr_swap_pages; watch->nr_attrs = n; - - mutex_unlock(&watch->mutex); } static enum hrtimer_restart vmevent_timer_fn(struct hrtimer *hrtimer) -- 1.7.7.6

13 years, 3 months

2
1
0 0

[PATCH 2/3] vmevent: Fix deadlock when using si_meminfo()

by Anton Vorontsov

si_meminfo() calls nr_blockdev_pages() that grabs bdev_lock, but it is not safe to grab the lock from the hardirq context (the lock is never taken with an _irqsave variant in block_dev.c). When taken from an inappropriate context it easily causes the following deadlock: - - - - ================================= [ INFO: inconsistent lock state ] 3.2.0+ #1 --------------------------------- inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage. swapper/0/0 [HC1[1]:SC0[0]:HE0:SE1] takes: (bdev_lock){?.+...}, at: [<ffffffff810f1017>] nr_blockdev_pages+0x17/0x70 {HARDIRQ-ON-W} state was registered at: [<ffffffff81061b20>] mark_irqflags+0x140/0x1b0 [<ffffffff81062f03>] __lock_acquire+0x4c3/0x9c0 [<ffffffff810639c6>] lock_acquire+0x96/0xc0 [<ffffffff8131c58c>] _raw_spin_lock+0x2c/0x40 [<ffffffff810f1017>] nr_blockdev_pages+0x17/0x70 [<ffffffff81089ba8>] si_meminfo+0x38/0x60 [<ffffffff81675493>] eventpoll_init+0x11/0xa1 [<ffffffff8165eb40>] do_one_initcall+0x7a/0x12e [<ffffffff8165ec8e>] kernel_init+0x9a/0x114 [<ffffffff8131e934>] kernel_thread_helper+0x4/0x10 irq event stamp: 135250 hardirqs last enabled at (135247): [<ffffffff81009897>] default_idle+0x27/0x50 hardirqs last disabled at (135248): [<ffffffff8131e1ab>] apic_timer_interrupt+0x6b/0x80 softirqs last enabled at (135250): [<ffffffff8103814e>] _local_bh_enable+0xe/0x10 softirqs last disabled at (135249): [<ffffffff81038665>] irq_enter+0x65/0x80 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(bdev_lock); <Interrupt> lock(bdev_lock); *** DEADLOCK *** no locks held by swapper/0/0. - - - - The patch fixes the issue by using totalram_pages instead of si_meminfo(). p.s. Note that VMEVENT_EATTR_NR_SWAP_PAGES type calls si_swapinfo(), which has a very similar problem. But there is no easy way to fix it. Do we have any use case for the VMEVENT_EATTR_NR_SWAP_PAGES event? If not, I'd vote for removing it and thus keeping things simple. Otherwise we would have two options: 1. Modify swap accounting for vmevent (either start grabbing _irqsave variant of swapfile.c's swap_lock, or try to make the accounting atomic); 2. Start using kthreads for vmevent_sample(). Signed-off-by: Anton Vorontsov <anton.vorontsov(a)linaro.org> --- The patch is for git://github.com/penberg/linux.git vmevent/core. mm/vmevent.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/mm/vmevent.c b/mm/vmevent.c index 2342752..1375f9d 100644 --- a/mm/vmevent.c +++ b/mm/vmevent.c @@ -51,18 +51,18 @@ static bool vmevent_match(struct vmevent_watch *watch, static void vmevent_sample(struct vmevent_watch *watch) { struct vmevent_watch_event event; - struct sysinfo si; int n = 0; memset(&event, 0, sizeof(event)); event.nr_free_pages = global_page_state(NR_FREE_PAGES); - si_meminfo(&si); - event.nr_avail_pages = si.totalram; + event.nr_avail_pages = totalram_pages; #ifdef CONFIG_SWAP if (watch->config.event_attrs & VMEVENT_EATTR_NR_SWAP_PAGES) { + struct sysinfo si; + si_swapinfo(&si); event.nr_swap_pages = si.totalswap; } -- 1.7.7.6

13 years, 3 months

2
1
0 0

[PATCH 1/3] vmevent: Fix build for SWAP=n case

by Anton Vorontsov

Caught this build failure: CC mm/vmevent.o mm/vmevent.c:17:6: error: expected identifier or '(' before numeric constant mm/vmevent.c:18:1: warning: no semicolon at end of struct or union [enabled by default] mm/vmevent.c: In function 'vmevent_sample': mm/vmevent.c:84:36: error: expected identifier before numeric constant make[1]: *** [mm/vmevent.o] Error 1 make: *** [mm/] Error 2 This is because linux/swap.h defines nr_swap_pages to 0L, and so things break. Fix this by undefinding it back, as we don't use it anyway. Signed-off-by: Anton Vorontsov <anton.vorontsov(a)linaro.org> --- The patch is for git://github.com/penberg/linux.git vmevent/core. mm/vmevent.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/mm/vmevent.c b/mm/vmevent.c index 37d2c5f..2342752 100644 --- a/mm/vmevent.c +++ b/mm/vmevent.c @@ -6,6 +6,7 @@ #include <linux/poll.h> #include <linux/slab.h> #include <linux/swap.h> +#undef nr_swap_pages /* This is defined to a constant for SWAP=n case */ #define VMEVENT_MAX_FREE_THRESHOD 100 -- 1.7.7.6

13 years, 3 months

2
1
0 0

[PATCH] Initial Device Tree system for Snowball

by Niklas Hernaeus

From: Niklas Hernaeus <niklas.hernaeus(a)linaro.org> This is the base system for using Device Tree for Snowball. The new boardfile is a slightly modified copy of the original board file, so new Device Tree stuff can simply be added and code removed, while functionality stays the same. Signed-off-by: Niklas Hernaeus <niklas.hernaeus(a)linaro.org> --- arch/arm/boot/dts/snowball.dts | 32 ++ arch/arm/mach-ux500/Kconfig | 17 +- arch/arm/mach-ux500/Makefile | 5 +- arch/arm/mach-ux500/board-mop500-dt.c | 729 +++++++++++++++++++++++++++++++ arch/arm/mach-ux500/include/mach/irqs.h | 2 +- 5 files changed, 779 insertions(+), 6 deletions(-) create mode 100644 arch/arm/boot/dts/snowball.dts create mode 100644 arch/arm/mach-ux500/board-mop500-dt.c diff --git a/arch/arm/boot/dts/snowball.dts b/arch/arm/boot/dts/snowball.dts new file mode 100644 index 0000000..02305fb --- /dev/null +++ b/arch/arm/boot/dts/snowball.dts @@ -0,0 +1,32 @@ +/* + * Copyright 2011 ST-Ericsson AB + * + * The code contained herein is licensed under the GNU General Public + * License. You may obtain a copy of the GNU General Public License + * Version 2 or later at the following locations: + * + * http://www.opensource.org/licenses/gpl-license.html + * http://www.gnu.org/copyleft/gpl.html + */ + +/dts-v1/; + +/ { + model = "Calao Systems Snowball platform with device tree"; + compatible = "calaosystems,snowball-a9500"; + + #address-cells = <1>; + #size-cells = <1>; + + memory { + device_type = "memory"; + reg = <0x00000000 0x20000000>; + }; + + soc-u9500 { + #address-cells = <1>; + #size-cells = <1>; + compatible = "simple-bus"; + ranges; + }; +}; diff --git a/arch/arm/mach-ux500/Kconfig b/arch/arm/mach-ux500/Kconfig index 52af004..be7e4fe 100644 --- a/arch/arm/mach-ux500/Kconfig +++ b/arch/arm/mach-ux500/Kconfig @@ -27,19 +27,22 @@ menu "Ux500 target platform (boards)" config MACH_U8500 bool "U8500 Development platform" depends on UX500_SOC_DB8500 + depends on !USE_OF select TPS6105X help Include support for the mop500 development platform. config MACH_HREFV60 - bool "U85000 Development platform, HREFv60 version" - depends on UX500_SOC_DB8500 - help - Include support for the HREFv60 new development platform. + bool "U85000 Development platform, HREFv60 version" + depends on UX500_SOC_DB8500 + depends on !USE_OF + help + Include support for the HREFv60 new development platform. config MACH_SNOWBALL bool "U8500 Snowball platform" depends on UX500_SOC_DB8500 + depends on !USE_OF select MACH_U8500 help Include support for the snowball development platform. @@ -49,6 +52,12 @@ config MACH_U5500 depends on UX500_SOC_DB5500 help Include support for the U5500 development platform. +config MACH_UX500_DT + def_bool y if USE_OF + depends on UX500_SOC_DB8500 || UX500_SOC_DB5500 + +config MACH_MOP500 + def_bool y if MACH_U8500 || MACH_UX500_DT endmenu config UX500_DEBUG_UART diff --git a/arch/arm/mach-ux500/Makefile b/arch/arm/mach-ux500/Makefile index 6bd2f45..05bee25 100644 --- a/arch/arm/mach-ux500/Makefile +++ b/arch/arm/mach-ux500/Makefile @@ -7,7 +7,10 @@ obj-y := clock.o cpu.o devices.o devices-common.o \ obj-$(CONFIG_CACHE_L2X0) += cache-l2x0.o obj-$(CONFIG_UX500_SOC_DB5500) += cpu-db5500.o dma-db5500.o obj-$(CONFIG_UX500_SOC_DB8500) += cpu-db8500.o devices-db8500.o -obj-$(CONFIG_MACH_U8500) += board-mop500.o board-mop500-sdi.o \ + +obj-$(CONFIG_MACH_UX500_DT) += board-mop500-dt.o +obj-$(CONFIG_MACH_U8500) += board-mop500.o +obj-$(CONFIG_MACH_MOP500) += board-mop500-sdi.o \ board-mop500-regulators.o \ board-mop500-uib.o board-mop500-stuib.o \ board-mop500-u8500uib.o \ diff --git a/arch/arm/mach-ux500/board-mop500-dt.c b/arch/arm/mach-ux500/board-mop500-dt.c new file mode 100644 index 0000000..33f4a83 --- /dev/null +++ b/arch/arm/mach-ux500/board-mop500-dt.c @@ -0,0 +1,729 @@ +/* + * Copyright (C) 2008-2009 ST-Ericsson + * + * Author: Srinidhi KASAGAR <srinidhi.kasagar(a)stericsson.com> + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2, as + * published by the Free Software Foundation. + * + */ +#include <linux/kernel.h> +#include <linux/init.h> +#include <linux/interrupt.h> +#include <linux/platform_device.h> +#include <linux/io.h> +#include <linux/i2c.h> +#include <linux/gpio.h> +#include <linux/amba/bus.h> +#include <linux/amba/pl022.h> +#include <linux/amba/serial.h> +#include <linux/spi/spi.h> +#include <linux/mfd/abx500/ab8500.h> +#include <linux/regulator/ab8500.h> +#include <linux/mfd/tc3589x.h> +#include <linux/mfd/tps6105x.h> +#include <linux/mfd/abx500/ab8500-gpio.h> +#include <linux/leds-lp5521.h> +#include <linux/input.h> +#include <linux/smsc911x.h> +#include <linux/gpio_keys.h> +#include <linux/delay.h> + +#include <linux/of.h> +#include <linux/of_platform.h> + +#include <linux/leds.h> +#include <asm/mach-types.h> +#include <asm/mach/arch.h> +#include <asm/hardware/gic.h> + +#include <plat/i2c.h> +#include <plat/ste_dma40.h> +#include <plat/pincfg.h> +#include <plat/gpio-nomadik.h> + +#include <mach/hardware.h> +#include <mach/setup.h> +#include <mach/devices.h> +#include <mach/irqs.h> + +#include "pins-db8500.h" +#include "ste-dma40-db8500.h" +#include "devices-db8500.h" +#include "board-mop500.h" +#include "board-mop500-regulators.h" + +static struct gpio_led snowball_led_array[] = { + { + .name = "user_led", + .default_trigger = "none", + .gpio = 142, + }, +}; + +static struct gpio_led_platform_data snowball_led_data = { + .leds = snowball_led_array, + .num_leds = ARRAY_SIZE(snowball_led_array), +}; + +static struct platform_device snowball_led_dev = { + .name = "leds-gpio", + .dev = { + .platform_data = &snowball_led_data, + }, +}; + +static struct ab8500_gpio_platform_data ab8500_gpio_pdata = { + .gpio_base = MOP500_AB8500_GPIO(0), + .irq_base = MOP500_AB8500_VIR_GPIO_IRQ_BASE, + /* config_reg is the initial configuration of ab8500 pins. + * The pins can be configured as GPIO or alt functions based + * on value present in GpioSel1 to GpioSel6 and AlternatFunction + * register. This is the array of 7 configuration settings. + * One has to compile time decide these settings. Below is the + * explanation of these setting + * GpioSel1 = 0x00 => Pins GPIO1 to GPIO8 are not used as GPIO + * GpioSel2 = 0x1E => Pins GPIO10 to GPIO13 are configured as GPIO + * GpioSel3 = 0x80 => Pin GPIO24 is configured as GPIO + * GpioSel4 = 0x01 => Pin GPIo25 is configured as GPIO + * GpioSel5 = 0x7A => Pins GPIO34, GPIO36 to GPIO39 are conf as GPIO + * GpioSel6 = 0x00 => Pins GPIO41 & GPIo42 are not configured as GPIO + * AlternaFunction = 0x00 => If Pins GPIO10 to 13 are not configured + * as GPIO then this register selectes the alternate fucntions + */ + .config_reg = {0x00, 0x1E, 0x80, 0x01, + 0x7A, 0x00, 0x00}, +}; + +static struct gpio_keys_button snowball_key_array[] = { + { + .gpio = 32, + .type = EV_KEY, + .code = KEY_1, + .desc = "userpb", + .active_low = 1, + .debounce_interval = 50, + .wakeup = 1, + }, + { + .gpio = 151, + .type = EV_KEY, + .code = KEY_2, + .desc = "extkb1", + .active_low = 1, + .debounce_interval = 50, + .wakeup = 1, + }, + { + .gpio = 152, + .type = EV_KEY, + .code = KEY_3, + .desc = "extkb2", + .active_low = 1, + .debounce_interval = 50, + .wakeup = 1, + }, + { + .gpio = 161, + .type = EV_KEY, + .code = KEY_4, + .desc = "extkb3", + .active_low = 1, + .debounce_interval = 50, + .wakeup = 1, + }, + { + .gpio = 162, + .type = EV_KEY, + .code = KEY_5, + .desc = "extkb4", + .active_low = 1, + .debounce_interval = 50, + .wakeup = 1, + }, +}; + +static struct gpio_keys_platform_data snowball_key_data = { + .buttons = snowball_key_array, + .nbuttons = ARRAY_SIZE(snowball_key_array), +}; + +static struct platform_device snowball_key_dev = { + .name = "gpio-keys", + .id = -1, + .dev = { + .platform_data = &snowball_key_data, + } +}; + +static struct smsc911x_platform_config snowball_sbnet_cfg = { + .irq_polarity = SMSC911X_IRQ_POLARITY_ACTIVE_HIGH, + .irq_type = SMSC911X_IRQ_TYPE_PUSH_PULL, + .flags = SMSC911X_USE_16BIT | SMSC911X_FORCE_INTERNAL_PHY, + .shift = 1, +}; + +static struct resource sbnet_res[] = { + { + .name = "smsc911x-memory", + .start = (0x5000 << 16), + .end = (0x5000 << 16) + 0xffff, + .flags = IORESOURCE_MEM, + }, + { + .start = NOMADIK_GPIO_TO_IRQ(140), + .end = NOMADIK_GPIO_TO_IRQ(140), + .flags = IORESOURCE_IRQ | IORESOURCE_IRQ_HIGHEDGE, + }, +}; + +static struct platform_device snowball_sbnet_dev = { + .name = "smsc911x", + .num_resources = ARRAY_SIZE(sbnet_res), + .resource = sbnet_res, + .dev = { + .platform_data = &snowball_sbnet_cfg, + }, +}; + +static struct ab8500_platform_data ab8500_platdata = { + .irq_base = MOP500_AB8500_IRQ_BASE, + .regulator_reg_init = ab8500_regulator_reg_init, + .num_regulator_reg_init = ARRAY_SIZE(ab8500_regulator_reg_init), + .regulator = ab8500_regulators, + .num_regulator = ARRAY_SIZE(ab8500_regulators), + .gpio = &ab8500_gpio_pdata, +}; + +static struct resource ab8500_resources[] = { + [0] = { + .start = IRQ_DB8500_AB8500, + .end = IRQ_DB8500_AB8500, + .flags = IORESOURCE_IRQ + } +}; + +struct platform_device ab8500_device = { + .name = "ab8500-i2c", + .id = 0, + .dev = { + .platform_data = &ab8500_platdata, + }, + .num_resources = 1, + .resource = ab8500_resources, +}; + +/* + * TPS61052 + */ + +static struct tps6105x_platform_data mop500_tps61052_data = { + .mode = TPS6105X_MODE_VOLTAGE, + .regulator_data = &tps61052_regulator, +}; + +/* + * TC35892 + */ + +static void mop500_tc35892_init(struct tc3589x *tc3589x, unsigned int base) +{ + mop500_sdi_tc35892_init(); +} + +static struct tc3589x_gpio_platform_data mop500_tc35892_gpio_data = { + .gpio_base = MOP500_EGPIO(0), + .setup = mop500_tc35892_init, +}; + +static struct tc3589x_platform_data mop500_tc35892_data = { + .block = TC3589x_BLOCK_GPIO, + .gpio = &mop500_tc35892_gpio_data, + .irq_base = MOP500_EGPIO_IRQ_BASE, +}; + +static struct lp5521_led_config lp5521_pri_led[] = { + [0] = { + .chan_nr = 0, + .led_current = 0x2f, + .max_current = 0x5f, + }, + [1] = { + .chan_nr = 1, + .led_current = 0x2f, + .max_current = 0x5f, + }, + [2] = { + .chan_nr = 2, + .led_current = 0x2f, + .max_current = 0x5f, + }, +}; + +static struct lp5521_platform_data __initdata lp5521_pri_data = { + .label = "lp5521_pri", + .led_config = &lp5521_pri_led[0], + .num_channels = 3, + .clock_mode = LP5521_CLOCK_EXT, +}; + +static struct lp5521_led_config lp5521_sec_led[] = { + [0] = { + .chan_nr = 0, + .led_current = 0x2f, + .max_current = 0x5f, + }, + [1] = { + .chan_nr = 1, + .led_current = 0x2f, + .max_current = 0x5f, + }, + [2] = { + .chan_nr = 2, + .led_current = 0x2f, + .max_current = 0x5f, + }, +}; + +static struct lp5521_platform_data __initdata lp5521_sec_data = { + .label = "lp5521_sec", + .led_config = &lp5521_sec_led[0], + .num_channels = 3, + .clock_mode = LP5521_CLOCK_EXT, +}; + +static struct i2c_board_info __initdata mop500_i2c0_devices[] = { + { + I2C_BOARD_INFO("tc3589x", 0x42), + .irq = NOMADIK_GPIO_TO_IRQ(217), + .platform_data = &mop500_tc35892_data, + }, + /* I2C0 devices only available prior to HREFv60 */ + { + I2C_BOARD_INFO("tps61052", 0x33), + .platform_data = &mop500_tps61052_data, + }, +}; + +#define NUM_PRE_V60_I2C0_DEVICES 1 + +static struct i2c_board_info __initdata mop500_i2c2_devices[] = { + { + /* lp5521 LED driver, 1st device */ + I2C_BOARD_INFO("lp5521", 0x33), + .platform_data = &lp5521_pri_data, + }, + { + /* lp5521 LED driver, 2st device */ + I2C_BOARD_INFO("lp5521", 0x34), + .platform_data = &lp5521_sec_data, + }, + { + /* Light sensor Rohm BH1780GLI */ + I2C_BOARD_INFO("bh1780", 0x29), + }, +}; + +#define U8500_I2C_CONTROLLER(id, _slsu, _tft, _rft, clk, t_out, _sm) \ +static struct nmk_i2c_controller u8500_i2c##id##_data = { \ + /* \ + * slave data setup time, which is \ + * 250 ns,100ns,10ns which is 14,6,2 \ + * respectively for a 48 Mhz \ + * i2c clock \ + */ \ + .slsu = _slsu, \ + /* Tx FIFO threshold */ \ + .tft = _tft, \ + /* Rx FIFO threshold */ \ + .rft = _rft, \ + /* std. mode operation */ \ + .clk_freq = clk, \ + /* Slave response timeout(ms) */\ + .timeout = t_out, \ + .sm = _sm, \ +} + +/* + * The board uses 4 i2c controllers, initialize all of + * them with slave data setup time of 250 ns, + * Tx & Rx FIFO threshold values as 8 and standard + * mode of operation + */ +U8500_I2C_CONTROLLER(0, 0xe, 1, 8, 100000, 200, I2C_FREQ_MODE_FAST); +U8500_I2C_CONTROLLER(1, 0xe, 1, 8, 100000, 200, I2C_FREQ_MODE_FAST); +U8500_I2C_CONTROLLER(2, 0xe, 1, 8, 100000, 200, I2C_FREQ_MODE_FAST); +U8500_I2C_CONTROLLER(3, 0xe, 1, 8, 100000, 200, I2C_FREQ_MODE_FAST); + +static void __init mop500_i2c_init(void) +{ + db8500_add_i2c0(&u8500_i2c0_data); + db8500_add_i2c1(&u8500_i2c1_data); + db8500_add_i2c2(&u8500_i2c2_data); + db8500_add_i2c3(&u8500_i2c3_data); +} + +static struct gpio_keys_button mop500_gpio_keys[] = { + { + .desc = "SFH7741 Proximity Sensor", + .type = EV_SW, + .code = SW_FRONT_PROXIMITY, + .active_low = 0, + .can_disable = 1, + } +}; + +static struct regulator *prox_regulator; +static int mop500_prox_activate(struct device *dev); +static void mop500_prox_deactivate(struct device *dev); + +static struct gpio_keys_platform_data mop500_gpio_keys_data = { + .buttons = mop500_gpio_keys, + .nbuttons = ARRAY_SIZE(mop500_gpio_keys), + .enable = mop500_prox_activate, + .disable = mop500_prox_deactivate, +}; + +static struct platform_device mop500_gpio_keys_device = { + .name = "gpio-keys", + .id = 0, + .dev = { + .platform_data = &mop500_gpio_keys_data, + }, +}; + +static int mop500_prox_activate(struct device *dev) +{ + prox_regulator = regulator_get(&mop500_gpio_keys_device.dev, + "vcc"); + if (IS_ERR(prox_regulator)) { + dev_err(&mop500_gpio_keys_device.dev, + "no regulator\n"); + return PTR_ERR(prox_regulator); + } + regulator_enable(prox_regulator); + return 0; +} + +static void mop500_prox_deactivate(struct device *dev) +{ + regulator_disable(prox_regulator); + regulator_put(prox_regulator); +} + +/* add any platform devices here - TODO */ +static struct platform_device *mop500_platform_devs[] __initdata = { + &mop500_gpio_keys_device, + &ab8500_device, +}; + +#ifdef CONFIG_STE_DMA40 +static struct stedma40_chan_cfg ssp0_dma_cfg_rx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_PERIPH_TO_MEM, + .src_dev_type = DB8500_DMA_DEV8_SSP0_RX, + .dst_dev_type = STEDMA40_DEV_DST_MEMORY, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; + +static struct stedma40_chan_cfg ssp0_dma_cfg_tx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_MEM_TO_PERIPH, + .src_dev_type = STEDMA40_DEV_SRC_MEMORY, + .dst_dev_type = DB8500_DMA_DEV8_SSP0_TX, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; +#endif + +static struct pl022_ssp_controller ssp0_platform_data = { + .bus_id = 0, +#ifdef CONFIG_STE_DMA40 + .enable_dma = 1, + .dma_filter = stedma40_filter, + .dma_rx_param = &ssp0_dma_cfg_rx, + .dma_tx_param = &ssp0_dma_cfg_tx, +#else + .enable_dma = 0, +#endif + /* on this platform, gpio 31,142,144,214 & + * 224 are connected as chip selects + */ + .num_chipselect = 5, +}; + +static void __init mop500_spi_init(void) +{ + db8500_add_ssp0(&ssp0_platform_data); +} + +#ifdef CONFIG_STE_DMA40 +static struct stedma40_chan_cfg uart0_dma_cfg_rx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_PERIPH_TO_MEM, + .src_dev_type = DB8500_DMA_DEV13_UART0_RX, + .dst_dev_type = STEDMA40_DEV_DST_MEMORY, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; + +static struct stedma40_chan_cfg uart0_dma_cfg_tx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_MEM_TO_PERIPH, + .src_dev_type = STEDMA40_DEV_SRC_MEMORY, + .dst_dev_type = DB8500_DMA_DEV13_UART0_TX, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; + +static struct stedma40_chan_cfg uart1_dma_cfg_rx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_PERIPH_TO_MEM, + .src_dev_type = DB8500_DMA_DEV12_UART1_RX, + .dst_dev_type = STEDMA40_DEV_DST_MEMORY, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; + +static struct stedma40_chan_cfg uart1_dma_cfg_tx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_MEM_TO_PERIPH, + .src_dev_type = STEDMA40_DEV_SRC_MEMORY, + .dst_dev_type = DB8500_DMA_DEV12_UART1_TX, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; + +static struct stedma40_chan_cfg uart2_dma_cfg_rx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_PERIPH_TO_MEM, + .src_dev_type = DB8500_DMA_DEV11_UART2_RX, + .dst_dev_type = STEDMA40_DEV_DST_MEMORY, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; + +static struct stedma40_chan_cfg uart2_dma_cfg_tx = { + .mode = STEDMA40_MODE_LOGICAL, + .dir = STEDMA40_MEM_TO_PERIPH, + .src_dev_type = STEDMA40_DEV_SRC_MEMORY, + .dst_dev_type = DB8500_DMA_DEV11_UART2_TX, + .src_info.data_width = STEDMA40_BYTE_WIDTH, + .dst_info.data_width = STEDMA40_BYTE_WIDTH, +}; +#endif + + +static pin_cfg_t mop500_pins_uart0[] = { + GPIO0_U0_CTSn | PIN_INPUT_PULLUP, + GPIO1_U0_RTSn | PIN_OUTPUT_HIGH, + GPIO2_U0_RXD | PIN_INPUT_PULLUP, + GPIO3_U0_TXD | PIN_OUTPUT_HIGH, +}; + +#define PRCC_K_SOFTRST_SET 0x18 +#define PRCC_K_SOFTRST_CLEAR 0x1C +static void ux500_uart0_reset(void) +{ + void __iomem *prcc_rst_set, *prcc_rst_clr; + + prcc_rst_set = (void __iomem *)IO_ADDRESS(U8500_CLKRST1_BASE + + PRCC_K_SOFTRST_SET); + prcc_rst_clr = (void __iomem *)IO_ADDRESS(U8500_CLKRST1_BASE + + PRCC_K_SOFTRST_CLEAR); + + /* Activate soft reset PRCC_K_SOFTRST_CLEAR */ + writel((readl(prcc_rst_clr) | 0x1), prcc_rst_clr); + udelay(1); + + /* Release soft reset PRCC_K_SOFTRST_SET */ + writel((readl(prcc_rst_set) | 0x1), prcc_rst_set); + udelay(1); +} + +static void ux500_uart0_init(void) +{ + int ret; + + ret = nmk_config_pins(mop500_pins_uart0, + ARRAY_SIZE(mop500_pins_uart0)); + if (ret < 0) + pr_err("pl011: uart pins_enable failed\n"); +} + +static void ux500_uart0_exit(void) +{ + int ret; + + ret = nmk_config_pins_sleep(mop500_pins_uart0, + ARRAY_SIZE(mop500_pins_uart0)); + if (ret < 0) + pr_err("pl011: uart pins_disable failed\n"); +} + +static struct amba_pl011_data uart0_plat = { +#ifdef CONFIG_STE_DMA40 + .dma_filter = stedma40_filter, + .dma_rx_param = &uart0_dma_cfg_rx, + .dma_tx_param = &uart0_dma_cfg_tx, +#endif + .init = ux500_uart0_init, + .exit = ux500_uart0_exit, + .reset = ux500_uart0_reset, +}; + +static struct amba_pl011_data uart1_plat = { +#ifdef CONFIG_STE_DMA40 + .dma_filter = stedma40_filter, + .dma_rx_param = &uart1_dma_cfg_rx, + .dma_tx_param = &uart1_dma_cfg_tx, +#endif +}; + +static struct amba_pl011_data uart2_plat = { +#ifdef CONFIG_STE_DMA40 + .dma_filter = stedma40_filter, + .dma_rx_param = &uart2_dma_cfg_rx, + .dma_tx_param = &uart2_dma_cfg_tx, +#endif +}; + +static void __init mop500_uart_init(void) +{ + db8500_add_uart0(&uart0_plat); + db8500_add_uart1(&uart1_plat); + db8500_add_uart2(&uart2_plat); +} + +static struct platform_device *snowball_platform_devs[] __initdata = { + &snowball_led_dev, + &snowball_key_dev, + &snowball_sbnet_dev, + &ab8500_device, +}; + +static void __init mop500_init_machine(void) +{ + int i2c0_devs; + + mop500_gpio_keys[0].gpio = GPIO_PROX_SENSOR; + + u8500_init_devices(); + + mop500_pins_init(); + + platform_add_devices(mop500_platform_devs, + ARRAY_SIZE(mop500_platform_devs)); + + mop500_i2c_init(); + mop500_sdi_init(); + mop500_spi_init(); + mop500_uart_init(); + + i2c0_devs = ARRAY_SIZE(mop500_i2c0_devices); + + i2c_register_board_info(0, mop500_i2c0_devices, i2c0_devs); + i2c_register_board_info(2, mop500_i2c2_devices, + ARRAY_SIZE(mop500_i2c2_devices)); + + /* This board has full regulator constraints */ + regulator_has_full_constraints(); +} + +static void __init snowball_init_machine(void) +{ + int i2c0_devs; + + u8500_init_devices(); + + snowball_pins_init(); + + platform_add_devices(snowball_platform_devs, + ARRAY_SIZE(snowball_platform_devs)); + + mop500_i2c_init(); + snowball_sdi_init(); + mop500_spi_init(); + mop500_uart_init(); + + i2c0_devs = ARRAY_SIZE(mop500_i2c0_devices); + i2c_register_board_info(0, mop500_i2c0_devices, i2c0_devs); + i2c_register_board_info(2, mop500_i2c2_devices, + ARRAY_SIZE(mop500_i2c2_devices)); + + /* This board has full regulator constraints */ + regulator_has_full_constraints(); +} + +static void __init hrefv60_init_machine(void) +{ + int i2c0_devs; + + /* + * The HREFv60 board removed a GPIO expander and routed + * all these GPIO pins to the internal GPIO controller + * instead. + */ + mop500_gpio_keys[0].gpio = HREFV60_PROX_SENSE_GPIO; + + u8500_init_devices(); + + hrefv60_pins_init(); + + platform_add_devices(mop500_platform_devs, + ARRAY_SIZE(mop500_platform_devs)); + + mop500_i2c_init(); + hrefv60_sdi_init(); + mop500_spi_init(); + mop500_uart_init(); + + i2c0_devs = ARRAY_SIZE(mop500_i2c0_devices); + + i2c0_devs -= NUM_PRE_V60_I2C0_DEVICES; + + i2c_register_board_info(0, mop500_i2c0_devices, i2c0_devs); + i2c_register_board_info(2, mop500_i2c2_devices, + ARRAY_SIZE(mop500_i2c2_devices)); + + /* This board has full regulator constraints */ + regulator_has_full_constraints(); +} + +static const char * snowball_dt_board_compat[] = { + "calaosystems,snowball-a9500", + NULL +}; + +MACHINE_START(U8500, "ST-Ericsson MOP500 platform") + /* Maintainer: Srinidhi Kasagar <srinidhi.kasagar(a)stericsson.com> */ + .atag_offset = 0x100, + .map_io = u8500_map_io, + .init_irq = ux500_init_irq, + /* we re-use nomadik timer here */ + .timer = &ux500_timer, + .handle_irq = gic_handle_irq, + .init_machine = mop500_init_machine, +MACHINE_END + +MACHINE_START(HREFV60, "ST-Ericsson U8500 Platform HREFv60+") + .atag_offset = 0x100, + .map_io = u8500_map_io, + .init_irq = ux500_init_irq, + .timer = &ux500_timer, + .handle_irq = gic_handle_irq, + .init_machine = hrefv60_init_machine, +MACHINE_END + +DT_MACHINE_START(SNOWBALL, "Calao Systems Snowball platform") + .atag_offset = 0x100, + .map_io = u8500_map_io, + .init_irq = ux500_init_irq, + /* we re-use nomadik timer here */ + .timer = &ux500_timer, + .handle_irq = gic_handle_irq, + .init_machine = snowball_init_machine, + .dt_compat = snowball_dt_board_compat, +MACHINE_END diff --git a/arch/arm/mach-ux500/include/mach/irqs.h b/arch/arm/mach-ux500/include/mach/irqs.h index 9db68d2..11e15d4 100644 --- a/arch/arm/mach-ux500/include/mach/irqs.h +++ b/arch/arm/mach-ux500/include/mach/irqs.h @@ -43,7 +43,7 @@ /* This will be overridden by board-specific irq headers */ #define IRQ_BOARD_END IRQ_BOARD_START -#ifdef CONFIG_MACH_U8500 +#if defined(CONFIG_MACH_U8500) || defined(CONFIG_MACH_MOP500) #include <mach/irqs-board-mop500.h> #endif -- 1.7.5.4

13 years, 3 months

4
4
0 0

[ACTIVITY] (John Stultz) Feb 27-Mar 2

by John Stultz

=== Highlights === * My LWN summary of the Android upstreaming interest group meeting from Linaro Connect was published: https://lwn.net/Articles/484196/ * Chased down an issue w/ serial triggered resume from suspend on Pandaboard. Working with PaulW & KevinH to narrow down the issue, as it seems to depend on a combination of uboot, kernel config, and boot options. * Did some initial testing w/ Rafael's wakelock patches using Android. Behavior is not totally what I expect, but some of the Android wakelock code is shifting (early suspend is being dropped) so I'm not sure if I have a ideal match between userland and kernel with which to compare. * Sent out patches to reduce timekeeping lock hold times. Got a bit of feedback from Ingo, which I integrated in. Also did some increased testing which found a few bugs in my new code. Also in testing my work, found and chased down some older timekeeping bugs that had been introduced upstream over the last few years. This took a good chunk of time this week. * Meetings: Ran Android-subteam meeting over email, Phone call with Zach, Lunch with Deepak. * Managed to reproduce an issue I saw earlier in the month with the lowmemory killer in staging. * Some internal items ate most of a day. === Plans === * Continue working with PaulW and KevinH to sort out alarmtiemr work * Need to really get focused on fadvise volatile work === Issues === * NA

13 years, 3 months

1
0
0 0

[ACTIVITY] (Linus Walleij) 2012-01-28 - 2012-03-02

by Linus Walleij

== Linus Walleij linusw == === Highlights === * Presented the pin control subsystem at the Embedded Linux Conference in San Francisco. * Discussed pin control at Linaro Connect, discussed pin control at Embedded Linux Conference. Wrote a bunch of patches refactoring the subsystem to be closer to what we agreed, Stephen will do the heavy lifting though. * Wrote and finalized a presentation for the Embedded Systems Conference pertaining to the platform perimeter including GPIO, pin control, device tree ... etc. * Reviewed and merged a whole bunch of patches from Stephen Warren @nVidia who gladly stepped in and offered to write the code we needed to get pin control to where we want it for v3.4. Dong Aishen is doing a great job in helping out with code review here. * Dummy pin controls implemented as default fallback for devices not provided with any controllers. * Sent pinctrl fixes to Torvalds for v3.3-rc4. * Collected a number of ux500 fixes and requested the ARM SoC maintainers to pull them in. Had to back off U9540 support but will reiterate. * Samuel Ortiz merged the DB8500 PRCMU update to the MFD tree. * Wrote mail to Greg & LKML about system controllers after discussion at ARM SoC maintainers summit. Seems the need may be there and we could create drivers/scm the day we have something that would live there. === Plans === * Accumulate pinctrl patches for kernel v3.4 merge window. * Drive generalization of Nomadik GPIO by using the pinctrl framework. drivers/gpio/gpio-nomadik.c * Test the PL08x patches on the Ericsson Research PB11MPCore and submit platform data for using pl08x DMA on that platform. * Look into other Ux500 stuff in need of mainlining... like - Ux500 clocks - the HWMON stuff. === Issues === * Ux500 mainlining or improvements (such as device tree) having second priority. * Sorry for long report covering much time, it's covering some of my vacation that is why... Thanks, Linus Walleij

13 years, 3 months

1
0
0 0

[ACTIVITY] (Saugata Das) Feb 27th - March 1

by Saugata Das

== Saugata Das sdas == === Activity Summary === * REQ_META patch submitted to EXT4 and FSDEVEL. Initial feedback is good from the community. Next step is to implement REQ_META on BTRFS. The BP (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-data-tag) is updated === Plans === * Work on native sector BP (https://blueprints.launchpad.net/linux-linaro/+spec/emmc4.5-native-sector) * Work on BP for putting journal on enhanced area (https://blueprints.launchpad.net/linux-linaro/+spec/journal-enhanced-emmc) === Issues === * None

13 years, 3 months

1
0
0 0

Replacing Kernel image suspends booting on "Uncompressing Linux... done, booting the kernel"

by Jaeyeon Kihm

Hi guys, Once I duplicated linaro-ubuntu-desktop image into SD card following the instruction on linaro website and it works fine. Now I need to patch the kernel so that I compiled the patched kernel and copy the kernel image into /boot of SD card but my pandaboard doesn't boot up. Below is more detail steps I did so please let me know what I did wrong. Also if you have an instruction, then it also might be really helpful. 1. I'm using PandaBoard ES. To start the board, I just dd linaro-ubuntu-desktop image to SD card following these steps ( http://releases.linaro.org/images/): # These values will change based on your system $ SDCARD=/dev/ #sdcard could be something sdb or mmcblk0 $ IMGFILE=overo-nano.img $ gunzip ${IMGFILE}.gz $ dd bs=64k if=${IMGFILE} of=${SDCARD} Then the linaro ubuntu works on the PandaBoard ES well. In detail, the version of this ubuntu 12.02 and kernel version is 3.1.1-8-linaro-lt-omap. 2. Next, I cloned your git repository(git:// git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git) to get kernel including remoteproc patch. Since there's no .config file I just copy the config file of 3.2-rc4 on here ( http://elinux.org/Panda_How_to_kernel_3_2_rcx) wihch is the version matching the kernel version on your git repository. And then I compile the kernel and modules to get an uImage and install modules with commands below (also explains http://elinux.org/Panda_How_to_kernel_3_2_rcx), and copy uImage to /boot on SD card and modules /rootfs/lib/ on SD card. I used arm-linux-gnueabi-gcc rather than arm-none-linux-gnueabi-gcc. Then compile like so: make ARCH=arm CROSS_COMPILE=Path_to_your/arm-2010q1/bin/arm-none-linux-gnueabi- uImage Then compile the modules like so: make ARCH=arm CROSS_COMPILE=/home/kenm/Panda/arm-2010q1/bin/arm-none-linux-gnueabi- modules "Install" the modules to somewhere convenient: make ARCH=arm CROSS_COMPILE=/home/kenm/Panda/arm-2010q1/bin/arm-none-linux-gnueabi- INSTALL_MOD_PATH=../testlib_omap modules_install 3. Then I put SD card to the Panda Board but it's suspending with the booting logs below. U-Boot SPL 2011.12-rc1 (Mar 01 2012 - 20:03:59) Texas Instruments OMAP4460 ES1.1 OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img U-Boot 2011.12-rc1 (Mar 01 2012 - 20:03:59) CPU : OMAP4460 ES1.1 Board: OMAP4 Panda I2C: ready DRAM: 1 GiB WARNING: Caches not enabled MMC: OMAP SD/MMC: 0 Using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 reading uEnv.txt ** Unable to read "uEnv.txt" from mmc 0:1 ** reading boot.scr 514 bytes read Loaded script from boot.scr Running bootscript from mmc0 ... ## Executing script at 82000000 reading uImage 3249584 bytes read reading uInitrd 1877535 bytes read reading board.dtb 340 bytes read ## Booting kernel from Legacy Image at 80200000 ... Image Name: Linux-3.2.0-rc4-00248-gb835c0f-d Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3249520 Bytes = 3.1 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 81600000 ... Image Name: initramfs Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 1877471 Bytes = 1.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 815f0000 Booting using the fdt blob at 0x815f0000 Loading Kernel Image ... OK OK reserving fdt memory region: addr=9d000000 size=3000000 Using Device Tree in place at 815f0000, end 815f3153 Starting kernel ... Uncompressing Linux... done, booting the kernel. Do you have any guess what I have missed or didn't do something? Any of your advise would be more than welcome. Thanks for your patches, and I really appreciate your consideration and help. Thanks, Jaeyeon

13 years, 3 months

1
0
0 0

[ACTIVITY] (Dong Aisheng) Feb 20 - Feb 29

by Dong Aisheng

=== Pinctrl === * Mainly focused on help reviewing pinctrl core rework patches(near 30 patches recently submitted by Stephen Warren and Linus Walleij) for API rework, merging mux and config and adding different state support as well as pinctrl core dt binding support(in plan). === Plan === * Continue to help review pinctrl core patches since many of them are still not hit mainline * Adding pin config and DT support for MX6Q pinctrl driver after pinctrl core rework patches get upstreamed * Will spend some free time to add DT support for MX28 platform

13 years, 3 months

1
0
0 0

Sample big.LITTLE model boot images

by Dave Martin

Hi all, I've added some detailed info on the wiki about how to go about building bootable images for the big.LITTLE components, here: https://wiki.linaro.org/Internal/Projects/Big.Little.Switcher/ARMFastModels… For the benefit of anyone who can't see that page, I've also pasted it here -- if anyone knows a better place to post this stuff, please let me know! Note that although the instructions give details of how to build a filesystem image, there is essentially nothing b.L or model-specific there -- it just serves as background for explaining how to work around some issues which you may encounter. These images are not supposed to present a fully working big.LITTLE system -- they are there to help people understand how booting works, where the sources are and how to work with the model. Note also that the bootwrapper will change soon (when I get there) to support loading of the kernel, initramfs from the host filesystem using semihosting, just like the kvm bootwrapper, but this isn't implemented for now. Cheers ---Dave == Filesystem == We need to create an SD card image with a filesystem on it, with the rootfs partition matching the bootargs set previously. The following example generates a suitable image using developer. The hardware pack is largely irrelevant because we're not getting the kernel, modules, bootloader or command-line from there -- but it keeps l-m-c happy. {{{ $ wget http://releases.linaro.org/12.02/ubuntu/oneiric-images/developer/linaro-o-d… $ wget http://releases.linaro.org/12.02/ubuntu/oneiric-images/developer/hwpack_lin… }}} Note that the ARM fast model's MMC interface emulation is currently limited to 2G. Make the image a bit smaller than that to be on the safe side: {{{ $ sudo linaro-media-create --dev vexpress --image_file mmc.bin --image_size 2000M --hwpack hwpack_linaro-lt-vexpress-a9_20120221-1_armel_suupported.tar.gz --binary linaro-o-developer-tar-20120221-0.tar.gz }}} After generating the filesystem, you probably want to customize it: * Disable address layout randomization (mitigates a memory consumption issue with the model, but not so important on host machines with >4GB of RAM): {{{ echo sys.kernel.randomize_va_space = 0 >>etc/sysctl.conf }}} * Disable DHCP for the network (otherwise boot will stall): {{{ sed -i '/auto.*eth0/d; s/^$iface.*eth0.*$dhcp/\1manual/' etc/network/interfaces }}} * Edit fstab to put the real device name into /etc/fstab in place of UUID=<uuid>. This may not be necessary (mountall was getting confused, but that may have been caused by not having an initramfs). Finally, extract the initramfs image (whatever /initrd.img in the filesystem image points to). == Kernel, switcher and bootwrapper == Clone the big.LITTLE switcher: {{{ $ git clone --branch gnu-build git://git.linaro.org/people/dmart/arm-virt-bl.git }}} Clone the kernel to run on the model. (Eventually we shouldn't need a special tree for this. There are a few model-specific tweaks in this tree, but nothing big.LITTLE-specific yet.) {{{ $ git clone --branch arm/vexpressdt-rtsm git://git.linaro.org/people/dmart/linux-2.6-arm.git }}} Now build the kernel: {{{ $ cd linux-2.6-arm/ $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- vexpress_rtsm_defconfig $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage dtbs }}} The bootwrapper doesn't support device tree yet, so for now append a suitable device tree blob to the zImage. This should match the model you intend to run on: {{{ $ cat arch/arm/boot/zImage arch/arm/boot/vexprress-v2p-ca15x4-rtsm.dtb >../zBlob }}} Now, build the bootwrapper using the kernel you just built: {{{ $ cd ../arm-virt-bl/bootwrapper }}} Configure some things: In Makefile, add the following argument to BOOTARGS: {{{ root=/dev/mmcblk0p2 }}} Due to current bugginess introduced by the ARM->GNU toolchain migration, the switcher is not currently stable. For now, we turn off autonomous asynchronous switching so that we can see the system booting: In big-little/Makefile, add change the line {{{ ASYNC ?= TRUE }}} to {{{ ASYNC ?= FALSE }}} Plug in the kernel and initramfs images from the previous steps: {{{ $ : >payload/fsimg $ cp ../../zBlob payload/kernel $ cp initrd.img payload/fsimg }}} ... and build: {{{ $ make [...] LD img.axf }}} img.axf is the boot payload which is needed to start the model. It contains the big.LITTLE switcher code and the kernel, along with a minimal bootloader. == Running == OK, so now we have: * A boot image containing the switcher and kernel: img.axf * A filesystem MMC card image: mmc.bin * A model binary Sample payload images can be found in http://people.linaro.org/~dmart/bl-images/model-images-20120228.tar.bz2 Run like this: {{{ $ ./RTSM_VE_Cortex-A15x4-A7x4 -C motherboard.mmc.p_mmc_file=mmc.bin -a coretile.cluster0.*=img.axf }}} This should be enough to boot to a prompt on the simulated UART. Beware though -- it can take up to 10 minutes or so to get there, depending on your machine.

13 years, 3 months

3
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel