[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-kernel
Subject:    [ACTIVITY] (Linus Walleij) 2012-11-20 - 2012-11-23
From:       linus.walleij () linaro ! org (Linus Walleij)
Date:       2012-11-23 8:00:17
Message-ID: CACRpkdapy9s_vWuGZf-MJvZTkw05MNi-Khhc6LQ5hoOcKFbWqg () mail ! gmail ! com
[Download RAW message or body]

== Linus Walleij linusw ==

=== Highlights ===

* Intense activity on pinctrl and gpio trees, also sending
  yet another round of pull requests for fixes to Torvalds
  for GPIO.

* Switched the U300 over to use the GPIO ranges.
  Discovered more issues with the solution and solved
  them with another 10 patches to the related code and
  drivers.
  https://blueprints.launchpad.net/linux-linaro/+spec/pinctrl-gpiorange-makeover

* Finalized my GPIO patch stack and sent of a pull
  request to Grant so he can funnel this to Torvalds for
  kernel v3.8.

* Discussed the status of the CW1200 driver in a lot of
  private mails.

* Acked a plethora of patches for the removal of __devinit

* Send clock patches for the Integrator/IM-PD1 to Mike
  Turquette, he merged them.

=== Plans ===

* Attack the remaining headers in arch/arm/mach-ux500
  so we can move forward with multiplatform for v3.9
  or so. (Make no promises, make no commitments...)

* 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...
  using an internal tracking sheet for this.

* Look into regmap. Try something out, get to know it.

=== Issues ===

* The GPIO range blueprint got escalated above the
  single zImage work due to influx from the community.
  Since contribuitors drive the process this happens...
  It was work that was on our blueprint list, but we could
  not control the priority of execution. I think this is
  normal but it needs to be reported and noted.

Thanks,
Linus Walleij


[prev in list] [next in list] [prev in thread] [next in thread]