Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Marco Felsch <m.felsch@pengutronix.de>
To:     tudor.ambarus@microchip.com, miquel.raynal@bootlin.com,
        richard@nod.at, vigneshr@ti.com,
        sergei.shtylyov@cogentembedded.com, boris.brezillon@collabora.com,
        michael@walle.cc, j.neuschaefer@gmx.net
Cc:     linux-mtd@lists.infradead.org, kernel@pengutronix.de,
        linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] MTD: SST SPI-NOR fixes
Date:   Fri, 11 Sep 2020 16:47:00 +0200
Message-Id: <20200911144703.25409-1-m.felsch@pengutronix.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi,

Patch 1-2: write path fixes
The sst write path is completely broken since v5.7-rc1 and in rare cases
since the support of the sst_write() function (49aac4aec53c).

Patch 3: cleanup

I've tested my patches with a small test app to ensure writes starting
on an odd address and with dd to test even start addresses. My dut was
an public available imx6q-sabrelite (rev.D).
Other testers are welcome :)

Regards,
  Marco

Marco Felsch (3):
  mtd: spi-nor: sst: fix write support for SST_WRITE marked devices
  mtd: spi-nor: sst: add missing write_enable
  mtd: spi-nor: sst: move sst_write_second to local driver

 drivers/mtd/spi-nor/core.c  | 15 +++++++++------
 drivers/mtd/spi-nor/sst.c   | 15 +++++++++++----
 include/linux/mtd/spi-nor.h |  2 --
 3 files changed, 20 insertions(+), 12 deletions(-)

-- 
2.20.1