linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Tom <tom.spi.devel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: wait between bytes
Date: Mon, 14 Mar 2011 16:17:59 -0600	[thread overview]
Message-ID: <AANLkTimYoL5SnxfBbzv1d8JpeGkXMjiyKLi=Kaw7WaUJ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimYghAYwNQSW26=j4SnYkC_6d5frcAjkgNzF7kW-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Mon, Mar 14, 2011 at 4:10 PM, Tom <tom.spi.devel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi,
> I thought delay_usec is to create delay between transfers (i.e message
> transfers ).

Between transfers; but a single spi message can contain multiple
transfers without twiddling the cs line.

> Can it be used to create delay between bytes of a single message transfer?

No, you'll have to construct a message of multiple single byte
transfers in that case.

g.

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d

      parent reply	other threads:[~2011-03-14 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14  4:24 wait between bytes Tom
     [not found] ` <AANLkTinPtp3h4uv_jvHjms02h9a-GbH=NtObQPEjVj2S-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-14 19:11   ` Grant Likely
     [not found]     ` <20110314191126.GB16096-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2011-03-14 22:10       ` Tom
     [not found]         ` <AANLkTimYghAYwNQSW26=j4SnYkC_6d5frcAjkgNzF7kW-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-14 22:17           ` Grant Likely [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTimYoL5SnxfBbzv1d8JpeGkXMjiyKLi=Kaw7WaUJ@mail.gmail.com' \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=tom.spi.devel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).