[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d35f2b66-1915-8111-9187-cdc49417f787@ti.com>
Date: Wed, 5 Oct 2016 17:42:50 +0530
From: Vignesh R <vigneshr@...com>
To: Cyrille Pitchen <cyrille.pitchen@...el.com>,
<computersforpeace@...il.com>, <linux-mtd@...ts.infradead.org>
CC: <marex@...x.de>, <boris.brezillon@...e-electrons.com>,
<nicolas.ferre@...el.com>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/9] mtd: spi-nor: add an alternative method to support
memory >16MiB
Hi,
On Tuesday 04 October 2016 10:07 PM, Cyrille Pitchen wrote:
[...]
> static struct seq_rw_config stfsm_s25fl_write4_configs[] = {
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 5c87b2d99507..423448c1c7a8 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -75,6 +75,10 @@ struct flash_info {
> * bit. Must be used with
> * SPI_NOR_HAS_LOCK.
> */
> +#define SPI_NOR_4B_OPCODES BIT(10) /*
> + * Use dedicated 4byte address op codes
> + * to support memory size above 128Mib.
> + */
I don't see this flag being added to any flash_info data for any m25p80
compatible flashes? Is that part of a separate series?
--
Regards
Vignesh
Powered by blists - more mailing lists