<div dir="ltr"><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Hi Boris,</p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"> </p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">Thanks for getting back to me on this driver.</p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif"><br></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;font-size:11pt;font-family:Calibri,sans-serif">A few comments/input:</p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt"></p><ol style=""><li style=""><font face="Calibri, sans-serif"><span style="font-size:14.6667px">We have been working on this driver for quite a long time to port it to the latest Linux conventions, polish the code, run tests and reach high quality.<br>Our partners and customers are waiting to get this driver upstream so they can freely use it.<br>Since this driver is already in final stages and is in very good shape we will appreciate if you can review this specific driver/interface and help us to upstream it. </span></font></li><li style=""><font face="Calibri, sans-serif"><span style="font-size:14.6667px"> As for the new interface, we are open for any discussion and for porting the driver as required.<br>We are unsure what is this specific interface and weather it really fits a driver for a Flash Interface Controller module (rather than a SPI flash device).<br>Is it possible to get a sample driver from another Flash Interface Controller module that was ported to this new interface ?<br>Based on this we can evaluate the required effort and assign it accordingly. </span></font></li></ol><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px">Regards,</span></font></div><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px"><br></span></font></div><div><font face="Calibri, sans-serif"><span style="font-size:14.6667px">Tomer</span></font></div><p></p></div><br><div class="gmail_quote"><div dir="ltr">On Mon, 3 Dec 2018 at 11:22, Boris Brezillon <<a href="mailto:boris.brezillon@bootlin.com">boris.brezillon@bootlin.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, 3 Dec 2018 11:14:54 +0200<br>
Tomer Maimon <<a href="mailto:tmaimon77@gmail.com" target="_blank">tmaimon77@gmail.com</a>> wrote:<br>
<br>
> This patch set adds Flash Interface Unit(FIU) SPI-NOR<br>
> support for the Nuvoton NPCM Baseboard Management <br>
> Controller (BMC).<br>
> <br>
> The FIU supports single, dual or quad communication interface.<br>
> <br>
> the FIU controller can operate in following modes:<br>
> - User Mode Access(UMA): provides flash access by using an<br>
> indirect address/data mechanism.<br>
> - direct rd/wr mode: maps the flash memory into the core<br>
> address space.<br>
> - SPI-X mode: used for an expansion bus to an ASIC or CPLD.<br>
> <br>
> The NPCM750/730/715/710 supports up to three FIU devices:<br>
> - FIU0 supports two chip select.<br>
> - FIU3 supports four chip select.<br>
> - FIUX supports two chip select.<br>
> <br>
> The NPCM FIU driver tested on NPCM750 evaluation board.<br>
> <br>
> Tomer Maimon (2):<br>
> dt-binding: mtd: add NPCM FIU controller<br>
> mtd: spi-nor: add NPCM FIU controller driver<br>
> <br>
> Documentation/devicetree/bindings/mtd/npcm-fiu.txt | 64 ++<br>
> drivers/mtd/spi-nor/Kconfig | 8 +<br>
> drivers/mtd/spi-nor/Makefile | 1 +<br>
> drivers/mtd/spi-nor/npcm-fiu.c | 930 +++++++++++++++++++++<br>
<br>
We are currently trying to move all SPI NOR controller drivers out of<br>
drivers/mtd/spi-nor. Can you try to implement the spi-mem interface [1]<br>
and place your driver in drivers/spi/. <br>
<br>
[1]<a href="https://elixir.bootlin.com/linux/v4.20-rc5/source/include/linux/spi/spi-mem.h#L185" rel="noreferrer" target="_blank">https://elixir.bootlin.com/linux/v4.20-rc5/source/include/linux/spi/spi-mem.h#L185</a><br>
</blockquote></div>