omap3: serial code for 3630 and zoom2/3 fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 7 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 7 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/7] omap3: serial code for 3630 and zoom2/3 fixes
Quoted 11 lines · Sergio Aguirre
Hi,
This series contains fixes for omap2/3/4 serial code, and are fixing:
- Avoid doing ioremap of a zero-based physical address. (causing a kernel panic during early init on 3630boards)
- Unproperomap_revisioncheck during uart globals setup. (omap_revisionis not yet filled at that point)
- Don't try to enable all uarts generically for zoom2/3 and 3630sdp.
- Make zoom2/3 just register one serial port (ttyS0).
Thanks, I've pulled this into omap-fixes-for-linus.
Regards,
Tony
Quoted 39 lines
This is a subset of the original series found here: [1]
Thanks to:
- Vikram Pandita
- Paul Walmsley
- Kevin Hilman
- Manjunath Kondaiah
- Felipe Balbi
- Tony LindgreenFor all the feedback recieved so far.
Regards,
SergioDetailed changelog:
Sergio Aguirre (7):
OMAP3: serial: Check for zero-based physical addr
OMAP3: serial: Use dev_* macros instead of printk omap2/3/4: serial: Remove condition for gettinguart4_phys
omap3: zoom2/3 / 3630sdp: Don't init always all uarts
omap3: 3630sdp: Explicitly enable all UARTs
omap3: zoom 2/3: Change debugboard serial port id
omap3: zoom2/3: Register only 1 8250 portarch/arm/configs/omap_zoom2_defconfig | 2 +- arch/arm/configs/omap_zoom3_defconfig | 2 +- arch/arm/mach-omap2/board-3630sdp.c | 1 + arch/arm/mach-omap2/board-zoom-debugboard.c | 2 +- arch/arm/mach-omap2/board-zoom-peripherals.c | 1 - arch/arm/mach-omap2/serial.c | 35 +++++++++++++------------ 6 files changed, 22 insertions(+), 21 deletions(-)[1] http://marc.info/?l=linux-omap&m=126826639903105&w=2
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html