Re: [U-Boot] [PATCH] spi: tegra20: fix mode selection logic

On 08/15/2016 09:35 AM, Stephen Warren wrote: On 08/13/2016 09:56 AM, Jagan Teki wrote: On 13 August 2016 at 02:36, Stephen Warren wrote: From: Stephen Warren When the set_mode() function runs, the SPI bus is not active, and hence the clocks to the

Re: [U-Boot] [PATCH] spi: tegra20: fix mode selection logic

On 08/13/2016 09:56 AM, Jagan Teki wrote: On 13 August 2016 at 02:36, Stephen Warren wrote: From: Stephen Warren When the set_mode() function runs, the SPI bus is not active, and hence the clocks to the SPI controller are not running. Any register

Re: [U-Boot] [PATCH] spi: tegra20: fix mode selection logic

On 13 August 2016 at 02:36, Stephen Warren wrote: > From: Stephen Warren > > When the set_mode() function runs, the SPI bus is not active, and hence > the clocks to the SPI controller are not running. Any register read/write > at this time will hang the

Re: [U-Boot] [PATCH] spi: tegra20: fix mode selection logic

2016-08-13 10:51 GMT+02:00 Mirza Krak : > 2016-08-12 23:06 GMT+02:00 Stephen Warren : >> From: Stephen Warren >> >> When the set_mode() function runs, the SPI bus is not active, and hence >> the clocks to the SPI controller

Re: [U-Boot] [PATCH] spi: tegra20: fix mode selection logic

2016-08-12 23:06 GMT+02:00 Stephen Warren : > From: Stephen Warren > > When the set_mode() function runs, the SPI bus is not active, and hence > the clocks to the SPI controller are not running. Any register read/write > at this time will hang the CPU.

[U-Boot] [PATCH] spi: tegra20: fix mode selection logic

From: Stephen Warren When the set_mode() function runs, the SPI bus is not active, and hence the clocks to the SPI controller are not running. Any register read/write at this time will hang the CPU. Remove the code from set_mode() that does this, and move it to the correct