linux-kernel - Atmel SoCs and the newly added CONFIG_DELAY_DEVICE

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-next>] [day] [month] [year] [list]

Date:	Fri, 16 Oct 2015 20:11:29 +0200
From:	Sylvain Rochet <sylvain.rochet@...secur.com>
To:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Jean-Christophe Plagniol-Villard <plagnioj@...osoft.com>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	Boris Brezillon <boris.brezillon@...e-electrons.com>,
	Wenyou Yang <Wenyou.Yang@...el.com>,
	Ludovic Desroches <ludovic.desroches@...el.com>,
	Tomeu Vizoso <tomeu.vizoso@...labora.com>
Subject: Atmel SoCs and the newly added CONFIG_DELAY_DEVICE_PROBES option

Hi,

FYI, to save you a git bisect, the recently added 
CONFIG_DELAY_DEVICE_PROBES (enabled by default) breaks Atmel SoCs.

For a few of quickly noticeable issues:
- PM is not working:   at91_pm_sram_init: sram pool unavailable!
- Watchdog is not even probed
- on -ek boards the wm8904 is not probed either.

Disabling CONFIG_DELAY_DEVICE_PROBES fixes all issues.

Tomeu, what should I provide to help find out what's happening ?

Sylvain
--
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/