mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Tim Harvey <tharvey@gateworks.com>,
	linux-kernel@vger.kernel.org, linux-can@vger.kernel.org,
	Wolfgang Grandegger <wg@grandegger.com>
Cc: "Timo Schlüßler" <schluessler@krause.de>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] can: mcp251x: convert to half-duplex SPI
Date: Tue, 25 Feb 2020 22:43:07 +0100	[thread overview]
Message-ID: <0ac77abd-0df5-e437-ea46-f6c77f59b81c@pengutronix.de> (raw)
In-Reply-To: <1582655734-20890-1-git-send-email-tharvey@gateworks.com>

On 2/25/20 7:35 PM, Tim Harvey wrote:
> Some SPI host controllers such as the Cavium Thunder do not support
> full-duplex SPI. Using half-duplex transfers allows the driver to work
> with those host controllers.

There are several transfers left in the driver, where both rx_buf and
tx_buf are set. How does your host controller driver know which one to
handle?

Marc

> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
> ---
>  drivers/net/can/spi/mcp251x.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/net/can/spi/mcp251x.c b/drivers/net/can/spi/mcp251x.c
> index 5009ff2..840c31c 100644
> --- a/drivers/net/can/spi/mcp251x.c
> +++ b/drivers/net/can/spi/mcp251x.c
> @@ -290,23 +290,23 @@ static u8 mcp251x_read_reg(struct spi_device *spi, u8 reg)
>  	priv->spi_tx_buf[0] = INSTRUCTION_READ;
>  	priv->spi_tx_buf[1] = reg;
>  
> -	mcp251x_spi_trans(spi, 3);
> -	val = priv->spi_rx_buf[2];
> +	spi_write_then_read(spi, priv->spi_tx_buf, 2, &val, 1);
>  
>  	return val;
>  }
>  
>  static void mcp251x_read_2regs(struct spi_device *spi, u8 reg, u8 *v1, u8 *v2)
>  {
> +	u8 val[4] = {0};
>  	struct mcp251x_priv *priv = spi_get_drvdata(spi);
>  
>  	priv->spi_tx_buf[0] = INSTRUCTION_READ;
>  	priv->spi_tx_buf[1] = reg;
>  
> -	mcp251x_spi_trans(spi, 4);
> +	spi_write_then_read(spi, priv->spi_tx_buf, 2, val, 2);
>  
> -	*v1 = priv->spi_rx_buf[2];
> -	*v2 = priv->spi_rx_buf[3];
> +	*v1 = val[0];
> +	*v2 = val[1];
>  }
>  
>  static void mcp251x_write_reg(struct spi_device *spi, u8 reg, u8 val)
> 

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2020-02-25 21:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25 18:35 Tim Harvey
2020-02-25 21:43 ` Marc Kleine-Budde [this message]
2020-02-25 22:25   ` Tim Harvey
2020-02-26  7:37     ` Marc Kleine-Budde
2020-02-26 10:19       ` Marc Kleine-Budde
2020-05-21 20:19         ` Tim Harvey
2020-05-21 21:08           ` Mark Brown
2020-05-25 11:17           ` Marc Kleine-Budde
2020-05-25 11:31             ` Mark Brown
2020-05-25 12:41               ` Marc Kleine-Budde
2020-05-25 12:57                 ` Mark Brown
2020-05-25 13:12                   ` Marc Kleine-Budde
2020-05-25 13:27                     ` 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=0ac77abd-0df5-e437-ea46-f6c77f59b81c@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schluessler@krause.de \
    --cc=tharvey@gateworks.com \
    --cc=wg@grandegger.com \
    /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

all inboxes | Powered by JetHome®