linux-kernel - Re: Linux 3.7 does not boot on OMAP L137 with CONFIG_TI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20121210234318.GA8439@shrek.podlesie.net>
Date:	Tue, 11 Dec 2012 00:43:18 +0100
From:	Krzysztof Mazur <krzysiek@...lesie.net>
To:	Matt Porter <mporter@...com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Linux 3.7 does not boot on OMAP L137 with CONFIG_TI_EDMA=y

On Tue, Dec 11, 2012 at 12:31:29AM +0100, Krzysztof Mazur wrote:
> Hi,
> 
> commit c2dde5f8f2095d7c623ff3565c1462e190272273
> (dmaengine: add TI EDMA DMA engine driver)
> with new option CONFIG_TI_EDMA=y causes system hang after
> "Uncompressing Linux... done, booting the kernel."
> on OMAP L137.

The system board is probably also important. The problem
occurs on Spectrum Digital OMAP-L137 EVM. I used following
board-specific options:

CONFIG_ARCH_DAVINCI=y
CONFIG_CP_INTC=y
CONFIG_ARCH_DAVINCI_DA830=y
CONFIG_ARCH_DAVINCI_DA8XX=y
CONFIG_MACH_DAVINCI_DA830_EVM=y
CONFIG_DA830_UI_LCD=y
CONFIG_GPIO_PCA953X=y
CONFIG_DAVINCI_MUX=y
CONFIG_DAVINCI_RESET_CLOCKS=y

> 
> The same problem still exists in current v3.7-rc8-41-gcaf4919.
> 
> This causes some regressions, for instance the converted to new DMA engine
> SPI driver does not work without CONFIG_TI_EDMA=y:
> 
> spi_davinci spi_davinci.0: Runtime PM disabled, clock forced on.
> spi_davinci spi_davinci.0: request RX DMA channel failed
> Trying to free nonexistent resource <0000000001c41000-0000000001c41000>
> 
> By the way:
> 
> 1. It's possible to compile davinci SPI driver with
> CONFIG_DMADEVICES=n (and CONFIG_TI_EMDA=n), but it does work
> in that configuration (see error above).
> 
> 2. The "Trying to free nonexistent resource" seems to indicate some
> other error in SPI driver cleanup after error code.
> 

Krzysiek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/