From: Christophe Kerello <christophe.kerello@foss.st.com> To: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>, <robh+dt@kernel.org>, <srinivas.kandagatla@linaro.org> Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <devicetree@vger.kernel.org>, <chenshumin86@sina.com>, Christophe Kerello <christophe.kerello@foss.st.com> Subject: [PATCH 0/3] mtd: rawnand: stm32_fmc2: Add NAND Write Protect support Date: Wed, 5 Jan 2022 14:57:31 +0100 [thread overview] Message-ID: <20220105135734.271313-1-christophe.kerello@foss.st.com> (raw) 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 NVMEN. Christophe Kerello (3): 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 .../bindings/mtd/nand-controller.yaml | 7 ++++ drivers/mtd/nand/raw/stm32_fmc2_nand.c | 40 ++++++++++++++++++- drivers/nvmem/core.c | 2 +- 3 files changed, 47 insertions(+), 2 deletions(-) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Christophe Kerello <christophe.kerello@foss.st.com> To: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>, <robh+dt@kernel.org>, <srinivas.kandagatla@linaro.org> Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <linux-stm32@st-md-mailman.stormreply.com>, <devicetree@vger.kernel.org>, <chenshumin86@sina.com>, Christophe Kerello <christophe.kerello@foss.st.com> Subject: [PATCH 0/3] mtd: rawnand: stm32_fmc2: Add NAND Write Protect support Date: Wed, 5 Jan 2022 14:57:31 +0100 [thread overview] Message-ID: <20220105135734.271313-1-christophe.kerello@foss.st.com> (raw) 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 NVMEN. Christophe Kerello (3): 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 .../bindings/mtd/nand-controller.yaml | 7 ++++ drivers/mtd/nand/raw/stm32_fmc2_nand.c | 40 ++++++++++++++++++- drivers/nvmem/core.c | 2 +- 3 files changed, 47 insertions(+), 2 deletions(-) -- 2.25.1 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2022-01-05 13:58 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-05 13:57 Christophe Kerello [this message] 2022-01-05 13:57 ` [PATCH 0/3] mtd: rawnand: stm32_fmc2: Add NAND Write Protect support Christophe Kerello 2022-01-05 13:57 ` [PATCH 1/3] dt-binding: mtd: nand: Document the wp-gpios property Christophe Kerello 2022-01-05 13:57 ` Christophe Kerello 2022-01-21 21:19 ` Rob Herring 2022-01-21 21:19 ` Rob Herring 2022-01-05 13:57 ` [PATCH 2/3] mtd: rawnand: stm32_fmc2: Add NAND Write Protect support Christophe Kerello 2022-01-05 13:57 ` Christophe Kerello 2022-01-05 13:57 ` [PATCH 3/3] nvmem: core: Fix a conflict between MTD and NVMEM on wp-gpios property Christophe Kerello 2022-01-05 13:57 ` Christophe Kerello 2022-01-25 10:11 ` Miquel Raynal 2022-01-25 10:11 ` Miquel Raynal 2022-01-25 10:44 ` Srinivas Kandagatla 2022-01-25 10:44 ` Srinivas Kandagatla 2022-01-26 11:08 ` Christophe Kerello 2022-01-26 11:08 ` Christophe Kerello 2022-01-26 11:19 ` Miquel Raynal 2022-01-26 11:19 ` Miquel Raynal
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220105135734.271313-1-christophe.kerello@foss.st.com \ --to=christophe.kerello@foss.st.com \ --cc=chenshumin86@sina.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=miquel.raynal@bootlin.com \ --cc=richard@nod.at \ --cc=robh+dt@kernel.org \ --cc=srinivas.kandagatla@linaro.org \ --cc=vigneshr@ti.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.