n950: mmc fails to work, omap_hsmmc 480b4000.mmc: RX DMA channel request failed ? was Re: 4.13 (and probably all recent) kernels refuse to boot on one Nokia N950, work or another

From: Pavel Machek <pavel@ucw.cz>
To: "Filip Matijević" <filip.matijevic.pz@gmail.com>
Cc: Sebastian Reichel <sre@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	pali.rohar@gmail.com, kernel list <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-omap@vger.kernel.org, khilman@kernel.org,
	aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
	patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com,
	clayton@craftyguy.net, martijn@brixit.nl,
	sakari.ailus@linux.intel.com
Subject: n950: mmc fails to work, omap_hsmmc 480b4000.mmc: RX DMA channel request failed ? was Re: 4.13 (and probably all recent) kernels refuse to boot on one Nokia N950, work or another
Date: Mon, 30 Oct 2017 20:43:40 +0100	[thread overview]
Message-ID: <20171030194340.GA9133@amd> (raw)
In-Reply-To: <65ad0b63-cfae-f7ac-f916-32fd0c7c540a@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

Hi!

I was able to setup nfsroot, and boot postmarketos (with root
read/only, but that's good enough for debugging).

Then I was (finally!) able to run dmesg, and that tells me:

[    0.816040] mousedev: PS/2 mouse device common for all mice
[    0.817657] input: TWL4030 Keypad as
/devices/platform/68000000.ocp/48070000.i2c/i2c-0/0-0048/48070000.i2c:twl@48:keypad/input/input0
[    0.820800] i2c /dev entries driver
[    0.830261] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout
60 sec
[    0.836212] omap_hsmmc 480b4000.mmc: RX DMA channel request failed
[    0.840026] ledtrig-cpu: registered to indicate activity on CPUs
[    0.840789] omap-aes 480c5000.aes: OMAP AES hw accel rev: 2.6
[    0.840942] omap-aes 480c5000.aes: Unable to request in DMA channel
[    0.841644] omap-aes 480c5000.aes: will run requests pump with
realtime priority

Kernel 4.13-rc2.

I'm now trying:

+++ b/.config
-CONFIG_MMC_OMAP_HS=y
+# CONFIG_MMC_OMAP_HS is not set

With that, error is gone, but so is MMC driver, so... not good.

Any ideas?

Best regards,
									Pavel   
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]