[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bad42fa4-679b-408e-99a7-008aead0302f@gmail.com>
Date: Sat, 25 Nov 2023 09:24:49 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: dregan@...adcom.com, miquel.raynal@...tlin.com,
bcm-kernel-feedback-list@...adcom.com,
linux-mtd@...ts.infradead.org, rafal@...ecki.pl,
joel.peshkin@...adcom.com, computersforpeace@...il.com,
dan.beygelman@...adcom.com, william.zhang@...adcom.com,
frieder.schrempf@...tron.de, linux-kernel@...r.kernel.org,
vigneshr@...com, richard@....at, bbrezillon@...nel.org,
kdasu.kdev@...il.com, JaimeLiao <jaimeliao.tw@...il.com>,
Adam Borowski <kilobyte@...band.pl>
Subject: Re: [PATCH v5 1/4] mtd: rawnand: Add destructive operation
On 11/24/2023 5:24 PM, dregan@...adcom.com wrote:
> From: Boris Brezillon <bbrezillon@...nel.org>
>
> Erase and program operations need the write protect (wp) pin to be
> de-asserted to take effect. Add the concept of destructive
> operation and pass the information to exec_op() so controllers know
> when they should de-assert this pin without having to decode
> the command opcode.
>
> Signed-off-by: Boris Brezillon <bbrezillon@...nel.org>
> Signed-off-by: David Regan <dregan@...adcom.com>
Reviewed-by: Florian Fainelli <florian.fainelli@...adcom.com>
--
Florian
Powered by blists - more mailing lists