=== Highlights ===
=== Pinctrl ===
* reviewed some converting imx driver to use pinctrl patches
* sent out a few pinctrl core fix and clean up patches
* added pinctrl mx5(mx51/mx53) support
* wrote a draft patch to implement per bin based config in a group, but it
seemed not good engouht
and found that current pinctrl config implementation is not suitable for
extend this feature due to different SoC's
characteristic and requirements, may think more on it and open the issue
for discussion
with some other people involved.
* pinctrl gpio support, did not spend too much time on it this week.
Due to the gpio base of dt is dynamically allocated which is not
suitable for current design,
still not found good idea to address this issue.
For IMX, we decided to config gpio in dts file as other pins
temporarily. Will keep tracking on
it.
=== mxs dt ===
* reviewd some mxs dt converting patches
=== Plan ===
* pinctrl per bin based config in the same group
* pinctrl gpio dt support improvement.
* convert remain imx drivers to use pinctrl
* convert mxs driver to support dt
Hi everyone,
This Thursday is a public holiday in Germany, so I won't be online and
Deepak is travelling, so let's cancel this weeks meeting. If something
important comes up, you can normally find me on #linaro-storage anyway
or send an email.
I think we can still do the meeting next week as a final preparation
for Connect, but it will likely be a short meeting since we are about
to meet (most of us) in person soon after that.
Arnd
=== Venkatraman S <svenkatr> ===
=== Highlights ===
* Submitted eMMC HPI patch v2 with complete changes upto OMAP controller driver
* Review eMMC BKOPS support and packed CMD support
* Submit various cleanup patches for OMAP MMC
=== Plans ===
* Collect profiling and application responsiveness data for HPI. Check
if the changes
in block layer / elevator can be minimized
* Update etherpad for Linaro connect storage work items, review state
of various features
* Cleanup and send erase block support for elevators to storage domain folks
=== Misc ===
* On leave for 2 days this week (May 15 & 16)
=== Highlights ===
* The mxs-common-clk series was finally pulled into arm-soc
* The late_initcall series was pulled into arm-soc
* Sent a series to convert outstanding imx and mxs device drivers to
adopt pinctrl support based on the dummy state support from Dong
Aisheng. It's on arm-soc now.
* Added device tree support for mxs i2c and audio drivers.
* Fixed various comments people put on mxs device tree branch. With
ack tags from subsystem maintainers collected, requesting Arnd and
Olof to pull the branch for upcoming v3.5 merge window.
* Sent a series to enable audio (DT) support for imx51-babbage and
imx53-qsb board.
* Reviewed and collected various imx device tree patches,
imx6q-sabrelite audio support from Richard Zhao, imx53-qsb DA9053
patch from Paul Liu. Came up the imx/dt/for-3.5 branch which has
been pulled into arm-soc now.
* Sent a couple of patches to update/fix pinctrl-mxs driver.
--
Regards,
Shawn
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Reworked the dw-mmc and spi patches based on review comments.
* Adding gpio interrupt and wakeup interrupt support in Samsung pinctrl driver.
=== Plans ===
* Complete the gpio interrupt and wakeup interrupt support in Samsung
pinctrl driver.
* Add device tree support for Samsung pinctrl driver.
== Linus Walleij linusw ==
=== Highlights ===
* Finalized and sent out ux500 pinctrl patches, they're already
ACKed by Stephen from nVidia so I will now funnel this into the
ARM SoC tree. Blueprint updated.
* Most Ux500 patches reported last week have landed in the
ARM SoC tree.
* Helped out in mainlining the ux500 crypto and hash drivers.
Patches are pending in Herbert Xu's tree, with some final touches
around the platform data and variant handling.
* Reviewed the incoming MIPS Lantiq pinctrl driver.
* Reviewed various incoming Ux500 devicetree patches from
Lee Jones.
* Discussed cyclic DMA callback and TX residue semantics with
Russell King, Mark Brown and some ALSA SoC developers.
* Mailed with Hongbo Zhang about DB8500 PRCMU API.
* Noticed incoming patches to siblings of the issue found in the
VIC IRQ handler, paged Julia Lawall about the possibility to
check for this type of bug using coccinelle, she promptly
identified two more suspicious drivers so I sent out patches
for those.
=== Plans ===
* Get Ux500 pinctrl into ARM SoC
* Finalize pinctrl for the upcoming 3.5 merge window.
* Review incoming pinctrl patches.
* 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 (looks like a new assignee might look into this)
- the HWMON stuff.
=== Issues ===
* NONE
Thanks,
Linus Walleij
===== highlights ====
1. Admin Tasks
- Followup for Board shipment
- collected 2 nos, V11 Snowball Board, kernel boots
- Further testing to be carried out
2. Sysadmin
- In the process of getting approval for firewall authentication for
git operations
- complete ubuntu distro setup on Virtual Box
3. DT Tasks
- DT for btemp is almost done, review in process
collected first level review comments from linusw and lee
- Adding platform specific data structure for btemp and to other
ab8500 device components
which helps to build and test the same
4. Support
- spend some time to look into the Uboot DT issue highlighted by
mathieu poirier.
- Supported Raj (newly joined member) for his on boarding activities
===== Plan ====
* Complete new staff tasks
* Continue to code and complete ab8500 DT components
* Review UBoot modification made by mathieu
==== Issues ====
--NA--
Thanks,
Rajanikanth
Hi.
We're using the 3.3 kernel from the TI landing team. The problem we are
facing is with real time audio. We are, through gst-poll, calling poll
every 10th ms to get audio samples. Problem is that it doesn't respond
fast enough, and we only manage to get the samples every 15-30th ms.
We have turned off the 32khz and tickless kernel flags in the kernel,
which seems to have helped some. Problem is that it's not stable at all,
some times it's fast enough, and gives a nice long tone, other times it
have long delays like before.
Do you have any suggestions as to other kernel configs that might help
with this?
Any help would be greatly appreciated.
=== Highlights ===
* Setup ubuntu distro on virtual box. {IT policy does not allow linux
distro on Laptop}
* Completed On Boarding Activities
* Spent time on sysadmin activities to get permission for server
access, distro upgrade etc.,
* Spent some time to look into UBoot DT Issue highlighted by Mathieu Poirier
* DT Study
* Started device tree binding for ab8500 battery temperature sensor.
=== Plans ===
* Complete new staff tasks
* Continue to code and complete ab8500 DT components
* Complete sysadmin activity pending if any
=== Issues ===
SysAdmin activities including Ubuntu distro setup consuming more time.
=== Highlights ===
* Addressed comments people put on arch_initcall cleanup series v1,
and sent out v2 which turns out a pull-request to Arnd for seeking the
exposure on linux-next.
* Reviewed and collected imx pinctrl platform changes from Dong
Aisheng, and sent out a series to add pinctrl support for a number of
outstanding imx and mxs device drivers.
* Sent out a series to have basic imx28 device tree support rebased on
common-clk and pinctrl, and basic imx23 DT support is also added.
* Sent out a series to convert gpio-mxs driver to device tree.
* Sent out a series to convert mxs-mmc driver to device tree.
* Reviewed mxs-dma device tree series v2 from Dong Aisheng and have it
rebased on common-clk and pinctrl.
* Reviewed and collected a few imx6q patches adding UART2 low-level
debug, SPI NOR, and SSI dts changes.
* Helped FSL Landing team enable imx53-qsb audio support on their v3.4 tree.
Regards,
Shawn
== Highlights ==
* Prepared some new features for vmevent:
- a new low-memory blended attribute. This is used to wisely account
page cache. The feature triggered a big discussion, so we might
end up with something different as the discussion is still ongoing;
- 'equal-to' attribute state (this is merged already);
* Never-ending discussion on memcg and vmevents memory notifications
continued;
* ram_console feature seemed quite interesting, so I started looking
more closely into it. Based on previous lkml discussions, it appears
that the main obstacle is that we should use pstore. So, as a warm-up
I started porting ramoops (which uses pstore in -next tree) driver to
use persistent_ram. That would be a good reason to move
persistent_ram out of staging/.
* v3.4 is approaching rc7 (or final), so I had to dedicate some time
for a pile of battery patches collected in my 'todo' mailbox.
== Plans ==
* Pekka asked to look into improving LT/GT/EQ handling in vmevent, make
it table-based may be;
* I was quite reluctant to getting my hands dirty into the cpufreq as
nobody likes it, and thus I'm risking to get involved into another
never-ending story, plus after refreshing Android git tree I noticed
that Android guys are actively hacking it at this precise moment. So,
to not step on each others' toes, I finally decided I'd better work
on something else, thus I picked ram_console and friends.
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
== Deepak Saxena <dsaxena> ==
(Took last Monday and Tuesday off to deal with some house issues)
=== Highlights ===
* Finalized list of introductory training at Connect:
Upstreaming 101: How and Why of Getting Code Accepted into the
kernel (Deepak S.)
Git 101: Using Git for kernel development (Matt W.)
ARM SOC Tree: Advice on doing a new platform or SOC port the right
way (Arnd B.)
Device Tree Intro: How and why of using DT (Thomas A.)
Pin Mux/Pin Control: How to develop a driver, overview of API (Linus W.)
* Connect session planning
=== Plans ===
* Sync up with interested parties (Dave R., Jon M., Leif L.) on
Enterprise kernel sessions
* Google Hangout on Air interview for marketing/outreach of Connect
training sessions.
* Continue Connect session planning: creating detailed outlines,
coordinating facilitators, slides, etc...
* Continue looking at/brain-storming about different methods for tracking work.
* Usual 1:1's and meetings
=== Issues ===
* None at the time
=== Travel/Time Off ===
* May 22nd - June 12th:
Austin to sync up with Mounir and Rob Herring
Linaro Connect
Few days of vacation in Beijing
Linux Con Japan
A few days of vacation in Tokyo
Back Home!
* Travel to visit family 7/27 - 8/1. Will be working from CST time
zone instead of PST.
* Out August 22nd- Sept 5th. Will be in the middle of nowhere and
have no connectivity.
=== Pinctrl ===
* pinctrl-imx patch series is already merged by Linus.
* converted esdhc driver to use pinctrl. merged by Shawn
=== mxs dt ===
* sent a patch series to make mxs-dma driver mach-independent and support
dt
=== Plan ===
* Implement per pin mux and config for pinctrl subsystem
* Improve pinctrl gpio support for dt
* convert remain imx drivers to use pinctrl
* convert mxs driver to support dt
=== Highlights ===
* Got further feedback from DaveC on the volatile ranges work. I need
to rework the patch significantly to use the falloc interface instead of
fadvise in order to allow the functionality to be more generic and
implementable on a per-filesystem basis (as there are lots of fs
specific tricks that can be used). Despite his insistence that I rework
it, he did say that he was interested in seeing the functionality added,
since he has some ideas for how it can be used w/ xfs. Started the
process of figuring out how to refactor the code to be per-fs, ideally
without rewriting most of it.
* Further review and quite a bit of discussion around community
CLOCK_TAI groundwork and improved leapsecond processing. Also got into
a big discussion with a researcher on UTC-SLS (smoothed leap second)
which allows applications to avoid the nasty leapsecond by smearing it
over ~15 minutes. All interesting, but getting both features to not
conflict and work together will be interesting. Submitted a example RFC
of how I'd like to see CLOCK_TAI implemented.
* Wrote up some blueprints for possible future Android related work
focusing on debugging
technology.https://blueprints.launchpad.net/linux-linaro/+spec/android-debu…
* Reported a compile bug w/ omap-usb-host.c caused by a not-so-recent
commit. The proper fix was merged shortly there after.
* Updated linaro-android-3.4 tree and made a few corrections at Andrey's
request.
=== Plans ===
* Continue reworking volatile ranges to use fadvise.
* Will be on vacation from May 9th-16th.
=== Issues ===
NA
== Linus Walleij linusw ==
=== Highlights ===
* Brought ux500 pinctrl forward, trying to find a smooth transition
from the existing codebase to a pinctrl-based approach. This is
taking some time since it requires quite a bit of upfront code.
Patches can be expected next week.
* Iterated/split the ux500 pull requests for the next merge window,
now in place and being boiled in -next after a minor screwup
with Lee's devicetree patches.
* Russell accepted some patches, especially the multiirq and
irqdomain patch for the FPGA IRQ controller.
* Discussing power domain issues.
=== Plans ===
* Convert ux500 (gpio-nomadik) to pinctrl
for the kernel 3.5 timeframe.
* Review incoming pinctrl patches.
* 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 (looks like a new assignee might look into this)
- the HWMON stuff.
=== Issues ===
* Children got chickenpox, back at work a constant line of
people and mail make it hard to get work done at times.
Thanks,
Linus Walleij
Hi all,
That's a respin of the previous patchset that tried to add a new
'cross' event type, which would trigger whenever value crosses a
user-specified threshold both ways, i.e. from a lesser values side
to a greater values side, and vice versa.
We use the event type in an userspace low-memory killer: we get a
notification when memory becomes low, so we start freeing memory by
killing unneeded processes, and we get notification when memory hits
the threshold from another side, so we know that we freed enough of
memory.
There's also a fix for a bug that makes kernel upset about sleeping
in the atomic context.
Per Pekka's comments here comes v2. Changes:
- Added a one-shot mode plus a greater-than attribute, the two
additions makes the equivalent of the cross-event type.
- In the bugfix patch I added some comments about implementation
details of the lock-free logic. Also, in the previous version of
the fix I forgot to remove 'struct mutex' form the
'struct vmevent_watch', this is now cleaned up.
As usual, the patches are against
git://github.com/penberg/linux.git vmevent/core
Thanks!
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
== Omar Ramirez <omarrmz> ==
=== Highlights ===
* Thread switching for bl-agitator, completed
- Added the feature for Android and Ubuntu/minimal fs.
* Resent: Iommu: OMAP: device detach on domain destroy
- Rebased to 3.4-rc2.
* Fixed dspbridge compilation break because of OMAP_L2_IO_ADDRESS macro.
* Tested Linaro kernel with DT
- Had to use 3.3 tilt as latest was unstable due to ongoing changes.
- It does accept DT.
* Internal (TI) training for tidspbridge from how to boot to test execution.
* tidspbridge: debugged dsp binaries since latest kernels have been
throwing L3 warnings when loading a static baseimage.
- It turned out to be changes in gpio uncovered a bug in the code
present in d.o-z, since it was accessing a gpio in the first bank
while in retention.
- Fixed and uploaded new exports.
- Removed precompiled binaries from d.o-z
- Fixed userspace samples build since a variable was being overriden.
* Maiblox DT rebased latest rc and cleaned up. (Minor cleanups and
retested in OMAP4)
- Needs testing in OMAP3.
=== Planned ===
* Test mailbox DT in OMAP3 and send to LO.
* debugfs interface for big.LITTLE to know which cluster is being used.
* bl-agitator refactoring and cleanup, if possible.
* Rebase iommu hwmod one more time.
- Add reset handling for linux-omap.
* Iommu DT
=== Highlights ===
* Addressed the comments that Mike and Sascha put on mxs common clk
series v1 and sent v2 based on Mike's clk-next branch, and expect
it go through arm-soc with Russell's clkdev and Mike's clk core pull
into arm-soc as dependencies.
* Had an extensive discussion with Dong Aisheng on imx and mxs pinctrl
binding and eventually agreed that we do not have to push for the
same binding as the controller between two architecture is so
different. Reviewed and acked pinctrl-imx v2 from Dong. Sent
pinctrl-mxs v2 with binding document improved and one small comment
from Stephen addressed.
* Reviewed imx5/6 cpuidle series from Rob Lee. We, including Sascha
and Russell agreed that instead of detecting soc type in a global
late_initcall call, a machine specific late_initcall time hook should
be added into "struct machine_desc" to do late init. But Russell
requires the patch series introducing the hook should convert all
existing late_initcall in arch/arm/mach-* to use this hook. Sent
a series to do this which actually is part single kernel work.
--
Regards,
Shawn
[ Yeah OK... I'm really bad with this stuff. ]
January 23 to FEbruary 03
- More on-going study of the standalone b.L switcher code.
- Discussion with Le.chi Thu, Paul Larson and others about big.LITTLE
switcher testing requirements.
- Involved in the review cycle for a patch about the new generic ioremap
optimization from Pawel Moll which turned out to be bad and needed
a subsequent revert.
- Obtaining and setting up the b.L Fast Model license.
- Review of some RCU changes pushed down the platform idle code path by Paul E.
McKenney which I ended up NAKing.
- Review of a patch from Stephen Boyd to disable preemption when reading
CCSIDR on ARMv7 to which I suggested a simpler alternative.
- Review of the initial test plan for the big.LITTLE switcher.
- REview of the SA11x0 cleanups from RMK.
- Investigation and prodding sent to Andrew Lunn for fixing a few Kirkwood
breakages from recent consolidation changes.
- More design discussions around b.L switcher with people from ARM Ltd,
notably Robin Randhawa.
- Preparing for Linaro Connect.
February 06 to 10
- Attending Linaro Connect.
- REview of Rob Herring's series cleaning up and removing IRQ and
FIQ related macros from the kernel.
- Wrote an article about big.LITTLE switcher for LWN.
- REview of Marc Zyngier's series to add per SoC SMP and CPU hotplug
operations.
- Quickstart session with Dave Martin to run the ARM Fast Model for b.L.
February 13 to 24
- Refinement to my LWN article about b.L before publication.
- Review of a patch series preparing the kernel for being entered in hypervisor
mode by Dave Martin.
- Discussion (on IRC) between Dave Martin and myself about design changes
brought to the in-kernel b.L switcher.
- Start experimenting with the b.L fast model.
- Read and digested various documents about the ARM virtualization,
the GIC, etc.
- Produced some b.L project status to help project management transition
from Usman to Mounir.
- Posted a patch to add support for early console output via semihosting.
- Wrote the first part of the big.LITTLE write-up for the monthly member
report (Paul McKenney did the second part).
February 27 to March 02
- Away on vacation.
March 05 to 16
- Review of the initial Kirkwood conversion to FDT by jason(a)lakedaemon.net.
- Review of a patch series removing most instances of io.h by Rob Herring.
- Comments/suggestions on how to deal with unresponsive maintainers,
prompted by Amit Kucheria.
- Review of a patch by Stephen Warren to generalize u-Boot's uImage
wrapping in the kernel build.
- More experiments with the b.L software model, attempting to boot
a 8-core SMP system, running into cross cluster cache coherency problems.
Finally get it to boot, thanks to the ARM guys who provided the missing
clue.
- Look at the multi-cluster aware boot protocol patches by Lorenzo
Pieralisi. Some of it might be directly useful for the b.L switcher.
- Review of Dave Martin's patch series to facilitate custom opcode
injection.
- Improved a patch I posted months ago to remove the debugging restrictions
inside the devicemaps_init() function and pushed upstream. REcent changes
to the kernel are making this patch very useful for people to debug
their own kernel.
- Quick review of the Cortex-M3 support by Uwe Kleine-König.
- Moved to the arm-soc tree to implement the in-kernel switcher as it
contains everything to boot a vexpress config with device tree on the
software model.
Nicolas
=== Pinctrl ===
* sent out pinctrl core add defer probe for gpio patch, merged by Linus.
* sent out pinctrl-imx v4 series patch
Already got Stephen Warren and Shawn Guo's ack. No more comments for a
few days.
I assume Linus Walleij may pick it up soon.
* Implement a common API to handle pinctrl dummy state, merged by Linus.
* Reviewed some other pinctrl patches.
* Implement per pin mux and config for pinctrl subsystem. INPROGRESS
=== Plan ===
* send out a draft pinctrl per pin mux and config patch and discuss it
with Linus and Stehpen.
* since the gpio base is dynamically allocated from DT, the exist pinctrl
gpio support
implementation based on fixed gpio base map may not fit any
more with DT.
Will think more about the solution and discuss it with Linus.
After a big move and other things, finally I can focus on the Linux
work. Now I have a high-speed internet in my new place, so using
'mumble' for conferencing is no problem any longer.
== Highlights ==
* We've got some 'looks fine' feedback on the userland LMK, and that's
reassuring.
The "bad news" is that there's not much of enthusiasm overall from
Android folks. That's understandable as kernel LMK driver works and
already in mainline^Wstaging kernel, so why bother. Well, it can't
live in staging/ forever, so we'd better hurry up.
* ulmkd's Makefile is again suitable for GNU/Linux builds
(as an addition to Android/Linux). This makes it easier for me
to test, plus maybe there we'll be other users for the daemon.
* for_each_process and task->mm fixes finally merged into -mm.
I will need a small documentation update for the series, but
overall the series seem to be fine.
* Prepared a few fixes for the memcg slab accounting. The proposed
slab accounting feature looks like exactly what was needed, except
that it doesn't account slab for the root cgroup. If that's not
a design decision, then it can be improved. If not, there are
two ways: a) drop cgroups support and go solely w/ vmevent
infrastructure b) try to push something like 'memory.available'
attribute for memcg. 'a)' is easy, and 'b)' is probably what I'll
try to implement tomorrow. Once implemented, we'll have all
options ready, and so can mark cgroups as either fully suitable
for lowmem notifications or not suitable by design.
== Plans ==
* I wonder if I need to make a deep-dive into Android build system
and try to integrate ulmkd into Android image myself?
* Back to interactive governor improvements? Well, as far as I
recall, the story behind interactive governor is very similar to
LMK: nobody likes the cpufreq overall, and want generic power
management improvements for the scheduler. At least, we need to
get 'interactive vs. ondemand' cpufreq latency numbers. That
would be a good starting point for any other improvements. And
the problem with cpufreq latency measurements was that it takes
ages for the benchmark to complete.
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
Hello Glauber,
On Fri, Apr 20, 2012 at 06:57:08PM -0300, Glauber Costa wrote:
> This is my current attempt at getting the kmem controller
> into a mergeable state. IMHO, all the important bits are there, and it should't
> change *that* much from now on. I am, however, expecting at least a couple more
> interactions before we sort all the edges out.
>
> This series works for both the slub and the slab. One of my main goals was to
> make sure that the interfaces we are creating actually makes sense for both
> allocators.
>
> I did some adaptations to the slab-specific patches, but the bulk of it
> comes from Suleiman's patches. I did the best to use his patches
> as-is where possible so to keep authorship information. When not possible,
> I tried to be fair and quote it in the commit message.
>
> In this series, all existing caches are created per-memcg after its first hit.
> The main reason is, during discussions in the memory summit we came into
> agreement that the fragmentation problems that could arise from creating all
> of them are mitigated by the typically small quantity of caches in the system
> (order of a few megabytes total for sparsely used caches).
> The lazy creation from Suleiman is kept, although a bit modified. For instance,
> I now use a locked scheme instead of cmpxcgh to make sure cache creation won't
> fail due to duplicates, which simplifies things by quite a bit.
>
> The slub is a bit more complex than what I came up with in my slub-only
> series. The reason is we did not need to use the cache-selection logic
> in the allocator itself - it was done by the cache users. But since now
> we are lazy creating all caches, this is simply no longer doable.
>
> I am leaving destruction of caches out of the series, although most
> of the infrastructure for that is here, since we did it in earlier
> series. This is basically because right now Kame is reworking it for
> user memcg, and I like the new proposed behavior a lot more. We all seemed
> to have agreed that reclaim is an interesting problem by itself, and
> is not included in this already too complicated series. Please note
> that this is still marked as experimental, so we have so room. A proper
> shrinker implementation is a hard requirement to take the kmem controller
> out of the experimental state.
>
> I am also not including documentation, but it should only be a matter
> of merging what we already wrote in earlier series plus some additions.
The patches look great, thanks a lot for your work!
I finally tried them, and after a few fixes the kmem accounting
seems to work fine with slab. The fixes will follow this email,
and if they're fine, feel free to fold them into your patches.
However, with slub I'm getting kernel hangs and various traces[1].
It seems that kernel memcg recurses when trying to call
memcg_create_cache_enqueue() -- it calls kmalloc_no_account()
which was introduced to not recurse into memcg, but looking
into 'slub: provide kmalloc_no_account' patch, I don't see
any difference between _no_account and ordinary kmalloc. Hm.
OK, slub apart... the accounting works with slab, which is great.
There's another, more generic question: is there any particular
reason why you don't want to account slab memory for root cgroup?
Personally I'm interested in kmem accounting because I use
memcg for lowmemory notifications. I'm installing events
on the root's memory.usage_in_bytes, and the thresholds values
are calculated like this:
total_ram - wanted_threshold
So, if we want to get a notification when there's 64 MB memory
left on a 256 MB machine, we'd install an event on the 194 MB
mark (the good thing about usage_in_bytes, is that it does
account file caches, so the formula is simple).
Obviously, without kmem accounting the formula can be very
imprecise when kernel (e.g. hw drivers) itself start using a
lot of memory. With root's slab accounting the problem
would be solved, but for some reason you deliberately do not
want to account it for root cgroup. I suspect that there are
some performance concerns?..
Thanks,
[1]
BUG: unable to handle kernel paging request at ffffffffb2e80900
IP: [<ffffffff8105940c>] check_preempt_wakeup+0x3c/0x210
PGD 160d067 PUD 1611063 PMD 0
Thread overran stack, or stack corrupted
Oops: 0000 [#1] SMP
CPU 0
Pid: 943, comm: bash Not tainted 3.4.0-rc4+ #34 Bochs Bochs
RIP: 0010:[<ffffffff8105940c>] [<ffffffff8105940c>] check_preempt_wakeup+0x3c/0x210
RSP: 0018:ffff880006305ee8 EFLAGS: 00010006
RAX: 00000000000109c0 RBX: ffff8800071b4e20 RCX: ffff880006306000
RDX: 0000000000000000 RSI: 0000000006306028 RDI: ffff880007c109c0
RBP: ffff880006305f28 R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000000 R12: ffff880007c109c0
R13: ffff88000644ddc0 R14: ffff8800071b4e68 R15: 0000000000000000
FS: 00007fad1244c700(0000) GS:ffff880007c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffb2e80900 CR3: 00000000063b8000 CR4: 00000000000006b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process bash (pid: 943, threadinfo ffff880006306000, task ffff88000644ddc0)
Stack:
0000000000000000 ffff88000644de08 ffff880007c109c0 ffff880007c109c0
ffff8800071b4e20 0000000000000000 0000000000000000 0000000000000000
ffff880006305f48 ffffffff81053304 ffff880007c109c0 ffff880007c109c0
Call Trace:
Code: 76 48 41 55 41 54 49 89 fc 53 48 89 f3 48 83 ec 18 4c 8b af e0 07 00 00 49 8d 4d 48 48 89 4d c8 49 8b 4d 08 4c 3b 75 c8 8b 71 18 <48> 8b 34 f5 c0 07 65 81 48 8b bc 30 a8 00 00 00 8b 35 3a 3f 5c
RIP [<ffffffff8105940c>] check_preempt_wakeup+0x3c/0x210
RSP <ffff880006305ee8>
CR2: ffffffffb2e80900
---[ end trace 78fa9c86bebb1214 ]---
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
=== Highlights ===
* Interview with Deepak and one-on-one introductory discussion
- Deepak pointed me to relevant linaro WIKI's with appropriate usage
information
* Discussion with lee jones and Deepak about the DT Work. ab8500 power has
been assigned
* OnBoarding is nearing completion
* Spent some time to read through DT documents
* Lee jones supported me to get the build and test readiness, Setup to
start the work is ready.
* Attended session on "platform perimeter" hosted by Linus Walleij
- http://www.df.lth.se/~triad/papers/ESC-400Slides_Walleij.pdf
* Spent good length of time with niklas to get the DeviceTree work
transferred
=== Plans ===
* Complete ab8500 power DeviceTree assignments
* Spend some time on DT Spec study
* IT/Admin work to carryout in order to get the new laptop with UBUNTU
distro.
* Complete the pending onboard activity
=== Issues ===
* 2011-09 version of linaro-media-create python application did not succeed
in
preparing bundled image for flashing, so migrated to 2012.04-1, found
issue is
fixed.
https://launchpad.net/ubuntu/+source/linaro-image-tools/2012.04-1/+build/34…
=== Highlights ===
* Tested Rafael's wakelock interface patches. Found a bug and sent a
fix, which he included.
* Submitted the volatile ranges patch for inclusion. Got some minor
feedback. Dave Chinner suggested I rework the patch so that it uses
fallocate rather then fadvise. I pushed back a bit to make sure that is
a consensus opinion, but will likely try to switch things over next week.
* After getting positive feedback from Arve, on my patch to convert
ashmem to use wakeup sources instead of the stubbed out wakelocks, I
submitted it and Greg included it into staging-next for 3.5
* Got a small RTC null pointer fix merged into tip/timers/urgent for 3.4
* Pinged the Android team on Anton's ulmkd proposal, got some
interesting feedback, and no outright objections.
* Submitted a talk to linux plumbers
* Reviewed some patches to introduce CLOCK_TAI functionality. Queued a
few community cleanups.
=== Plans ===
* Rework volatile ranges to use fallocate & resubmit to lkml
=== Issues ===
NA
== Linus Walleij linusw ==
=== Highlights ===
* pinctrl fixes sent and pulled by Torvalds.
* Reviewed and applied a bunch of pinctrl patches from Stephen,
Dong, and a newcomer: John Crispin from OpenWRT. We have
good traction in this subsystem.
* Sent pull requests for ux500-core, ux500-devicetree and
ux500-gpio-pins to bring the machine up to date with the recent
patches. Not yet pulled into ARM SoC
* Brought ux500 pinctrl forward, trying to find a smooth transition
from the existing codebase to a pinctrl-based approach. This is
taking some time since it requires quite a bit of upfront code.
* Reviewing device tree from Lee Jones.
* Russell accepted PL190 VIC cleanups and applied them.
* Discussing power domain issues. Andrea and our internal
power management team as well as Vincent Guittot from Linaro
PM are all involved. We might need to propose modifications to
runtime PM.
* Ran the ESC platform perimeter presentation twice internally
discussing and presenting new features in kernels 3.0 thru 3.4+
roughly. It appears to have been appreciated.
http://www.df.lth.se/~triad/papers/ESC-400Slides_Walleij.pdf
=== Plans ===
* Review incoming pinctrl patches.
* Convert ux500 (gpio-nomadik) to pinctrl
for the kernel 3.5 timeframe.
* 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 (looks like a new assignee might look into this)
- the HWMON stuff.
=== Issues ===
* Reviewing-and applying pinctrl and ux500 patches cuts
into ux500 pin control development and disturbs focus.
Thanks,
Linus Walleij
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Researching new roadmap cards
* Talk on "One zImage to Rule them All" accepted to LinuCon Japan!
* Doing lots of back research on single zImage. Focusing on
information research right now,
going through all the emails I can find on the topic back to last
May, chasing down discussions,
digging through the kernel, syncing up with Nico and Arnd as
needed, and getting my head
around it all. My goal is to have a clear idea of what is left to
do and also a plan of what
we should focus on at Connect.
* 1:1's
* Interviewed Rajinakanth from ST-E for KWG
* Synced up with Scott and Vicki on training sessions at Connect.
=== Plans ===
* Usual 1:1's and meetings
* ST-E DT sync up with Raj and Lee
* Connect training planning
* Interviewing Ulf from ST-E for KWG position
* Continue work on new roadmap cards
* Continue single zImage deep dive
* Dig out my timex.h patches if I have time
=== Issues ===
* None at the time
=== Travel/Time Off ===
* Possibly out Monday, April 30th.
* Off May 4th and following week, back to work on Monday the 13th.
Will have no interwebs and limited phone access.
* Connect Q2, with follow up travel to Linux Con Japan the week after
and going to Austin before Connect to sync up with Mounir.
=== Highlights ===
* Sent the mach-mxs common clk conversion series based on v3.4-rc3 plus
various fixup/cleanup patches that Mike confirmed pick-up on his
-next branch and the clkdev registration patch.
* Reviewed imx pinctrl patch from Dong Aisheng.
* Added pinctrl support for mach-mxs in using a different binding from
imx. Discussing the pros and cros between these two the bindings.
* Reviewed initial spi-mxs support patch from Fabio.
* Reviewed the mach-mxs changes of Marek's mxs usb series, and push him
to use device tree.
* Reviewed mxs-dma device tree support series from Dong Aisheng.
* Reviewed gpmi-nand device tree support series from Huang Shijie.
* Reviewed and merged the initial imx6q-sabresd support patch from
Fabio.
* Reviewed imx5/6 cpuidle patches from Rob Lee.
--
Regards,
Shawn
=== Pinctrl ===
* sent two patch to improve pinctrl core debug information
* sent out pinctrl-imx v2 patch
Addressed many comments from Stephen, Sascha and etc.
The main changes are allow pin based config.
Still not received comments.
* Sent out handling pinctrl dummy state in core patch.
Got a lot discussions, the finally decision would be provide a common
api for platforms to call
to decide whether it needs using dummy state.
* sent out a patch series to convert mxs-dma driver to be more generic to
support both mxs and mx6
and add dt support
=== Plan ===
* send pincgtrl handling dummy state v2 patch, then we can start convert
drivers to use pinctrl
without breaking exist code.
* pinctrl handle dummy gpio support which avoid breaking exist code when
using pinctrl gpio support
* pinctrl-imx gpio support which depends on pinctrl handle dummy gpio patch
...otherwise the we're getting the wrong numbers in usage_in_bytes.
On Mon, Mar 05, 2012 at 09:19:34AM +0900, KAMEZAWA Hiroyuki wrote:
[...]
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index 228d646..c8abdc5 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -3812,6 +3812,9 @@ static inline u64 mem_cgroup_usage(struct mem_cgroup *memcg, bool swap)
> >
> > val = mem_cgroup_recursive_stat(memcg, MEM_CGROUP_STAT_CACHE);
> > val += mem_cgroup_recursive_stat(memcg, MEM_CGROUP_STAT_RSS);
> > + val += mem_cgroup_recursive_stat(memcg, MEM_CGROUP_STAT_FILE_MAPPED);
> >
> > 1. Is there any particular reason we don't currently account file mapped
> > memory in usage_in_bytes?
> >
> > To me, MEM_CGROUP_STAT_FILE_MAPPED hunk seems logical even if we
> > don't use it for lowmemory notifications.
> >
> > Plus, it seems that FILE_MAPPED _is_ accounted for the non-root
> > cgroups, so I guess it's clearly a bug for the root memcg?
>
> CACHE includes all file caches. Why do you think FILE_MAPPED is not included in CACHE ?
There were tons of changes in the memcg lately, but I believe the issue
is still there.
For example, looking into this code flow:
-> page_add_file_rmap() (mm/rmap.c)
-> mem_cgroup_inc_page_stat(page, MEMCG_NR_FILE_MAPPED) (include/linux/memcontrol.h)
-> void mem_cgroup_update_page_stat(page, MEMCG_NR_FILE_MAPPED, 1) (mm/memcontrol.c)
And then:
void mem_cgroup_update_page_stat(struct page *page,
enum mem_cgroup_page_stat_item idx, int val)
{
...
switch (idx) {
case MEMCG_NR_FILE_MAPPED:
idx = MEM_CGROUP_STAT_FILE_MAPPED;
break;
default:
BUG();
}
this_cpu_add(memcg->stat->count[idx], val);
...
}
So, clearly, this function only bothers updating _FILE_MAPPED only,
leaving _CACHE alone.
If you're saying that _CACHE meant to include _FILE_MAPPED, then
I guess the patch down below would be a proper fix then... Otherwise
we need to be consistent on stats reporting, and either fall-back
to my original fix (in mem_cgroup_usage()), or think about doing it
some other way...
Signed-off-by: Anton Vorontsov <anton.vorontsov(a)linaro.org>
---
The patch is against current -next.
Thanks,
mm/memcontrol.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 884e936..760ecf5 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1958,6 +1958,8 @@ void mem_cgroup_update_page_stat(struct page *page,
switch (idx) {
case MEMCG_NR_FILE_MAPPED:
+ idx = MEM_CGROUP_STAT_CACHE;
+ this_cpu_add(memcg->stat->count[idx], val);
idx = MEM_CGROUP_STAT_FILE_MAPPED;
break;
default:
--
1.7.9.2
=== Highlights ===
* Reworked the Android ashmem code so it uses my fadvise volatile work
* Handled a few issues for Andrey w/ the linaro-android-3.4 tree.
* Synced up with gregkh and tglx, then sent the Android Alarm timer
mending patches to staging for 3.5, and got them merged.
* Converted Android Alarm driver to using wakeup sources instead of
wakelocks, sent out an RFC to lkml and the Android team
* Spent more time looking at Rafael's userland wakelock api.
* Worked on reported RTC regression. Looks to be a hardware quirk, but
still waiting on feedback from the owner.
* Dug in a bit on a community clocksource watchdog issue. Still no
solution yet.
* Gave Deepak feedback on upstream tracking ideas.
* Did bi-weekly Android upstreaming subteam email
=== Plans ===
* Haven't gotten much feedback recently, so I'm planning to submit
volatile range code for inclusion. This likely will get detractors to
come out of the woodwork. But hey, maybe I'll get lucky and it will
just go in?
* See if Rafael's userland wakelock api can be readied for 3.5
=== Issues ===
* NA.
== Linus Walleij linusw ==
=== Highlights ===
* Brought pending ux500 GPIO and pinctrl fixes forward. I have
a patch set with all internal changes from ST-Ericsson that
will be mailed off today. This is a prerequisite for the ux500
pinctrl work.
* Sent pull request for ux500 fixes for the -rc series to ARM SoC,
Olof @lixom has pulled it in.
* Reviewed a patch-storm from Lee Jones. Keeps me on the
move that guy :-)
* Finalized NO_IRQ removal issues and irq_domain migration for
the FPGA IRQ controller in the ARM Integrator and Versatile.
Patch is in Russell's patch tracker.
* Wrote four patches to the PL190 VIC due to bugs found during
the FPGA IRQ conversion. One makes the VIC respect the mask
of valid interrupt sources, one uses the map iterator, one bumps
the U300 IRQ list and one bumps the Nomadik IRQ list, both to
avoid using IRQ 0 which is now "NO_IRQ".
* Discussing power domain issues. Now on the I2C controller in
ux500. It looks like the maintainers want a centralized approach
to power domains, not distributed.
* Proposed patches to delete support for the obsolete DB5500
ASIC. Need to be rebased to a patch from MFD before it can
be pulled into ARM SoC.
* Booked hotel for Linaro Connect 2012.2
=== Plans ===
* Send pinctrl fixes to Torvalds.
* Review incoming pinctrl patches.
* Convert ux500 (gpio-nomadik) to pinctrl
for the kernel 3.5 timeframe.
* 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.
* Presentation for a dept. here about the platform perimeter
from the ESC two weeks ago. Seems useful for getting some
news in v3.4+. Today actually!
=== Issues ===
* Too much internal fuzz and advisory for different internal
projects have been a bit stressful, so I dropped off IRC for
that reason. The people visiting me in person are distracting
enough as it is. I will currently only use IRC when working from
home. This is one of the few environmental actions I can take
to get some focus from time to time.
Thanks,
Linus Walleij
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Submitted initial device tree support patches for Exynos5 Rev1.0.
* Prepared initial device tree support for SPI controller driver. This will
be submitted after additional testing.
=== Plans ===
* Complete device tree support for SPI controller driver.
* Rework combiner and wakeup interrupt controller device tree patches.
* Start with device tree support for Samsung pin-ctrl driver.
=== Highlight ===
* Reviewed common clock bindings from Rob Herring, and raised concern
on multiple clock outputs support and the question on how the entire
clock tree will be represented in the combination of clock driver
and device tree.
* Converted mach-mxs clock to common clk, and waiting for a stable
branch with all recent fixup/cleanup integrated to post the patches.
* Discovered a couple of bugs existing in common clk and previous imx6
porting during mach-mxs porting and testing. Sent fixing to Mike and
Sascha respectively for them to integrate.
* Reviewed the v6 of pwm framework series and tested it with mxs pwm
backlight drivers.
* Fixed the gpmi-nand breakage caused by dma cookie series in the way
that Russell suggested, enabling dma channel in issue_pending call.
* Reviewed DA9052 mfd and regulator device tree support from Paul Liu.
* Reviewed a couple of imx6q dts patches from Fabio, including the
initial SabreSD dts file.
--
Regards,
Shawn
=== Highlights ===
* Resolved the volatile persistence issue, and finally took a crack at
resolving the calling vmtruncate_range from a shrinker lockdep problem.
Sent out another revision (v7) of the volatile range code to lkml.
* Notified Andrey about my rebased 3.4-rc1 androidization patch set, and
immediately afterwards the Google developers released their own. Did
some basic testing and mirrored it out for 12.04. Tixy pointed out a
missing patch and I re-added it.
* Pinged Rafael and Arve about the reworked userland wakelocks code.
Ends up the userland wakelocks api is not reworked, Arve's just removed
the dependencies on the wakelock core, and that there are still
outstanding issues blocking upstream w/ the existing implementation.
Rafael's userland wakelock implementation is likely the future, but
needs further work/testing.
* Ran Android upstreaming subteam call
=== Plans ===
* Punted on a few community issues this week, so I'll likely need to
revisit them.
* Read up on sysrq-t and why its holding irqs off for very long periods
of time.
* See what feedback I get from volatile range, and if its minimal, drop
the RFC and submit it for inclusion.
=== Issues ===
* NA.
=== Pinctrl ===
* sent one pinctrl core patch to improve error checking
* sent out pinctrl-imx core driver patch with mux and config support for
review
* sent out pinctrl-imx6q driver patch for review
=== Plan ===
* add gpio support for pinctrl-imx core
* start to convert imx drivers to use pinctrl subsystem
== Linus Walleij linusw ==
=== Highlights ===
* I got Linux v3.4-rc2 to boot on Snowball and HREF500 after submitting
a bunch of patches fixing some boot problems. Now I have a testbed for
doing pinctrl on ux500.
* Applied a bunch of pinctrl patches, full migration of Tegra to pinctrl
and bug fixes from Dong Aisheng.
* Finalized U9540 basic support patch on top the -rc2 tag for v3.5.
* Looked at some NO_IRQ removal issues and irq_domain migration for
the FPGA IRQ controller in the ARM Integrator and Versatile. Cooking
a patch after some review from Russell.
* Discussing power domain issues.
* Booked and confirmed tickets to Connect 2.12 in Hong Kong.
=== Plans ===
* Send pinctrl fixes to Torvalds.
* Send ux500 fixes to ARM SoC.
* Review incoming pinctrl patches.
* Convert ux500 (gpio-nomadik) to pinctrl
for the kernel 3.5 timeframe.
* 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.
* Presentation for a dept. here about the platform perimeter
from the ESC two weeks ago. Seems useful for getting some
news in v3.4+.
=== Issues ===
* N/A
Thanks,
Linus Walleij
== Omar Ramirez <omarrmz> ==
=== Highlights ===
* Working on device tree for mailbox:
Find a kernel that works with DT for pandaboard (OMAP4):
- k3.4-rc1 doesn't recognize DT blob, k3.3 DT panics at boot.
- DT has to be appended to zImage.
Find a DT uboot:
- secretlab.ca uboot doesn't have usb support for panda, having
problems with fatload and mmc.
- linaro uboot has problems recognizing dt blob in memory (bootm
${kern} - ${dtb}; doesn't work properly).
* Sent "round 2" patches for the agitator, now merged.
=== Planned ===
* debugfs interface for big.LITTLE to know which cluster is being used.
* Add independent thread switching to the agitator.
On 2 April 2012 11:14, Omar Ramirez Luna <omar.luna(a)linaro.org> wrote:
=== Time off ===
Apr 6th Holiday
Regards,
Omar
== Linus Walleij linusw ==
=== Highlights ===
* NONE: I've been on vacation until yesterday. But I sent this report at
Deepaks request. :-)
=== Plans ===
* Expect next report on april 13th
* Review incoming pinctrl patches.
* Prepare to convert ux500 (gpio-nomadik) to pinctrl
for the kernel 3.5 timeframe.
* 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
=== Highlights ===
* Reviewed pwm framework v5 from Thierry Reding, and added mxs-pwm
support on top of it.
* Tested and acked patch "factor out dynamic amba device allocator"
from Linus.W
* Sent a patch to rename uart and fec device tree nodes to stop them
being bad examples (complained by device tree maintainer for several
times)
* Tested patch "Remove AMBA level regulator support" from Mark Brown
* Sent imx6 common clk patches, and he integrated it into the whole
imx common clk series. Waiting Mike's core fixup for rebasing and
post.
* Converting mach-mxs clock to common clk.
--
Regards,
Shawn
=== Venkatraman S <svenkatr> ===
=== Highlights ===
* Sent out couple of patches for UFSHCD driver; reported another issue
* Created feature branches for UFS & eMMC for 12.04
* Rebased OMAP MMC fixes for 3.4-rc2
* Develop MMC abort interface for foreground HPI
(Had a short work week due to some medical emergency)
=== Plans ===
* Received JIG board from Saugata - need to test power off notify and
trim/discard patches for eMMC4.5
* More work on HPI stress testing / plan to post RFC patches to linux-mmc
=== Misc ===
* Will be off on Apr 16th
Hi all,
This small patch set fixes a bug in the vmevent core, plus makes the
vmevent-test buildable w/o unneded SDL library.
Plus, we add a new 'cross' event type: the event will trigger whenever
a value crosses a user-specified threshold. It works two-way, i.e. when
a value crosses the threshold from a lesser values side to a greater
values side, and vice versa.
We use the event type in an userspace low-memory killer: we get a
notification when memory becomes low, so we start freeing memory by
killing unneeded processes, and we get notification when memory hits
the threshold from another side, so we know that we freed enough of
memory.
The patches are against
git://github.com/penberg/linux.git vmevent/core
Thanks!
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
=== Highlights ===
* Did some extra testing and found a few bugs in the volatile range
code. Fixed those up and sent it out to lkml.
* Finished a second pass at rebasing the AOSP 3.3 tree to 3.4-rc1. Needs
testing then I will send to Andrey.
* Handled some community clocksource issues around long irqoff periods
* Quite a bit of discussion on linaro-dev about the config fragment tree
and what the workflow should be with it.
* Merged a bunch of config fragment patches from Tixy and Tushar
* Got pulled into internal customer support issue.
* Wrote up a rypple review
* Wrote up talk proposal for plumbers
* Reviewed Anton's ulmkd draft mail
* Did weekly Android subteam mail
=== Plans ===
* Hit some ackward issues w/ the fadvise volatile work. Need to read
some more VM code and maybe ask for some help from VM friends.
* Do some testing w/ my 3.4-rc1 based android patch set & send out.
* Read up on sysrq-t and why its holding irqs off for very long periods
of time.
=== Issues ===
* NA.
=== Pinctrl ===
* Reviewed pinctrl core dt binding patches
Merged into pinctrl subsystem by Linus Walleij.
* sent mx28 basic dt support patch.(Merged by Shawn)
* add dt support for pinctrl-imx driver based on common dt binding.
The mux part was done. The config and gpio part were still ongoing.
* sent two pinctrl core fix patches.
=== Plan ===
* complete pinctrl-imx driver based on dt in next week including config
and gpio support.
== Rajendra Nayak <rnayak> ==
=== Highlights ===
* Worked mostly on OMAP2/3 common clk data generation
using python. Thanks to Paul Walmsley who did a perl script to
convert C99 structs to JSON format, which allowed me to use
python to reconvert from JSON to the common clock format.
Fixed some issues around OMAP4 common clk scripts.
* Working on a series to get rid of the clk->clkdm association
for OMAP2/3. This greatly helps reduce the data size of OMAP2/3/4
clock data when converting to common clk.
=== Plans ===
* Continue on pending issues with the script to generate OMAP2/3 common
clk data.
* more work on getting rid of clk->clkdm association.
=== Misc ===
* Will be off 2 days next week. April 9th and April 10th.
Hi Eric,
while testing the Quick Start Board, I quickly tried several kernel
built from git://git.linaro.org/bsp/freescale/linux-linaro.git
- lt-3.2-imx5 : needs some fixes to build, boots but X fails to run
(with 11.09.01 BSP's userland on the VGA output)
- lt-3.2-imx6: needs some fixes to build, fails to boot
- lt-3.1-2011.12: don't remember the result
- rel_imx_2.6.38_12.01.01 : fails to boot
I can provide log & more details for each configuration later if needed.
The instructions on the Wiki
( https://wiki.linaro.org/Boards/MX53QuickStart ) seems outdated.
Is this platform still supported by Linaro ?
What is the Freescale Landing team's recommended tag to use to test
linux-linaro on iMX53QSB ?
What are the recommended GPU & VPU libraries to use to get the best of
the i.MX53 with linux-linaro ?
Thanks
Eric
--
http://eukrea.com/en/news/104-2012
I meant week: Mar 26 - Apr 1.
On 2 April 2012 11:14, Omar Ramirez Luna <omar.luna(a)linaro.org> wrote:
> == Omar Ramirez <omarrmz> ==
>
> === Highlights ===
>
> * Working on v2 of the agitator, so far:
> - Cleanup comments and minor bugs.
> - Print of execution time on exit, also triggered when catching
> SIGINT and SIGTERM.
> - Added independent cpu switching along with synchronous switching
> (for all cpus).
> - Added random switching, option to specify seed and the limit to
> randomize the time intervals.
>
> * Sent omap iommu fix for scenario: domain destroy with devices attached.
>
> === Planned ===
>
> * debugfs interface for big.LITTLE to know which cluster is being used.
>
> * Add independent thread switching to the agitator.
>
> Regards,
>
> Omar
== Omar Ramirez <omarrmz> ==
=== Highlights ===
* Working on v2 of the agitator, so far:
- Cleanup comments and minor bugs.
- Print of execution time on exit, also triggered when catching
SIGINT and SIGTERM.
- Added independent cpu switching along with synchronous switching
(for all cpus).
- Added random switching, option to specify seed and the limit to
randomize the time intervals.
* Sent omap iommu fix for scenario: domain destroy with devices attached.
=== Planned ===
* debugfs interface for big.LITTLE to know which cluster is being used.
* Add independent thread switching to the agitator.
Regards,
Omar
=== Highlights ===
* Sent a series to clean up basic clks of common clk framework, and
Mike will integrate them into his fixup branch.
* Sent a patch to fix the issue that audio driver only works with SSI1
on imx5. It assigns dma peripheral type according to bus topology.
(Merged by Mark)
* Sent a couple of patches to fix sgtl5000 MIC Bias power and add
audio routing support for imx-sgtl5000 machine driver to get capture
functional. (Merged by Mark)
* Tested patch "ASoC: sgtl5000: Convert mic bias to a supply widget"
from Mark with imx-sgtl5000.
* Added basic clock management for fsl_ssi driver. To make it compile
for both powerpc and imx, the powerpc dummy clock API needs to be
built in. Sent a patch to linuxppc-dev list and waiting for comment.
* Reviewed and merged anatop-regulator imx6q dts patch from Paul.
* Reviewed and merged basic imx28 DT patch (booting into console with
nfsroot) from Aisheng.
* Tested v3.4-rc1 on imx28 and imx6q, and sent a couple patches to fix
amba probe failure, section mismatch warning.
--
Regards,
Shawn