== Linus Walleij linusw ==
=== Highlights ===
* Torvalds accepted and pulled in the 31 patches that were
accumulated for pin control last kernel cycle.
* Bug fixes for various ux500 Daniel Lezcano (PM) on
linux-next were applied by Russell and pulled into the
mainline tree with the other ARM patches.
* Fixed a build bug in SA1100 caused by the new dynamic
clksrc stuff. (Found in kisskb.)
* Updating Blueprints and such administrativa.
* Merged the PXA pin control (muxing only) driver by
Haoijan, it's a real nice driver and good example for
others.
* Ux500 mainlining since too little is happening:
- Prepared a set of PRCMU update patches.
- Helping our ALSA SoC authors to get started to get their
stuff upstream.
* Signed GPG keys for Sjur Brændeland and
Henrik Rydberg (the input/touch maintainer).
=== Plans ===
* New pin config table patch due ASAP. I am working on this.
There is a per-pin and per-group configuration call but this
does not suffice: developers want tables of configurations
to be handled by the pin controller core as well.
* Various pinctrl patches being applied and discussed among them
dummy pinmuxes akin to dummy regulators, we need to
see if this is a good idea or not.
* Prepare conference presentations for Android builders and
Embedded Linux Conference.
* 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 ===
* Nobody is mainlining Ux500, and being a subarch
maintainer I feel bad about not being able to do much about
it due to time shortage. This is creating problems for others
since core functionality is missing which makes other
subsystems suffer and other stuff cannot be mainlined. :-(
Thanks,
Linus Walleij
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Submitted patch for a new lcd power control driver with device tree support.
This is required for controlling power to lcd panel that do not use a serial
command interface or memory mapped io interface.
* Submitted device tree support patch for generic power domains.
* Submitted device tree support patch for Samsung display controller.
* Not much progress on the Samsung pinmux/pinconfig driver.
=== Plans ===
* Complete device tree support patch for Samsung SPI controller.
* Re-start work on Samsung pinmux/pinconfig driver.
=== Device tree ===
* Reviewed imx pinctrl patch series from Aisheng, and had some
extensive discussion on how we should add DT binding for pinctrl
drivers.
=== imx6 maintenance ===
* Collected a number of imx tty/serial patches and sent them to Greg
for 3.3 merge window.
* Collected a couple of imx6 PM fixup patches from Eric Miao
* Reviewed imx6 IRAM patch from Jason Chen
* Reviewed imx6 anatop regulator bypass patch from Jason Chen
* Reviewed imx6 suspend patches from Jason Chen
* Reviewed cpufreq patch series from Richard Zhao
* Reviewed imx-sdma fixup patches from Richard Zhao
* Reviewed imx6 audio board level patches from Richard Zhao
* Sent a patch to fix !SMP build for imx6
* Sent a patch to fix v7_invalidate_l1 by adding I-Cache invalidation
* Reviewed irqdomain fixup patches from Thierry Reding
=== mxs maintenance ===
* Sent the clk-prepare series to fix mutex locking issue while moving
one step towards common-clk frame work
* Sent a patch to use CHIPID register to detect soc between imx23 and
imx28, so that we do not need to touch uncompress.h and mxs.h every
time a new board support is added. (Thanks for Wolfram Sang for
the suggestion)
* Managed to send 'Bluegiga APX4 Development Kit' board support from
Lauri Hintsala to arm-soc. Not sure if it will be in for 3.3 merge
window though.
* Tested the patch from Fabio Estevam adding audio support into
mxs_defconfig
=== Misc ===
* Sent a random u-boot patch on common/image.c to align usage of
fdt_high with initrd_high (come along with playing fdt_high on
imx6)
--
Regards,
Shawn
=== Highlights ===
* Couple of RTC patches I pushed in before the holidays were causing
regressions, so got them reverted and worked to revise the fixes with
the patch authors.
* Synced with Greg KH and Tim Bird and submitted talk on Android kernel
patch status for ELC
* Pinged Google devs on still pending actions from Nov meeting.
* Sent a few iterations of the patches to evdev to allow monotonic
timestamps to be used (required for ICS). Made some requested
modifications by the upstream maintainer. Didn't get any objections.
Pinged Google devs to try to get feedback prior to submitting (hopefully
for 3.3 - which might allow ICS to run/limp on 3.3 without any
additional patches)
* Pinged Andrey to see how the kernel maintenance handover is going.
* Wasted a good chunk of a day sorting out some sort of
hardware/firmware network flakiness with one of my x86 test machines.
=== Plans ===
* Try to catch up on monthly status stuff for Mounir
* Sync with Anton and get Android sub-team status stuff sorted
* Hopefully sort out the evdev bits and get them queued.
* Look into shmem_mmap alternative to using shmem_set_file in ashmem.
* More fadvise volatile work
=== Issues ====
* None.
== Dave Martin <dmart> ==
=== Activity Summary ===
* Various patches accepted by Russell while I was on holiday.
* This week mostly spent on catch-up, and reading up on the ARM
Virtualisation Extensions.
=== Plans ===
* Possibly post driver changes to replace NO_IRQ with a test compatible
with the "0 means no irq" convention.
* Sync with Deepak, Pawel etc. about what needs to be done for the
remaining DT bits (bindings, drivers)
* Finish and push GNU build changes for the switcher code.
=== Work Items ===
no update
=== Absences ===
none planned yet
== Dong Aisheng <DongAisheng> ==
=== Highlights ===
* Add basic DT support for pinmux-imx core driver (tested on MX6Q)
* Send out the patches for adding DT binding of pinmux mappings for pinctrl
core.
Received comments from Stephen and fixed a few issues, still on
discussing
the better way to bind pin maps due to some DT limitations.
Found a possible way which is similar as regulator and clock core code
do.
=== Plans ===
* Will try the way as regulator and clock framework to do pinmux map
binding.
=== Travel/Time Off ===
* Holiday vacation 1/1/12 - 1/3/12
* Holiday vacation 1/21/12 - 1/29/12
* Connect + ELC 02/05-02/18
== Saugata Das sdas ==
=== Activity Summary ===
* Published data tag patch
* Performed SD, MMC access pattern study during video recording and
USB mass storage
=== Plans ===
* Context ID implementation and internal review
=== Issues ===
* Not able to validate MMC-4.5 patches due to lack of MMC-4.5 device
on any board at my end
== Anton Vorontsov <cbou> ==
It seems that I haven't yet used to the weekly activity reports, but from
now on I'll try to set it right.
=== Highlights ===
* Got a new toy (almost a Christmas present): a pandaboard. :-) Played with it
a little bit: tried Linaro (w/ a serial console, no GUI), various kernels,
including linux-next.
* In addition to the pandaboard, set up a Linaro QEMU environment for quick
tests; especially useful when not having access to a real HW;
* Finally felt confident enough to send out my thoughts on the memory killer;
* From the discussion it seems that:
- Now mem_cg is a lot better on memory usage, but still not enough for
embedded use;
- cgroups has a big impact on the kernel size image;
- cgroups impacts performance in a bad way (using not so synthetic hackbench):
http://lkml.org/lkml/2011/12/21/487
(purely synthetic tests, like cyclictest, do not show any downgrade);
- there are still some demand for the dedicated memory notifiers;
So, it seems that mem_notify reincarnation is inevietable.
=== Plans ===
* I haven't yet able to boot Linaro/Android on the pandabord, need a HDMI-DVI
cable, I'll get it soon; I've tried to boot Android on the QEMU/VExpress,
but it took ages (4+ hours) only to get it to the welcome screen (I was
trying on my travel x120e notebook, 1.6 GHz. But I will try on a more
powerful machine soon, just out of curious).
* I'll take some side project, also Android related. This is to have some
"rest" from the lowmemory notifiers/killer;
* Address some community comments on the current lowmemorykiller driver;
* Start implementing "low memory notify" driver.
=== Highlights ===
* Got a "non-objection" from Arve for pushing the ashmem patches to
staging. Wanted an Ack, but he said he wouldn't have time to look at
them until after the holidays, so I should go ahead and post them. Will
sync with him after the holdiays to make sure nothing in staging looks
out of place. The good news though is that ashmem is in staging, and
that allows us to be very close to a functional ICS with the vanilla
mainline kernel.
* Sent Android evdev patch to input list for feedback. Got a mail from a
ChromeOS guy who had tried to push a similar patch and ran into ABI
issues (legacy applications expect CLOCK_REALTIME timestamps, and
Android expect CLOCK_MONOTONIC). This is problematic because it means
Android ICS depends on breaking Linux' input ABI semantics slightly.
Generated a patch to allow the different ABI semantics to be selectable
via an IOCTL and sent a rough draft to list for feedback. Spent some
time reworking and improving the draft so that I can resend after the
holidays.
* Created a new blueprint to cover the work above:
https://blueprints.launchpad.net/linux-linaro/+spec/android-evdev-upstreami…
* Sent links to Andy's stgit workflow and code to the Android team.
Hopefully they will be able to review it over the break.
* Bunch of discussion around the wider Android upstreaming effort Tim
Bird is trying to organize.
* Piped in somewhat on the Android Logger patch discussion Tim started.
* Reworked fadvise volatile patch to use its own LRU and shrinker
methods which is falling back to being more similar to Android's ashmem.
Still having some locking difficulties to figure out between allocation
and freeing paths.
* Had initial meeting with Anton and made sure he had enough work on his
plate.
=== Plans ===
* Holidays. Will be back in the new year.
* Look into shmem_mmap alternative to using shmem_set_file in ashmem.
* More fadvise work
* Try to sort out something for an ELC talk
* Need to sort out plans dealing with some scheduled extended downtime
for my main development box next year.
=== Issues ===
* None.
== Deepak Saxena <dsaxena> ==
=== Highlights ===
* Had kick off meetings for pinmux and storage sub teams
* Released Linaro 11.12 kernel
* Worked up updating and cleaning up KWG blueprints for 12.01 work
=== Plans ===
* Work on kernel wiki page updates
* Distribute monthly team highlights
* Connect session planning
* Cleanup remaining unfinished KWG roadmap cards
=== Travel/Time Off ===
* Will be out of contact mid-day Tuesday due to veterinary appointment
* Holiday vacation 12/24/11 - 01/09/12
* Connect + ELC 02/04-02/18
== Venkatraman S svenkatr ==
=== Highlights ===
* Review of Data Tag implementation patches
* Review and forward porting of eMMC HPI implementation for data path.
(I need to break this down to changes for each layer in MMC stack)
* Continued study on deadline scheduler and characterization.
=== Plans ===
* eMMC HPI forward porting
* Draft UFS validation plan
== Saugata Das sdas ==
=== Activity Summary ===
* Prepared data tag patch. Internal review ongoing
* Continued review and follow up on MMC-4.5 patches within community.
Helping on cache control, power class selection, HS200 patches.
=== Plans ===* Study the MMC, SD block access pattern during "write
intensive" use cases like video recording and USB mass storage
transfer.
=== Issues ===* Not able to validate MMC-4.5 patches due to lack of
MMC-4.5 device on any board at my end
=== Highlights ===
* Reworked ashmem patches that I've preped for staging per Arve's
feedback and resent the queue for acks. As soon as I get an ack, I'll
fold the patches down and send to Greg.
* Sent a small and simple evdev patch from Android to input maintainer
for feedback. This is the one patch outside of the ashmem patches I have
queued for staging that allows ICS to run on a staging-next kernel.
* Reworked the Android alarm-timer driver so it would be ready for
possible inclusion into staging. Its a little more awkward because its
very dependent on wakelocks. Sent out for feedback to Android developers
and Greg.
* Synced with Greg and others on what remains in common.git that has the
potential to go into staging.
* Re-sent Rafael the split out Android wakelock queue.
* Re-adding CONFIG_SCHED_MC options to 3.2 based Linaro+Android kernel.
* Helped Jesse with some git usage.
* Queued two RTC fixes for 3.2 and sent them to Thomas.
* Discussed vdso clock_gettime(CLOCK_THREAD_CPUTIME,...) implementation
issues with some of the facebook folks. This took a tangent into larger
discussion about timekeeping items like future support for CLOCK_TAI and
other issues like improved leap-second handling.
* Got a mail from Tim Bird on setting up a wider Android upstreaming
effort, trying to get a handle on who all is doing what in the
community. Sent him updates on what the Linaro team is doing and
GregKH's staging tree plans. Plans for a meeting at Connect including
non-linaro folks working on these issues is in progress.
* Spent a little bit of time on the fadvise volatile patches, and ran
into some potential ugly locking issues that I need to resolve.
Considering falling back to the lru approach the ashmem patch uses.
=== Plans ===
* Hopefully get final ack from Arve on ashmem patches and push those to
Greg.
* Follow up on alarmtimer mending patches.
* Look into shmem_mmap alternative to using shmem_set_file in ashmem.
* More work on fadvise volatile implementation.
* Prep for the holidays
* Start actually acting as sub-lead for Kernel Android work (I've been
bad the last two weeks) and get a regular meeting planned.
=== Issues ===
* None.
== Linus Walleij linusw ==
=== Highlights ===
* Located and fixed a nasty ux500 iotable bug reported by
Daniel Lezcano (PM) on linux-next:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7233/1
* Located a clock drift problem on ux500 found by
Daniel Lezcano (PM) as well. Thinking about a patch...
* Various pinctrl patches being applied and discussed among them
dummy pinmuxes akin to dummy regulators, we need to
see if this is a good idea or not.
* Blueprints and stuff updates with assitance from Mounir
(thanks!) we're using pinctrl as some test
case for the process, which is both fun and painful.
* Reviewed Samsung and Freescale and PXA pinctrl
(mainly mux) implementations, it actually looks like these
drivers will be mainly a smooth ride.
* Discussed DT mappings to pin controllers again, now
Dong Aisheng is taking it a step further since he has a
clear idea on how this should work and will write and
document pinctrl bindings for Freescale, patches already
exist for iMX.6 this is looking real good.
* Ux500 mainlining since too little is happening:
- core ASIC patches and dropping prototype silicon patches
sent out.
- Helping our ALSA SoC authors to get started to get their
stuff upstream, some problem with the usual - clocks,
regulators, DMA, but it's looking OK.
* Helped Sjur Brændeland to get M7400 XSHM patches
into linux-next and will help him to establish a
k.org repository.
=== Plans ===
* Vacation 2011-12-19 thru 2012-01-06
Expect next report at the end of my first working week
2012-01-13.
* 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
- the HWMON stuff.
- DB8500 PRCMU updates
=== Issues ===
* Snowball/Igloo may need help with a USB issue, but
I won't be in any capacity to help them :-(
Thanks,
Linus Walleij
== Dave Martin <dmart> ==
=== Activity Summary ===
* Reviewing of Pawel's versatile express patches and related discussions
(steadily progressing -- there are a few issues to resolve, but the
series appears almost ready. Some issues came up when testing.)
* Reposted kconfig cleanup patches, responding to comments from various
people, and adding cleanup for CONFIG_SMP.
* Spent a bit more time on AMBA bindings.
=== Plans ===
* Propose AMBA driver changes to replace NO_IRQ with a test compatible
with the "0 means no irq" convention.
* Continue to miscellaneous outstanding DT issues (bindings, drivers)
forward.
=== Work Items ===
https://blueprints.launchpad.net/linux-linaro/+spec/kernel-versatile-boad-d…
* Agree/merge isp1760: DONE
* Agree/merge pata_generic changes: INPROGRESS
=== Absences ===
Christmas (2011-12-19 - 2012-01-03)
With the latest 3.1.5 merge linux-linaro-3.1 fails to build on Jenkins:
https://ci.linaro.org/jenkins/view/All%20CI/job/linux-linaro-3.1_panda-omap…
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
`oprofile_arch_exit' referenced in section `.init.text' of
arch/arm/oprofile/built-in.o: defined in discarded section
`.exit.text' of arch/arm/oprofile/built-in.o
`oprofile_arch_exit' referenced in section `.init.text' of
arch/arm/oprofile/built-in.o: defined in discarded section
`.exit.text' of arch/arm/oprofile/built-in.o
I originally saw this with my packaged kernel builds so checked the
unpackaged version to see if it was a config/sauce issue from
packaging.
3.1 or 3.2?
Android seems to be going with 3.2 judging by a pre-release version,
what about the kernel working group and Ubuntu?
And where do we find out about these things? Because I find it a bit too
late to not find out until the releases is done.
--
Tixy
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Submitted regulator device tree support patches for pmic block of max8997
* Submitted regulator support patches for platform-lcd driver.
* Submitted irq domain and device tree support patches for Exynos4
interrupt combiner.
* Submitted irq domain and device tree support patches for Exynos4
wakeup interrupts.
* Submitted device tree support patches for Exynos4 power domains.
=== Plans ===
* v2 of regulator device tree support patches for pmic block of max8997.
* v2 of regulator support patches for platform-lcd driver.
* v2 of irq domain and device tree support patches for Exynos4
interrupt combiner.
* Review the latest pin config patches and pinctrl dt discussion.
* Populate Exynos specific pinmux definitions in Samsung pinctrl driver.
=== Device Tree ===
* Sent v3 of mc13892-regulator device tree support series for a minor
document change. Hopefully this is the last version.
* Started looking into pinctrl DT binding discussion for the later
imx pinctrl DT support.
=== Consolidation and cleanup ===
* Reviewed imx pinmux initial support series from Aisheng
* Tested pinmux patch on imx6q
* Reviewed Rob's adding irqdomain for irq_chip_generic patch and
tested it on imx5 with some feedback and breakage report
=== Misc ===
* Reviewed fec fix-up patches from Lothar
* Reviewed mxs-mmc fix-up patches from Lothar
* Reviewed Fabio's patch adding uart wakeup support and tested
it on imx6q
--
Regards,
Shawn
== Rajendra Nayak <rnayak> ==
=== Highlights ===
* Working on making the pinmux/pinconf (which I initially got working
only on OMAP4) to work on all OMAPs. The challenge is to manage the
data size (for pins and pinfunc/pingrps) which is getting large.
For now passing data from platform code (till there is some
conclusion on how to pass data from DT)
* Did some work on moving leaf clocks to DT. Need more changes in
the way hwmod handles setting up early modules.
=== Plans ===
* Repost TWL regulator support after a rebase on top of the latest
i2c/twl series from Benoit.
* Continue work on pinmux/pinconf for OMAP and post patches for
common pinmux/pinconf supporting all OMAPs (with data in passed
from platform code)
* Continue working on moving leaf clock nodes to DT.
=== Misc ===
* Will be taking off the week before Xmas (19th to 23rd Dec) and work
through the Xmas week.
== Venkatraman S svenkatr ==
=== Highlights ===
* Created elevator API description and mapping document for CFQ and
deadline scheduler
https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0Ap8HyUkSzX2JdGFnQ…
*Generated iozone metrics for CFQ and deadline scheduler for comparison.
* Understanding the work completed on fs-block-allocation and try the
flashbench utility
* Synced up with Saugata on eMMC4.5 Context-ID and Data-Tag
implementation requirements
=== Plans ===
* Study of deadline scheduler and comparison with CFQ on random
workloads with flashbench
* Restart work on eMMC-HPI implementation - plan to post initial draft
by e/o December
* Study UFS and draft a validation spec for UFS
=== Highlights ===
* Synced with GregKH on plans for adding some android patches to
staging.
* Reworked Android ashmem patches so they could be included in staging.
Sent out for review to Greg and Android team. Got some feedback from
Arve, and am working to address his concerns.
* Worked out what other Android patches were necessary to get the
staging kernel up and running with ICS (luckily, its only one more patch
in addition to the ashmem changes).
* Starting looking at requirements to get Android alarm-timer driver
(and the pending patches I have to simplify the driver and make it use
the upstreamed posix alarm timer code) into staging.
* Sent mail to Andrey Konovalov with overview of the old linaro+android
kernel maintenance process, and my understanding of the new goals around
linaro kernel tree maintenance going forward.
* Due to the shortened schedule this month, released an initial 11.12
Linaro+Android kernel so there is something to work with while Andrey
ramps up to speed.
=== Plans ===
* Continue working to get ashmem patches for staging reviewed and acked
by Android team. Push resulting queue to Greg.
* Continue looking at android alarmtimer driver for staging. It requires
the wakelock patches, so either I cut out wakelocks or wait for some
form of wakelocks to go upstream.
* Look into what other bits from the Android patch set could possibly go
into staging.
* Address the SCHEC_MC option getting dropped from android defconfigs.
* Try to send the timekeeping locking changes to tglx.
=== Issues ===
* None.
== Saugata Das sdas ==
=== Activity Summary ===
* Continued review and follow up on MMC-4.5 patches with Samsung.
Helping on power OFF notify patch
* Studying the blueprint for file system block size > 4KB,
https://blueprints.launchpad.net/linux-linaro/+spec/vfs-larger-than-4k-bloc…
* Studying the blueprint for data tag and context ID,
https://blueprints.launchpad.net/linux-linaro/+spec/linaro-kernel-emmc4.5-c…
=== Plans ===
* Propose the data tag patch within next two weeks
=== Issues ===
* In order to use the Samsung 4.5 eMMC sample, we need to do hardware
modification, which needs specialised equipments. Will need sometime
to prepare the setup for verification of 4.5 patches.
== Dave Martin <dmart> ==
=== Activity Summary ===
* Reviewing of Pawel's versatile express patches and related discussions
(steadily progressing -- there are a few issues to resolve, but the
series appears almost ready. Some issues came up when testing.)
* Concluded that we should fix drivers to stop using NO_IRQ or assuming
NO_IRQ == -1 on an as-needed basis.
* Worked on some miscellaneous patches to do some Kconfig cleanup,
a couple of errata workarounds relevant to vexpress etc.
=== Plans ===
* Propose AMBA driver changes to replace NO_IRQ with a test compatible
with the "0 means no irq" convention.
* Repost l2x0 Kconfig cleanup patches along with patch to clean up
the dependencies of CONFIG_SMP.
* Continue to miscellaneous outstanding DT issues (bindings, drivers)
forward.
=== Work Items ===
https://blueprints.launchpad.net/linux-linaro/+spec/kernel-versatile-boad-d…:
* Document outstanding AMBA tree bindings: INPROGRESS
* Propose of/irq and/or AMBA driver changes to resolve NO_IRQ
iinterface mismatch between OF drivers and (currently breaking pata_generic on vexpress): INPROGRESS
* Post outstanding AMBA tree bindings upstream: TODO
=== Absences ===
Christmas (2011-12-19 - 2012-01-03)
== arm-soc tree ==
* merged 35 bug fixes for 3.2, now included in -rc5
* nagged subarch maintainers about sending stuff
* merged one feature branch (mxs/saif), the total number of branches for
3.3 is now 9, with 124 changesets total.
== code review ==
* reviewed vexpress dt patches
* started reviewing st-ericsson xshm drivers
* extensive discussions about coherency in dma-buf patches
== other work ==
* almost getting on top of randconfig patches for 3.2, plan
to send them out again next week.
== Linus Walleij linusw ==
=== Highlights ===
* Sent out v6 of the pin config patch series - it is now stable,
and functionality is in linux-next.
* Working on generic pin config for ASICs that want to keep
things simple.
* Discussed DT mappings to pin controllers with Stephen
Warren and Tony Lindgren. No consensus reached.
* Ux500 mainlining since too little is happening:
- Iterated AB5500 high voltage LEDs driver.
* Reviewed the Switch class derived from Android
by Samsung. This is very important stuff I feel.
* Helped Sjur Brændeland to get M7400 XSHM patches
into linux-next and will help him to establish a
k.org repository.
* Reviewed som MMC patch...
=== Plans ===
* Vacation 2011-12-19 thru 2012-01-06
* 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 the HWMON stuff.
=== Issues ===
* None, apart from some ST-Ericsson internal stuff.
Thanks,
Linus Walleij
== Dave Martin <dmart> ==
=== Activity Summary ===
* Reviewing of Pawel's versatile express patches and related discussions
(steadily progressing -- there are a few issues to resolve, but the
series appears almost ready. Some issues came up when testing.)
* Some discussions around U-Boot loading of relocatable images (now
supported in upstream U-Boot master branch thanks to Stephen Warren)
* Reworked AMBA modalias series on top of the file2alias.c cleanup patches
proposed on lkml.
* Some discussion around NO_IRQ and OF.
=== Plans ===
* Move miscellaneous outstanding DT issues (bindings, drivers) forward.
=== Work Items ===
https://blueprints.launchpad.net/linux-linaro/+spec/kernel-versatile-boad-d…:
Dynamic loading of AMBA device drivers (including via DT) - Propose for merging (proposed; waiting for confirmation): BLOCKED
Review/Ack Pawel's patches on final posting: BLOCKED
=== Absences ===
Christmas (approx. 2011-12-18 - 2012-01-06 -- exact dates TBD)
=== Device Tree ===
* Sent v2 of mc13892-regulator device tree support series
=== Consolidation and cleanup ===
* Sent a patch to add restart support for imx6 based on rmk's restart
branch
* Sent a series to clean up gpio-mxc gpio and irq numbering to have
them allocated dynamically
=== Misc ===
* Sent a patch to fix imx51 babbage power button
* Sent 2 patches to fix imx6 gpio interrupt controller
* Sent a patch to fix the use of pdev->id in fec driver
--
Regards,
Shawn
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Reviewed v5 of the regulator core device tree support patches.
* Started adding regulator device tree support for Origen board.
=== Plans ===
* Complete regulator dt support for Origen board.
* Add device tree support for Exynos4 display controller.
* Review the latest pin config patches and pinctrl dt discussion.
* Populate Exynos specific pinmux definitions in Samsung pinctrl driver.
== Rajendra Nayak <rnayak> ==
=== Highlights ===
* Added support for pin-configuration for OMAP4 using the v4 of
the pinconf core support patches. Data still in the driver and
not moved to dt. Waiting on Tony;s series/patches for DT support
and moving data out of the drivers.
* Started looking at clock bindings and generic struct clock support
patches. Experimented with moving OMAP clock data to dt which started
to look very complex (moving all clock data). Had a call with Benoit/
Mike on this and for now working on moving only leaf clocks/mappings
to dt keeping the rest of the clock tree in kernel.
* omap-serial dt support patches acked by Rob.
* Working with Aneesh V on omap4 EMIF driver dt support doing initial
reviews.
=== Plans ===
* Repost TWL regulator support. (Still waiting for a repost of omap
i2c/twl DT support patches)
* Refine the experimental patches to move OMAP clock data to dt.
* Rework some of the pinmux/pinconf support on top of changes Tony
has been proposing/working on once they are available.
=== Misc ===
* Will be taking off the week before Xmas (19th to 23rd Dec) and work
through the Xmas week.
Hi -
Alexander was asking how linaro-androidization-tracking is maintained
(hope you are feeling better Alexander).
I made a 90-slide presentation about it at the last Connect, you can
find the slides here
http://people.linaro.org/~andygreen/lttools-introduction.pdf
and the tools here
http://git.linaro.org/gitweb?p=people/andygreen/lt-tools.git;a=summary
In a nutshell common-3.0 from Google is a history tree, so detecting new
patches on there is clear enough. John Stultz saw it had come back
recently and dropped me a note it had been updated. I asked Jassi to
isolate the new patches and send them to me.
I use lt-tools to distribute any new patches between the topics, then
reapply it to my android-ready branch and confirm it builds and works
before pushing.
lt-tools also takes care of the tracking action, it's important
everything is on the same Linus HEAD basis so I routinely rebase
linaro-androidization-tracking along with my other tracking branches, as
of last week it's on 3.2-rc4.
Actually, l-a-t is low maintainence since it's far from every day new
patches are coming on common-3.0, and so far on 3.2 cycle there was no
serious uplevel conflict between the androidization patch load and Linus
HEAD changes.
If we have someone else now who wants to maintain it, I think that's
fine with the provisos we should maintain the topic structure and look
at further refactor there, and we need a new approach to deal with
rebase points that more than one tree can rendezvous at --->
Right now when my tracking branches are in as reasonable a shape on one
Linus HEAD basis as they will get, I randomly pull a new basis from what
happens to be on Linus' tree that moment, and rebase everything on my
side against that (including up until now l-a-t at the same time). That
won't really scale to other LTs and WGs all randomly sampling Linus HEAD
at different random points as their basis.
Scott mentioned that there's a desire to see more KWG content at least
on tracking, I think that's a great idea. One way to solve both those
problems would be to no longer have LTs base off Linus HEAD but from a
new tree which is Linus HEAD + "linux-linaro-tracking", as it were, with
these other topics already merged in. So long as this rebases against
Linus HEAD really often, like daily at least in the early -rcs, carrying
its topic content with it, and matching linaro-androidization-tracking
is available, that would be a good way for all the LT trees to both get
any Linaro-specific content and increase their chances of having a
common "rendezvous" basis where multiple LT trees can be bound together.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
Includes some items from the short holiday week before
=== Highlights ===
* Sent out fadvise based ashmem alternative patch to lkml for review.
Got a decent writeup at lwn: http://lwn.net/Articles/468896/ as well as
decent feedback.
* Got a small fixes to the config_merge.sh script included in -mm
* Sent out patch queue for 3.3 (including the CLOCK_RATE removal patches
from Deepak). Tglx has yet to pull it, but I'll nag him again.
* Pushed a few fixes for 3.2 for RTC and clocksource issues. Were merged
into -tip.
* Reworked timekeeping cleanup/performance patches for Thomas
* Worked with Anton Vorontsov on background and plans for lowmemory
killer upstreaming.
* Chased some RTC, sched_clock and timekeeping related bugs.
* Good meetings with Android and CromeOS teams.
* Started reworking ashmem alternative idea from lkml feedback.
* Saw Greg KH has queued some android patches for staging again. Sent
email out to him to try to get a sense of what he's planning and looking
for.
=== Plans ===
* More reworking of the fadvise ashmem alternative. Try to integrate
akpm's mumble tree idea.
* Try to sort out some of the community bugs that i've been handling.
* Get xtime lock breakup patches submitted.
=== Issues ===
* Community issues been cropping up and taking more time then I'd like.
== Anton Vorontsov <cbou> ==
=== Highlights ===
* Got the first Linaro task: Android lowmemory driver upstreaming.
Familiarized with the lowmemorykiller code and requirements, investigation
on previous upstreaming efforts.
== Linus Walleij linusw ==
=== Highlights ===
* Sent out v5 of the pin config patch series after some further
discussion: as usual nVidia provide the most challenging
feedback.
* Discussed pinmux maps proliferation with Arnd Bergmann
and Haojian Zhuang (PXA pinmux maintainer) and came up
with patches to address the issue of being able to tag
pinmux maps as __initdata so they are discarded after boot.
We also added the possibility to incrementally add several
sets of pinmux mappings, doing away with the "once and
for all" approach to registering maps.
* Discussed DT mappings to pin controllers with Stephen
Warren and Tony Lindgren. No consensus reached.
* Ux500 mainlining since too little is happening:
- AB8500 RTC patches iterated with Andrew Morton and
accepted into his tree.
- Fixed up patches for some movearound in the abx500
include headers directory.
- Clean-up and forward-ported AB5500 high voltage
LEDs driver.
- The two latter will be sent off ASAP, just awaiting some
optional internal feedback.
* Read and commented on a few patches on various mailing
lists to keep uptodate.
=== Plans ===
* 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 the HWMON stuff.
=== Issues ===
* Risk of pin controller subimplementations being delayed due
to the time it takes to reach consensus. Would be good if
the people who really need the pin config stuff got involved
with the discussion and start ACK:ing patches when they
like them, and tell me what I'm doing wrong and if they agree
with the critics. Active participation in discussions would be
appreciated. NOTE: I'm worthless in soft motivational-aspects
of leadership (get people to actively do stuff). The only person
I can motivate to discuss pin control is myself...
Thanks,
Linus Walleij
Hi,
For those of you who did not attend the ELC/LinuxCon in Prague a few
weeks ago, the slides and videos are available here (just in case you
were not aware):
http://free-electrons.com/blog/elce-2011-videos/
Among them, you can find my LPAE/A15 presentation ("Linux Support for
the ARM Large Physical Address Extensions"), Lorenzo's "Consolidating
Linux Power Management on ARM Multiprocessor Systems" and Pawel's
"Linux on Non-Existing SoCs". Enjoy :)
--
Catalin
=== Device Tree ===
* Added device tree support for imx6 clock based common-clk-v3 series
and Grant's device tree binding series (RFC).
* Addressed Sascha's comments on imx6 clock DT support.
* Added mc13892-regulator device tree support based on Rajendra's
series which has been applied on regulator/for-next.
=== Consolidation and cleanup ===
* Reviewed Mike's common-clk-v3 series.
=== Misc ===
* Collected mxs saif-recording patches.
--
Regards,
Shawn
== Niklas Hernaeus <nhe> ==
=== General activity ===
* Prepared DT for knowledge sharing session.
* Knowledge sharing session on DT.
* Further planning for DT on Snowball.
== Rajendra Nayak <rnayak> ==
=== Highlights ===
* Regulator core DT support patches pulled in by Mark Brown.
Pushed to linux-next.
* Posted v2 of omap-serial DT support series with all outstanding
issues fixed.
* Working on pinconf support (pull up/down configuration) for OMAP
based on the latest v3 pinconf-core support series from LinusW.
Should have patches out early this week.
* Working on moving the omap clock data into DT based on the latest
clock bindings from Grant. Mike Turquette already has a port of
omap clock framework to use common clock infrastructure.
=== Plans ===
* Repost TWL regulator support. (Still waiting for a repost of omap
i2c/twl DT support patches)
* Work on pinconf/pinmux support for OMAP and align with Tony who is
working on moving the data into DT and creating function/pin-gp
information dynamically.
* Other driver DT support for OMAP.
== Linus Walleij linusw ==
=== Highlights ===
* Sent out v3 of the pin control patch set, along with the U300
reference implementation mentioned last week.
* Discussed pin properties v3 patch set, the compulsory generic
pin properties were shot down so I took them out and submitted
v4 where they are instead an optional feature:
http://marc.info/?l=linux-kernel&m=132216047021660&w=2http://marc.info/?l=linux-kernel&m=132216047121661&w=2
* Finalized discussion on GPIO range mappings when
using different directions, the solution is to support calls
for pinmux_gpio_direction_[input|output] as well.
Added short blurb to blueprint about it.
http://marc.info/?l=linux-kernel&m=132196330625742&w=2
* LWN has an article on pin control from Jon Corbet, yay!
* Harvested a single GPIO patch, will send to Torvalds
by pull request ASAP.
* Git my kernel.org linux-stericsson and linux-pinctrl repos
back online.
* Forwarded Rabins fix to Stultz' alarm timers:
* Ran an internal 30min presentation about kernel
consolidation going forward.
* Re-pushed AB8500 RTC patches with Andrew Morton on
To: since Alessandro Zummo is AWOL.
=== Plans ===
* 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.
* Pushed out the AB8500 HWMON driver, will try to address
review comments.
* Look into other Ux500 stuff in need of mainlining...
=== Issues ===
* Pretty much internal fuzz at my parent company due to re-
organization. Even more this week. And then some christmas
stress.
Thanks,
Linus Walleij
== Dave Martin <dmart> ==
=== Activity Summary ===
* Reviewing of Pawel's versatile express patches and related discussions
* Proposed a more unified approach for manipulating instruction opcodes
inside the kernel in the presence of multiple ISA and endianness
cofigurations.
* Started to sketch out a unified unwind/backtrace interface for the
ARM kernel (or, possibly, the whole kernel) in response to upstream
discussions regarding ftrace -- ftrace doesn't support unwind tables,
but really there should be a unified interface so nobody has to care.
* Reported a couple of binutils bugs
=== Plans ===
* Move miscellaneous outstanding DT issues (bindings, drivers) forward.
=== Work Items ===
https://blueprints.launchpad.net/linux-linaro/+spec/kernel-versatile-boad-d…:
* loading of AMBA device drivers (including via DT) - Propose for merging: DONE
=== Absences ===
(none planned)
Hi -
Thanks to the work of Angus and Tushar a second Landing Team has
established a tracking tree, for Samsung Origen. They're using the same
lt-tools management scripts I use to handle the various trees in TI
Landing Team.
As I mentioned in the talk I gave at Connect about lt-tools, the fact
that we're both tracking near Linus HEAD allows us to casually combine
the trees for the first time if we can arrange for our basis to be
relatively close.
Today with the help of Angus and Tushar I gave that a try and -->
http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=shortl…
this single tree builds current Landing Team tracking for both Panda
(omap4_defconfig) and Origen (origen_defconfig), we confirmed the
results work as expected. Its common basis is Linus HEAD from yesterday.
Actually, the two trees did not tread on each others' toes at all, the
rebase proceeded with zero conflicts. Angus mentioned that there are
still some topics to come on his side; maybe they can create conflicts
in the future. Panda tracking got battered by upstream stuff post-3.1
we're still working to clear but it's still workable for this test
purpose anyway since it includes all the code footprint.
So we should be able to make ongoing combined tracking releases, and if
that continues to work smoothly it will naturally lead to a combined 3.2
release tree. Since we'll both be using the same
linaro-androidization-tracking on these trees to create Android kernels,
a single unified Android kernel should be possible to generate
automatically from the unified vanilla one and I'll look at starting
that after Panda tracking is in better shape.
-Andy
--
Andy Green | TI Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
Apologies all for the late report -- I wrote this last week, but I
just found it sitting in my drafts folder. It doesn't look like I
ever sent it.
I will try to avoid that next time...
Cheers
---Dave
== Dave Martin <dmart> ==
=== Activity Summary ===
* Reviewing of Pawel's versatile express patches and related discussions
=== Plans ===
* Move miscellaneous outstanding DT issues (bindings, drivers) forward.
=== Work Items ===
https://blueprints.launchpad.net/linux-linaro/+spec/kernel-versatile-boad-d…
* Review Pawel Moll's multi coretile support updates: DONE
=== Absences ===
(none planned)
== Niklas Hernaeus <nhe> ==
=== General activity ===
* Uart works for dt, but not quite as it is supposed to. Need to add dt
to a
general uart file.
* Preparing DT report for Knowledge sharing session. 40% done.
* Presented Linaro Connect report for STE Competence group.
=== Plans ===
* Make detailed plans for the work items.
* Make the dt uarts work as it is supposed to.
* Start work on dt i2c.
* Also, MMC must be included in the blueprints, somewhere at the top,
below i2c.
* Preparing a Linaro collaboration tools session. (irc, mumble, etherpad,
blueprints, rypple) 20% done. Date and form not set.
== Niklas Hernaeus <nhe> ==
=== General activity ===
* Uart works for dt, but not quite as it is supposed to. Need to add dt
to a
general uart file.
* Preparing DT report for Knowledge sharing session. 40% done.
* Presented Linaro Connect report for STE Competence group.
=== Plans ===
* Make detailed plans for the work items.
* Make the dt uarts work as it is supposed to.
* Start work on dt i2c.
* Also, MMC must be included in the blueprints, somewhere at the top,
below i2c.
* Preparing a Linaro collaboration tools session. (irc, mumble, etherpad,
blueprints, rypple) 20% done. Date and form not set.
=== Device Tree ===
* Reviewed Grant's clock DT binding series
* Converted imx6 clock code to Mike's pre-v3 common-clk series and
device tree binding. (a big RFC patch)
* Suggested change '#clock-cells' design to make the users a little
bit easier
=== Consolidation and cleanup ===
* Tested rmk's restart work for mxs
* Tested Sascha's mx5-merge series on imx6q, imx53 and imx51. With
this series, we can build single zImage for imx3, imx5 and imx6.
=== Misc ===
* Collected fixing patches for imx6 and mxs, and sent them to Arnd
for next -rc.
=== Plan ===
* Post mc13892 regulator DT patches based on Rajendra's series v5
--
Regards,
Shawn
== Thomas Abraham <thomas-ab> ==
=== Highlights ===
* Submitted initial version of gpio/pin-ctrl/pin-mux driver for internal review.
* Working on device tree support for i2s driver.
=== Plans ===
* Complete the device tree support for i2s driver.
=== Misc ===
* Leave on 18th (Friday) and 21st (Monday) November.
== Venkatraman S (svenkatr) ==
Was off partly due to TI internal activities.
== Highlights ==
* Understand requirements for eMMC4.5 implementation - studying specifications
* Review patches on Packed CMD implementation on mmc mailing list
* Testing of patches for preventing merges across erase block sizes
for low-end flash devices
== Plans ==
* Test and post patches for the above activity
* Continue study of eMMC4.5 features and UFS
Regards,
Venkat