| 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
| ||
|
Date: Mon, 5 Dec 2011 13:17:29 -0600 From: Daniel Drake <dsd@...top.org> To: NeilBrown <neilb@...e.de> Cc: Ohad Ben-Cohen <ohad@...ery.com>, linux-mmc@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>, Joe Woodward <jw@...rafix.co.uk>, Chris Ball <cjb@...top.org> Subject: Re: [PATCH] mmc/sdio: don't allow interface to runtime-suspend until probe is finished. On Mon, Dec 5, 2011 at 1:06 PM, NeilBrown <neilb@...e.de> wrote: > The chip has a requirement that the reset line is held down during power-on, > and raised shortly after (I don't know exactly how short). So if you just > remove power and give it back, the chip doesn't come up properly. In another thread, Marvell confirmed that performing a SDIO reset is sufficient, no reset line tweaking is needed in the face of a reset. However, I would certainly advise playing with this reset line at the point of failure - you could confirm if it is or isn't being tweaked at this particular point, and if its not, you could try adjusting the code to manipulate this line at this point to see if it helps at all. Another area of experimentation is detailed here: http://article.gmane.org/gmane.linux.kernel.mmc/11475 especially if you can confirm that mmc_send_if_cond is the source of the failure. Thanks, Daniel -- 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/
Powered by blists - more mailing lists