All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: spi-devel-general@lists.sourceforge.net,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [spi-devel-general] Re: question on spi_bitbang
Date: Fri, 31 Mar 2006 14:20:02 -0800	[thread overview]
Message-ID: <200603311420.02962.david-b@pacbell.net> (raw)
In-Reply-To: <61D4885F-D742-4583-939F-FA93A4AAC8D4@kernel.crashing.org>

On Friday 31 March 2006 2:11 pm, Kumar Gala wrote:

> So I give a new question.  Any issue with adding a rx & tx completion  
> to spi_bitbang?

What do you mean?

> In my HW I get an interrupt when the transmitter is   
> done transmitting and one when the receiver is done receiving.  I  
> need some way to synchronize and wait for both events to occur before  
> continuing on in txrx_word().

You can't return from txrx_word() before the RX event, since the
return value is the word that was shifted in.  So if you use IRQs
to synchronize there (rather than polling a status register), all
that would be internal to your code.

- Dave

  reply	other threads:[~2006-03-31 22:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 17:31 question on spi_bitbang Kumar Gala
2006-03-31 18:11 ` David Brownell
2006-03-31 18:19   ` [spi-devel-general] " Stephen Street
2006-03-31 19:16     ` David Brownell
2006-03-31 19:07   ` Kumar Gala
2006-03-31 19:17     ` Kumar Gala
2006-03-31 19:32     ` [spi-devel-general] " David Brownell
2006-03-31 20:00       ` Kumar Gala
2006-03-31 20:36         ` David Brownell
2006-03-31 20:52           ` Kumar Gala
2006-03-31 21:15             ` David Brownell
2006-03-31 22:11               ` Kumar Gala
2006-03-31 22:20                 ` David Brownell [this message]
2006-03-31 23:58                   ` Kumar Gala

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=200603311420.02962.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.