Date: Mon, 25 Feb 2008 09:25:15 +0900 (JST)
Message-Id: <20080225.092515.126141645.anemo@mba.ocn.ne.jp>
To: nforrester@whoi.edu
Cc: david-b@pacbell.net, spi-devel-general@lists.sourceforge.net,
       marc.pignat@hevs.ch, linux-kernel@vger.kernel.org
Subject: Re: [spi-devel-general] [PATCH] atmel_spi: support zero length
 transfer
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
In-Reply-To: <47BF2455.8030904@whoi.edu>
References: <47BED734.5030002@whoi.edu>
	<20080222190228.2B0CB28E363@adsl-69-226-248-13.dsl.pltn13.pacbell.net>
	<47BF2455.8030904@whoi.edu>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 750
Lines: 17

On Fri, 22 Feb 2008 14:36:53 -0500, Ned Forrester <nforrester@whoi.edu> wrote:
> Or are you and Atsushi talking about using spi_transfer.delay_usecs
> *with* a zero length transfer to effectively put a delay between the
> assertion of CS and the start of the first clock?  If so, then I guess I
> missed the original point.  Sorry.

Yes.  I want to use zero length transfer with delay_usecs to achieve
CS-CLK delay for my funny device.  And I was too lazy to reject true
nop transfer.

---
Atsushi Nemoto
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/