| 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: Thu, 24 May 2012 14:39:02 -0300 From: Fabio Estevam <festevam@...il.com> To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de> Cc: Mark Brown <broonie@...nsource.wolfsonmicro.com>, Philippe Rétornaz <philippe.retornaz@...l.ch>, marc@...esign.com.au, Shawn Guo <shawn.guo@...escale.com>, Samuel Ortiz <sameo@...ux.intel.com>, Sascha Hauer <kernel@...gutronix.de>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: mc13xxx-core: kernel hangs after 'regmap_read' On Thu, May 24, 2012 at 1:41 PM, Uwe Kleine-König <u.kleine-koenig@...gutronix.de> wrote: >> If this is actually the issue the usual fix for this if the SPI >> controller hardware can't be persuaded to do the right thing is to put >> the chip select pin in GPIO mode and manage it by hand, though looking >> at the driver it appears it should be doingn that already. If you >> change to using the bitbanging SPI driver it should do the right thing >> (but will obviously be hideously slow), that ought to be at least a good >> reference for expected behaviour here. > The imx spi driver can do both (GPIO and hardware CS) because not all > pins that can do hardware CS are available as GPIO. Right, unfortunately on mx31 the SPI CS pins cannot be used as GPIOs. On mx51evk the SPI CS are used as GPIOs and that probably explains why it worked on mx51evk and fails on mx31pdk. -- 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