linux-kernel - 32kHz clock removal causes problems omap

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:	Thu, 15 Nov 2012 10:31:33 +0200
From:	Luciano Coelho <coelho@...com>
To:	<svenkatr@...com>, <linux-omap@...r.kernel.org>
CC:	<linux-mmc@...r.kernel.org>, <cjb@...top.org>, <lrg@...com>,
	<broonie@...nsource.wolfsonmicro.com>,
	<linux-kernel@...r.kernel.org>, <balbi@...com>,
	Peter Ujfalusi <peter.ujfalusi@...com>,
	Tony Lindgren <tony@...mide.com>
Subject: 32kHz clock removal causes problems omap_hsmmc

Hi,

Since the 32KHz clock was removed from the twl-regulator (0e8e5c34
regulator: twl: Remove references to 32kHz clock from DT bindings),
we've been having problems with our wl12xx chip that is connected
through the omap_hsmmc.

Our card simply doesn't get added to the system and we get lots of
-ETIMEOUTs during mmc_attach.  If I revert 0e8e5c34 (plus a couple of
associated patches), everything works fine.

I've been using a Blaze device with a WiLink 1283 chip connected in the
COM (internal) port.  The funny thing is that I don't have the same
problem with a WiLink 1853 chip (which is connected externally to
another Blaze).

Does anyone know what the problem could and how to fix it?

This is a regression that has been there since 3.6-rc1.

--
Cheers,
Luca.

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