[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220217144755.270679-1-christophe.kerello@foss.st.com>
Date: Thu, 17 Feb 2022 15:47:51 +0100
From: Christophe Kerello <christophe.kerello@...s.st.com>
To: <miquel.raynal@...tlin.com>, <richard@....at>, <vigneshr@...com>,
<robh+dt@...nel.org>, <srinivas.kandagatla@...aro.org>,
<p.yadav@...com>
CC: <linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<devicetree@...r.kernel.org>, <chenshumin86@...a.com>,
Christophe Kerello <christophe.kerello@...s.st.com>
Subject: [PATCH v3 0/4] mtd: rawnand: stm32_fmc2: Add NAND Write Protect support
This patchset adds the management of the WP# signal in FMC2 driver.
WP will be disabled in probe/resume callbacks and will be enabled
in remove/suspend callbacks.
This patchset also fixes a conflict on wp-gpios property between
MTD and NVMEM.
Changes in v3:
- add a fixes tag in patches 3 and 4.
- rename skip_wp_gpio by ignore_wp in nvmen_config.
Changes in v2:
- add Rob Acked-by for the bindings part.
- rework the proposal done to fix a conflict between MTD and NVMEM on
wp-gpios property.
Christophe Kerello (4):
dt-binding: mtd: nand: Document the wp-gpios property
mtd: rawnand: stm32_fmc2: Add NAND Write Protect support
nvmem: core: Fix a conflict between MTD and NVMEM on wp-gpios property
mtd: core: Fix a conflict between MTD and NVMEM on wp-gpios property
.../bindings/mtd/nand-controller.yaml | 7 ++++
drivers/mtd/mtdcore.c | 2 +
drivers/mtd/nand/raw/stm32_fmc2_nand.c | 40 ++++++++++++++++++-
drivers/nvmem/core.c | 2 +-
include/linux/nvmem-provider.h | 4 +-
5 files changed, 52 insertions(+), 3 deletions(-)
--
2.25.1
Powered by blists - more mailing lists