From e3c81877368124cb52cb13aa73d356efa28ea1c6 Mon Sep 17 00:00:00 2001 From: Benjamin Valentin Date: Fri, 25 Mar 2022 12:14:20 +0100 Subject: [PATCH] dirvers/mtd: don't use work_buf as proxy for !direct write flag Currently work_buf is only NULL when MTD_DRIVER_FLAG_DIRECT_WRITE is set, so it served as a proxy for that flag. However, we might want to have a work buffer even when writes without erase are possible. --- drivers/mtd/mtd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/mtd.c b/drivers/mtd/mtd.c index a865021efa..9e587c243a 100644 --- a/drivers/mtd/mtd.c +++ b/drivers/mtd/mtd.c @@ -201,7 +201,7 @@ int mtd_write_page(mtd_dev_t *mtd, const void *data, uint32_t page, return -ENODEV; } - if (mtd->work_area == NULL) { + if (mtd->driver->flags & MTD_DRIVER_FLAG_DIRECT_WRITE) { return mtd_write_page_raw(mtd, data, page, offset, len); }