== 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