Russell,
On the mainline 2.6.31-rc6, OMAP4 boot is crashing. Also serial code in the
linux-next branch isn't merge correctly and needs reworked patches.
Can you please see if they are ok?
This patch series addresses the OMAP4430 boot up crash issues on the latest
2.6.31-rc6 kernel release. T
Second reason of OMAP4 boot failure on 2.6.31.rc6, the UART
platform data is not getting registered to kernel.
Registration was failing because of clock check failure in
omap_serial_init().
Below patch fix the same.
OMAP4 clock framework patches are still getting discussed on mailing
list so till
After the patch series "[PATCH 00/14] OMAP PM fixes for .31-rc"
merge in 2.6.31-rc5, the kernel crashed during boot on OMAP4430.
This patch fixes it by adding UART4 support and related code.
Without this patch omap_serial_init() would produce " NULL pointer
dereference" and kernel crashes in the bo
just a few cleanups here and there.
Felipe Balbi (6):
dsp: bridge: use ARRAY_SIZE
dsp: bridge: wcd: else is unnecessary
dsp: bridge: rename Kbuild to Makefile
dsp: bridge: always use dynamic major/minor numbers
dsp: brigde: remove unnecessary memset()
dsp: bridge: beautify erro path
trivial patch using ARRAY_SIZE.
Signed-off-by: Felipe Balbi
---
drivers/dsp/bridge/pmgr/wcd.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/dsp/bridge/pmgr/wcd.c b/drivers/dsp/bridge/pmgr/wcd.c
index 859043d..7434f43 100644
--- a/drivers/dsp/bridge/pmgr/wcd.
The return makes the use of else unnecessary, remove it
Signed-off-by: Felipe Balbi
---
drivers/dsp/bridge/pmgr/wcd.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/dsp/bridge/pmgr/wcd.c b/drivers/dsp/bridge/pmgr/wcd.c
index 7434f43..01c9572 100644
--- a/driv
we all use Makefile, let's keep the name.
Signed-off-by: Felipe Balbi
---
drivers/dsp/bridge/{Kbuild => Makefile} |0
1 files changed, 0 insertions(+), 0 deletions(-)
rename drivers/dsp/bridge/{Kbuild => Makefile} (100%)
diff --git a/drivers/dsp/bridge/Kbuild b/drivers/dsp/bridge/Makefile
... and get rid of a possible memory leak.
in case of error while adding the chardev, probe()
would not kfree() bridge_device.
Signed-off-by: Felipe Balbi
---
drivers/dsp/bridge/rmgr/drv_interface.c | 20 ++--
1 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/dri
there's no reason to initialize that to 0 or use module parameters
if kernel will always get us dynamic numbers.
Signed-off-by: Felipe Balbi
---
drivers/dsp/bridge/rmgr/drv_interface.c | 25 ++---
1 files changed, 6 insertions(+), 19 deletions(-)
diff --git a/drivers/dsp/b
bridge_device is static and thus doesn't need
to be zero-initialized.
Signed-off-by: Felipe Balbi
---
drivers/dsp/bridge/rmgr/drv_interface.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/dsp/bridge/rmgr/drv_interface.c
b/drivers/dsp/bridge/rmgr/drv_interface.
Hi,
On Fri, Aug 21, 2009 at 12:23:38PM +0200, Balbi Felipe (Nokia-D/Helsinki) wrote:
> bridge_device is static and thus doesn't need
> to be zero-initialized.
>
> Signed-off-by: Felipe Balbi
I changed this patch to the following:
cut here =
>From 1a5699476007fdff6beb5a895c74bc15f0bd
Tim Bird writes:
> Paul Walmsley wrote:
>> Hi Peter,
>>
>> On Wed, 19 Aug 2009, Peter Barada wrote:
>>
>>> 1) Does anyone have a URL of the format patches should be in that are
>>> submitted to the linux-omap list?
>>>
>>> I've got some patches to add base support for the Logic OMAP 35x SOM and
On Fri, 2009-08-21 at 15:10 +0200, Kevin Hilman wrote:
> Tim Bird writes:
>
> > Paul Walmsley wrote:
> >> Hi Peter,
> >>
> >> On Wed, 19 Aug 2009, Peter Barada wrote:
> >>
> >>> 1) Does anyone have a URL of the format patches should be in that are
> >>> submitted to the linux-omap list?
> >>>
>
Hi!
On Friday 21 August 2009 16:34:33 Peter Barada wrote:
> On Fri, 2009-08-21 at 15:10 +0200, Kevin Hilman wrote:
> > Tim Bird writes:
> > > Paul Walmsley wrote:
> > >> Hi Peter,
> > >>
> > >> On Wed, 19 Aug 2009, Peter Barada wrote:
> > >>> 1) Does anyone have a URL of the format patches should
Santosh Shilimkar writes:
> Second reason of OMAP4 boot failure on 2.6.31.rc6, the UART
> platform data is not getting registered to kernel.
> Registration was failing because of clock check failure in
> omap_serial_init().
> Below patch fix the same.
>
> OMAP4 clock framework patches are still g
"Shilimkar, Santosh" writes:
> Russell,
>
> On the mainline 2.6.31-rc6, OMAP4 boot is crashing. Also serial code in the
> linux-next branch isn't merge correctly and needs reworked patches.
>
> Can you please see if they are ok?
After the fix I suggested on patch 2/2, I'm OK with these.
Tony
Patch1/2: clean up the DEBUG_LL infrastructure.
Patch3: add DEBUG_LL support for Zoom2 board
Patch4/5: some Zoom2 fixes
Vikram Pandita (5):
OMAP1/2/3/4: DEBUG_LL: cleanup
OMAP1/2/3/4: Adapt board files for cleand DEBUG_LL interface
OMAP: Zoom2: Add DEBUG_LL interface using external Quart
O
This patch cleans up the DEBUG_LL infrastructure for omap boards.
The three stages of log printing infrastructure is using their own #defines
The patch integrates the three stages to use the same variable.
Three stages are:
Stage 1: Prints - Uncompressing Linux..
File getting used: ar
This patch assigns the physical address of debug uart as defined
in menucoinfig item CONFIG_OMAP_DEBUG_LL_UART_PHY_ADDR to phys_io
The virtual address for io_pg_offset is calculated as per static
mapping
CONFIG_OMAP_DEBUG_LL_UART_PHY_ADDR is a hex value and for boards
like Zoom2, the phy address
This patch adds DEBUG_LL interface for Zoom2 board.
The low level debug uart now points corrctly to External Quad uart
controller on detachable debug board.
The Quad uart is available over GPMC chip select with physical address
0x1000.
This physical address has been mapped to virtual address
Fix the break in Zoom2 Quad uart debug port support.
Patch by Kevin Hilman fd455ea899b5a14 caused a break as it introuduced
per port PLATFORM id and Zoom2 was not tested with this change.
For Zoom2 serial port, add platform id as 4
Signed-off-by: Vikram Pandita
cc: Kevin Hilman
---
arch/arm/m
Release the Dbg board detection gpio once its purpose is served
Signed-off-by: Vikram Pandita
---
arch/arm/mach-omap2/board-zoom-debugboard.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/arm/mach-omap2/board-zoom-debugboard.c
b/arch/arm/mach-omap2/board-zo
Hi everyone,
maybe some OMAP-hackers might like this :-)
- Paul
-- Forwarded message --
Date: Fri, 21 Aug 2009 17:59:15 +0100
From: Catalin Marinas
To: linux-arm-kernel
Subject: ARM Architecture Reference Manual available for download
Hi,
I thought people in the ARM Linux c
On Thu, Aug 20, 2009 at 11:34 AM, Steve Sakoman wrote:
> I've been doing a bit of testing on 2.6.31-rc5 on Overo with good
> results overall.
Related to the Gumstix Overo
How is the USB working on this version. I am still stuck using the
2.6.20-rc8, with patches for the hwmod and mmc updates. Th
On Fri, Aug 21, 2009 at 1:25 PM, John Sarman wrote:
> Related to the Gumstix Overo
> How is the USB working on this version. I am still stuck using the
> 2.6.20-rc8, with patches for the hwmod and mmc updates. This is the
> last version I can successfully use the USB host.
USB host works fine i
OMAP1_MPUIO_BASE was used instead of OMAP1_MPUIO_VBASE leading to
a crash on init as soon as the address was used.
Signed-off-by: Alistair Buxton
---
arch/arm/plat-omap/gpio.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/plat-omap/gpio.c b/arch/arm/plat-omap
Hi Tony,
Are you OK with below patch? I have not received any comment yet.
In case this patch is OK, can you please push it?
-vimal
On Wed, Aug 19, 2009 at 10:14 AM, vimal singh wrote:
> Add support for flash on SDP boards. NAND, NOR and OneNAND
> are supported.
>
> Only tested on 3430SDP (ES2
27 matches
Mail list logo
