=== Highlights ===
* I can't take credit for it, but wakelocks landed in 3.5!
* Continued reworking the volatile range code to use fallocate
* Integrated Hugh Dicken's tmpfs fallocate hole punch changes into my
fallocate volatile code.
* Got the fallocate volatile patchset functioning and cleaned up, then
submitted to lkml for review.
* Reviewed and discussed community leapsecond improvement patches
* Pushed a few ntp cleanups to tglx
* Preped and ran bi-weekly android upstreaming subteam call
* Took a first pass at forward porting the AOSP tree to early 3.5-rc
* Chased down (with Arnd's help) mmc issue on Panda
* Reported hdmi issue on panda
* Reported tty_lock lockdep issue to lkml
=== Plans ===
* Discuss and integrate any review feedback into volatile range code.
* Update the 3.5 Android fwdport tree
* Test upstreamed wakelocks w/ Android environment.
=== Issues ===
NA
== Linus Walleij linusw ==
=== Highlights ===
* Sent pull requests to Torvalds to merge the pinctrl subsystem
updates for the v3.5 merge window, he accepted it and merged
the stuff.
* The ARM SoC portions of Ux500 including basic U9540 support
and Ux500 pin control was pulled in by Torvalds.
* Investigated a ux500 boot failure on Torvalds kernel, detected
last week in the linux-next tree, found that it was
caused by two orthogonal approaches to do pin control on the
PL011 UART. Coded a fix and sent out, ACK from Shawn Guo,
waiting for Greg to pick this into the TTY tree after the merge
window closes.
* Worked on a pinctrl presentation for Linaro Connect.
=== Plans ===
* Vacation:
23 june -> 30 june
9 july -> 3 august (preliminary)
* Prepare for travel to Linaro Connect.
* 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 ===
* N/A
Thanks,
Linus Walleij
Hi all,
A brand new v4:
- Per Kees Cook's comments, the patches no longer remove an automatic
updates feature, but instead make the it configurable; plus disable
it by default (in a separate patch);
- Fixed some bugs noticed by Colin Cross;
- Documented new continuous ramoops-console log behaviour (also
noticed by Colin Cross).
In v3:
- Rebased on top of current staging-next;
- The series are getting bigger. This is partly because we now support
different persistent zone sizes for oops records and console log,
per Colin Cross' request.
And I believe the code is now more manageable for further enhancements
(e.g. if we'd want to add other message types, e.g. tracing);
- Addressed Kees Cook's comments on the unlinking matters;
- Removed automatic updates support. Please see the last patch
description for rationale;
- A new fixup for pstore/inode, just getting rid of a sparse warning.
In v2:
- Updated documentation per Colin Cross' comments;
- Corrected return value in ramoops_pstore_write() (noticed by Kees Cook);
- Fixed large writes handling in pstore_console_write(), i.e. when
log_buf write is larger than pstore bufsize. Also Noticed by Kees Cook.
And a boilerplate for the series:
Currently pstore doesn't support logging kernel messages in run-time,
it only dumps dmesg when kernel oopses/panics. This makes pstore
useless for debugging hangs caused by HW issues or improper use of HW
(e.g. weird device inserted -> driver tried to write reserved bits ->
SoC hanged. In that case we don't get any messages in the pstore.
This series add a new message type for pstore, i.e. PSTORE_TYPE_CONSOLE,
plus make pstore/ram.c handle the new messages.
The old ram_console driver is removed. This might probably cause
some pain for out-of-tree code, as it would need to be adjusted...
but "no pain, no gain"? :-) Though, if there's some serious resistance,
we can probably postpone the last two patches.
Thanks!
---
Documentation/ramoops.txt | 14 ++
drivers/staging/android/Kconfig | 5 -
drivers/staging/android/Makefile | 1 -
drivers/staging/android/ram_console.c | 179 --------------------------
fs/pstore/Kconfig | 7 +
fs/pstore/inode.c | 5 +-
fs/pstore/platform.c | 49 ++++++-
fs/pstore/ram.c | 228 ++++++++++++++++++++++++++-------
fs/pstore/ram_core.c | 108 +++-------------
include/linux/pstore.h | 1 +
include/linux/pstore_ram.h | 22 +---
11 files changed, 272 insertions(+), 347 deletions(-)
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
== Highlights ==
* Found and fixed a few bugs in persistent_ram and pstore,
the fixes are already merged;
* Consolidated persistent_ram and ramoops, added ECC suppport
for ramoops. This is now called 'a generic pstore RAM backend'.
So persistent_ram is moved out of staging/android/ directory,
and is considered useful for the rest of (i.e. non-Android)
world. The backend will handle dmesg, console and tracing
messages. The consolidation patches are already in linux-next,
and I guess they're heading v3.5.
* Sent out a bunch of patches that add console support for pstore
(this is ram_console replacement). This is probably v3.6 material.
* Started looking into adding tracing support to pstore.
* Got a somewhat intense comments on the vmevents subsystem. The
bad news is that, according to the comments, vmevent is in not
a good shape: it is not generic enough to make -mm folks happy.
But the good news is that -mm folks finally looked at the code
itself, and we know (to some degree) what is exactly wrong with
it. So, hurrah!
* Not much progress on AOSP and ulmkd integration. Just built
Android images to work with on my current laptop, but so far
didn't look into build system itself.
== Plans ==
* Continue work on tracing support for pstore.
* Resume work on vmevents, have some patches ready by the
end of this week.
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
=== Highlights ===
* Sent a couple of patches to add gpio-range support for pinctrl-mxs
driver. Dong commented a bit on that and came up with a proposal
to support it at pinctrl core level.
* Sent a patch to fix gpio-generic driver on shadow variable
initialization. Grant picked it up for v3.5.
* Added initial support for imx6dl support. As it's a derivative of
imx6q and highly compatible with imx6q, the effort is only about
dts tweaking for the initial support.
* Reviewed the platform part of the imx-usb series from Richard and
and tested it on imx28 with brand new DT support. With a few lines
of clk lookup and dts changes, the driver tested on imx6q beforehand
starts working nicely for imx28.
* Collected a number of fixes on imx platform pinctrl.
--
Regards,
Shawn
Hi all,
Here comes v3:
- Rebased on top of current staging-next;
- The series are getting bigger. This is partly because we now support
different persistent zone sizes for oops records and console log,
per Colin Cross' request.
And I believe the code is now more manageable for further enhancements
(e.g. if we'd want to add other message types, e.g. tracing);
- Addressed Kees Cook's comments on the unlinking matters;
- Removed automatic updates support. Please see the last patch
description for rationale;
- A new fixup for pstore/inode, just getting rid of a sparse warning.
In v2:
- Updated documentation per Colin Cross' comments;
- Corrected return value in ramoops_pstore_write() (noticed by Kees Cook);
- Fixed large writes handling in pstore_console_write(), i.e. when
log_buf write is larger than pstore bufsize. Also Noticed by Kees Cook.
And a boilerplate for the series:
Currently pstore doesn't support logging kernel messages in run-time,
it only dumps dmesg when kernel oopses/panics. This makes pstore
useless for debugging hangs caused by HW issues or improper use of HW
(e.g. weird device inserted -> driver tried to write reserved bits ->
SoC hanged. In that case we don't get any messages in the pstore.
This series add a new message type for pstore, i.e. PSTORE_TYPE_CONSOLE,
plus make pstore/ram.c handle the new messages.
The old ram_console driver is removed. This might probably cause
some pain for out-of-tree code, as it would need to be adjusted...
but "no pain, no gain"? :-) Though, if there's some serious resistance,
we can probably postpone the last two patches.
Thanks!
---
Documentation/ramoops.txt | 14 ++
drivers/staging/android/Kconfig | 5 -
drivers/staging/android/Makefile | 1 -
drivers/staging/android/ram_console.c | 179 --------------------------
fs/pstore/Kconfig | 7 +
fs/pstore/inode.c | 5 +-
fs/pstore/platform.c | 70 +++++-----
fs/pstore/ram.c | 228 ++++++++++++++++++++++++++-------
fs/pstore/ram_core.c | 109 ++++------------
include/linux/pstore.h | 1 +
include/linux/pstore_ram.h | 22 +---
11 files changed, 269 insertions(+), 372 deletions(-)
--
Anton Vorontsov
Email: cbouatmailru(a)gmail.com
=== Highlights ===
* Pushed a handful of cleanup patches from the linaro-android tree to
AOSP and got them merged into the Android tree
* Went on vacation from 5/9 -> 5/16
* Got back from vacation, managed to churn through most of my email.
* Updated the linaro-android-3.4 tree w/ the latest bits from the AOSP tree
* Started discussions about integrating android-3.4-compat tree w/
linaro-android-3.4
* Met with Deepak and started generating details for Android upstreaming
session at connect
* Synced with Rafael about wakelock patch status for 3.5
* Synced with Anton about his recent ramconsole work
=== Plans ===
* Get back to falloc volatile range rework
* Address Hugh Dickins' ashmem patch
* Prep some time related patches for 3.5 merge window
* Further prep for remote Linaro Connect attendence
=== Issues ===
NA
=== Highlights ===
* reviewed mxs pinctrl gpio support patch
* sent pinctrl mx5(mx51/mx53) v2 patch, merged by Linus.
* pinctrl gpio standard common binding support
Sent out v1/v2 patch. Already got some agreement on the standard binding
way after
some discussion with Stephen Warren.
* sent out a few pinctrl core fix and clean up patches
* Reviewed some imx pinctrl converting patches.
=== Plan ===
* complete standard pinctrl gpio dt binding.
* pinctrl per bin based config in the same group investigate and implement
==== highlights ====
1. UBUNTU Distro setup on Laptup,
This took approximately 1.5 days including necessary setup
- Extended support for Raj on UBUNTU Setup
2. New staff tasks:
Found following issues while using:
2.1 Linaro Calender:
Could not get the link for "Kernel Working Group"
2.2 Thunderbird Mail setup:
https://wiki.linaro.org/Internal/Process/ThunderbirdSetup
Setup instruction conveyed in the URL above does not help
3. Device Tree:
- Obtained review comments from Lee Jones regarding platform structure
support for ab8500 device entries Implementing the same.
- Found issues in exporting platform data structure from board
file to driver,
debugging / root-causing the issue.
4.Support
- Looked into the issue highlighted by Mathieu on Uboot with DT,
Could not repro kernel panic issue as mathieu is observing.
- Assisted appala (Newly joined member) for on boarding tasks
===== Plan ====
1. Continue to support mathieu
2. Continue debugging platform structure support and complete
==== Issues ====
== Linus Walleij linusw ==
=== Highlights ===
* Ux500 pinctrl has landed in the ARM SoC tree.
* Merged:
- i.MX51 pinctrl driver (Dong Aisheng)
- i.MX53 pinctrl driver (Dong Aisheng)
- Various pinctrl fixes (Dong, Shawn, Stephen & friends)
* Closed the pinctrl tree for the imminent merge window.
* Reviewed some incoming GPIO patches in an attempt to
offload Grant.
* Investigated a ux500 boot failure on -next, not sure of what
is causing this. (Reported by Lee Jones.)
* Worked on a pinctrl presentation for Linaro Connect.
=== Plans ===
* Prepare for travel to Linaro Connect.
* 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 ===
* This was a short week in Sweden, out of office
thursday+friday.
Thanks,
Linus Walleij
