[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ+vNU3vk92_1UnrYH72QgD3-q9Oy9As=jCiup42jzx_2LG9FA@mail.gmail.com>
Date: Tue, 25 Feb 2020 14:25:40 -0800
From: Tim Harvey <tharvey@...eworks.com>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: open list <linux-kernel@...r.kernel.org>,
linux-can@...r.kernel.org, Wolfgang Grandegger <wg@...ndegger.com>,
Timo Schlüßler <schluessler@...use.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH] can: mcp251x: convert to half-duplex SPI
On Tue, Feb 25, 2020 at 1:43 PM Marc Kleine-Budde <mkl@...gutronix.de> wrote:
>
> 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,
Your right... there is the mcp251x_hw_rx_frame() call that also uses
spi_rx_buf after a synchronous transfer (I didn't see any others).
I'll look at this again.
In general is it an ok approach to switch the driver to half-duplex
for this issue without the need of complicating things with a
module/dt param?
Regards,
Tim
Powered by blists - more mailing lists