Linux SPI subsystem development
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm-KobBqTBAxd8@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: spi_write_then_read with different tx/rx bits_per_word
Date: Mon, 13 Jan 2014 14:35:18 +0100	[thread overview]
Message-ID: <20140113133518.GA6613@frolo.macqel> (raw)
In-Reply-To: <20140110102745.GA29039-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>

On Fri, Jan 10, 2014 at 10:27:45AM +0000, Mark Brown wrote:
> On Wed, Jan 08, 2014 at 11:35:38PM +0100, Philippe De Muyter wrote:
> 
> > Is there a convenience function similar to spi_write_then_read
> > to handle that case or must I roll my own one in my driver ?
> 
> Try regmap?

Thanks.

Actually it was late in the evening and I was confusing read in
`spi_write_then_read' with read as in 'read a register'.

`spi_write_then_read' should probably better be named `spi_xmit_then_rcv'

Best regards

Philippe

-- 
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-01-13 13:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 22:35 spi_write_then_read with different tx/rx bits_per_word Philippe De Muyter
     [not found] ` <20140108223538.GA2861-NqYOdiUDesgPnqCj3zZnUQ@public.gmane.org>
2014-01-10 10:27   ` Mark Brown
     [not found]     ` <20140110102745.GA29039-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-01-13 13:35       ` Philippe De Muyter [this message]
     [not found]         ` <20140113133518.GA6613-NqYOdiUDesgPnqCj3zZnUQ@public.gmane.org>
2014-01-13 15:36           ` Mark Brown

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=20140113133518.GA6613@frolo.macqel \
    --to=phdm-kobbqtbaxd8@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@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