Re: [PATCH v2] mtd: map: new driver for NXP IFC

[Sanjay Tandel <sanjay.tandel@rockwellcollins.com>]

Hi Prabhakar,

On Tue, Aug 29, 2017 at 7:37 PM, Prabhakar Kushwaha
<prabhakar.kushwaha@nxp.com> wrote:
> Dear Matt,
>
>> -----Original Message-----
>> From: linux-mtd [mailto:linux-mtd-bounces@lists.infradead.org] On Behalf Of
>> Matt Weber
>> Sent: Wednesday, August 30, 2017 1:17 AM
>> To: linux-mtd@lists.infradead.org
>> Cc: Matt Weber <matthew.weber@rockwellcollins.com>; boris.brezillon@free-
>> electrons.com; Sanjay Tandel <sanjay.tandel@rockwellcollins.com>;
>> arnd@arndb.de
>> Subject: [PATCH v2] mtd: map: new driver for NXP IFC
>>
>> From: Sanjay Tandel <sanjay.tandel@rockwellcollins.com>
>>
>> This patch adds map driver for parallel flash chips interfaced over
>> a NXP Integrated Flash Controller (IFC). This driver allows either
>> 8-bit or 16-bit accesses, depending on bank-width, to parallel flash
>> chips(like Everspin MR0A16A), which are physically mapped to CPU's
>> memory space. For unaligned accesses, it performs read-modify-write
>> operations to keep access size same as bank-width.
>>
>
>
> IFC is configured as per Flash's width per Chip select via boot-loader.

That's right. We are configuring IFC from boot-loader.

>
> Can you please share more details about the driver requirement.
> What is not working with NXP IFC?

8-bit accesses to 16-bit MRAM (through IFC) , using MTD map driver,
seem to corrupt the data.
We need this driver to limit all accesses to be bank-width size,

For more details, please refer the discussion on following thread:
https://patchwork.ozlabs.org/patch/797787/

>
> --prabhakar
>

Regards,
Sanjay