RE: [PATCH v2 0/6] spi: Add Renesas SPIBSC controller

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Dec 17, 2019, Sergei Shtylyov wrote:
>    But what does the acronym mean?
QSPI = "Quad SPI"


> > So at the moment, there is nothing yet for me to 'try' on the RZ/A series,
> correct?
> 
>    Why, I can send you a working version of the SPI driver, and even HF one
> if you're
> interested.

The point of this whole discussion is to determine if we should have 2 drivers
for the same Renesas HW IP.

There was a RPC-IF patch series that made it to v17....and is now dead.

You sent a new RFC series for a new method, but all it had was low level APIs,
no MTD framework, do it didn't really do anything.

If there was a complete patch set that I could try on the RZ/A SoCs and 
get a working SPI MTD device to show up, then I would drop my efforts of
getting my driver in and just add RZ/A support to the R-Car driver.

Geert suggested out an easy solution for the "XIP" use case for RZ/A 
devices, and that mostly happens outside this driver, so I'm not worried 
about that anymore.

Honestly, I'll be out of the office until January, so it's not like I'm 
going to do anything with it until then. But if there is a complete series
to try by then, I will see how it performs on RZ/A boards.

Chris





[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]


  Powered by Linux