omap fixes against v3.12-rc3
The following changes since commit 15c03dd4859ab16f9212238f29dd315654aa94f6:
Linux 3.12-rc3 (2013-09-29 15:02:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/fixes-against-v3.12-rc3-take2
for you to fetch changes up to d1f1ca36b566aa56effdd7df69750062ec735131:
ARM: OMAP2: RX-51: Add missing max_current to rx51_lp5523_led_config (2013-10-08 11:22:43 -0700)
----------------------------------------------------------------
Few fixes for omap3 related hangs and errors that people have noticed now that people are actually using the device tree based booting for omap3.
Also one regression fix for timer compile for dra7xx when omap5 is not selected, and a LED regression fix for n900.
----------------------------------------------------------------
Aaro Koskinen (1):
ARM: OMAP2: gpmc-onenand: fix sync mode setup with DT
Nishanth Menon (1):
ARM: OMAP3: Fix hardware detection for omap3630 when booted with device tree
Pali Roh?r (1):
ARM: OMAP2: RX-51: Add missing max_current to rx51_lp5523_led_config
Simon Barth (1):
ARM: mach-omap2: board-generic: fix undefined symbol
Tony Lindgren (1):
ARM: dts: Fix pinctrl mask for omap3
arch/arm/boot/dts/omap3-beagle-xm.dts | 2 +- arch/arm/boot/dts/omap3.dtsi | 4 ++-- arch/arm/mach-omap2/board-generic.c | 18 ++++++++++++++++++ arch/arm/mach-omap2/board-rx51-peripherals.c | 9 +++++++++ arch/arm/mach-omap2/gpmc-onenand.c | 12 +++++++++++- arch/arm/mach-omap2/mux.h | 4 +--- arch/arm/mach-omap2/timer.c | 4 ++-- include/dt-bindings/pinctrl/omap.h | 4 +--- 8 files changed, 45 insertions(+), 12 deletions(-)
Quoted 8 lines · Tony Lindgren
The following changes since commit
15c03dd4859ab16f9212238f29dd315654aa94f6:Linux 3.12-rc3 (2013-09-29 15:02:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omaptags/fixes-against-v3.12-rc3-take2
Quoted 8 lines
for you to fetch changes up to
d1f1ca36b566aa56effdd7df69750062ec735131:ARM: OMAP2: RX-51: Add missing
max_currenttorx51_lp5523_led_config(2013-10-08 11:22:43 -0700)----------------------------------------------------------------
Few fixes for omap3 related hangs and errors that people have noticed now that people are actually using the device tree based booting for omap3.
FWIW, my automated boot is doing only DT boots on all the OMAP platforms. However, it's only testing basic boot so far so there's not a whole lot of driver testing yet (but it's coming soon.)
Quoted 2 lines
Also one regression fix for timer compile for dra7xx when omap5 is not selected, and a LED regression fix for n900.
Thanks, pulled into fixes.
Kevin
Quoted 4 lines · Kevin Hilman
FWIW, my automated boot is doing only DT boots on all the OMAP platforms. However, it's only testing basic boot so far so there's not a whole lot of driver testing yet (but it's coming soon.)
OK cool. For omap3, off-idle with DT needs the pending pinctrl-single patches, and some yet unknown way of mapping wake-up events to device interrupts. But after that you can also do some PM related tests potentially :)
Tony
Quoted 10 lines · Tony Lindgren
Quoted 4 lines · Kevin Hilman
FWIW, my automated boot is doing only DT boots on all the OMAP platforms. However, it's only testing basic boot so far so there's not a whole lot of driver testing yet (but it's coming soon.)
OK cool. For omap3, off-idle with DT needs the pending pinctrl-single patches, and some yet unknown way of mapping wake-up events to device interrupts. But after that you can also do some PM related tests potentially :)
Yeah, a review/test of that series is already my TODO list.
Kevin
Quoted 7 lines · Kevin Hilman
Quoted 6 lines · Tony Lindgren
Quoted 4 lines · Kevin Hilman
FWIW, my automated boot is doing only DT boots on all the OMAP platforms. However, it's only testing basic boot so far so there's not a whole lot of driver testing yet (but it's coming soon.)
Quoted 6 lines
Quoted 4 lines
OK cool. For omap3, off-idle with DT needs the pending pinctrl-single patches, and some yet unknown way of mapping wake-up events to device interrupts. But after that you can also do some PM related tests potentially :)
Yeah, a review/test of that series is already my TODO list.
Thanks, I would appreciate it if you could give it a quick try so we can make sure it does not cause regressions for the legacy booting.
For the DT based booting, you need to currently seprately do a request_irq on the wake-up interrupts, I have a test driver that does that that I can email to you if you need it.
Regards,
Tony