On Mon, Jul 9, 2012 at 2:08 PM, Mark Brown wrote:
> On Thu, Jul 05, 2012 at 09:45:40AM +0200, Uwe Kleine-K?nig wrote:
>> On Thu, Feb 09, 2012 at 10:21:45PM +0100, Uwe Kleine-K?nig wrote:
>> > The chip select line was configured as output with the initial value
>> > being active explicitly. It was
On Thu, Jul 05, 2012 at 09:45:40AM +0200, Uwe Kleine-K?nig wrote:
> On Thu, Feb 09, 2012 at 10:21:45PM +0100, Uwe Kleine-K?nig wrote:
> > The chip select line was configured as output with the initial value
> > being active explicitly. It was later deasserted during
> > spi_bitbang_setup() without
On Thu, Feb 09, 2012 at 10:21:45PM +0100, Uwe Kleine-König wrote:
> The chip select line was configured as output with the initial value
> being active explicitly. It was later deasserted during
> spi_bitbang_setup() without any clock activity in between. So it makes
> no sense to activate the devi
The chip select line was configured as output with the initial value
being active explicitly. It was later deasserted during
spi_bitbang_setup() without any clock activity in between. So it makes
no sense to activate the device at all and the chip select line can
better start non-active.
Signed-of
