linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: spi-devel-general@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] spi: Use void pointers for data in simple SPI I/O operations
Date: Thu, 19 May 2011 13:00:34 -0600	[thread overview]
Message-ID: <20110519190034.GF5109@ponder.secretlab.ca> (raw)
In-Reply-To: <1305065370-28616-1-git-send-email-broonie@opensource.wolfsonmicro.com>

On Wed, May 11, 2011 at 12:09:30AM +0200, Mark Brown wrote:
> Currently the simple SPI I/O operations all take pointers to u8 * buffers
> to operate on. This creates needless type compatibility issues and the
> underlying spi_transfer structure uses void pointers anyway so convert the
> API over to take void pointers too.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>

Merged, thanks.

g.

> ---
>  drivers/spi/spi.c       |    4 ++--
>  include/linux/spi/spi.h |    8 ++++----
>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index 82b9a42..2e13a14 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1047,8 +1047,8 @@ static u8	*buf;
>   * spi_{async,sync}() calls with dma-safe buffers.
>   */
>  int spi_write_then_read(struct spi_device *spi,
> -		const u8 *txbuf, unsigned n_tx,
> -		u8 *rxbuf, unsigned n_rx)
> +		const void *txbuf, unsigned n_tx,
> +		void *rxbuf, unsigned n_rx)
>  {
>  	static DEFINE_MUTEX(lock);
>  
> diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
> index b4d7710..bb4f5fb 100644
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -581,7 +581,7 @@ extern int spi_bus_unlock(struct spi_master *master);
>   * Callable only from contexts that can sleep.
>   */
>  static inline int
> -spi_write(struct spi_device *spi, const u8 *buf, size_t len)
> +spi_write(struct spi_device *spi, const void *buf, size_t len)
>  {
>  	struct spi_transfer	t = {
>  			.tx_buf		= buf,
> @@ -605,7 +605,7 @@ spi_write(struct spi_device *spi, const u8 *buf, size_t len)
>   * Callable only from contexts that can sleep.
>   */
>  static inline int
> -spi_read(struct spi_device *spi, u8 *buf, size_t len)
> +spi_read(struct spi_device *spi, void *buf, size_t len)
>  {
>  	struct spi_transfer	t = {
>  			.rx_buf		= buf,
> @@ -620,8 +620,8 @@ spi_read(struct spi_device *spi, u8 *buf, size_t len)
>  
>  /* this copies txbuf and rxbuf data; for small transfers only! */
>  extern int spi_write_then_read(struct spi_device *spi,
> -		const u8 *txbuf, unsigned n_tx,
> -		u8 *rxbuf, unsigned n_rx);
> +		const void *txbuf, unsigned n_tx,
> +		void *rxbuf, unsigned n_rx);
>  
>  /**
>   * spi_w8r8 - SPI synchronous 8 bit write followed by 8 bit read
> -- 
> 1.7.5.1
> 

      reply	other threads:[~2011-05-19 19:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 22:09 [PATCH] spi: Use void pointers for data in simple SPI I/O operations Mark Brown
2011-05-19 19:00 ` 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=20110519190034.GF5109@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --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 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).