From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,URIBL_DBL_ABUSE_MALW,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1C7A9C2D0DB for ; Mon, 27 Jan 2020 15:48:20 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id E545922527 for ; Mon, 27 Jan 2020 15:48:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="ZlqLEgMu" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E545922527 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bootlin.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=7W3hpee+652pg4/bFoa/HRS6wHY1AxS0KPGXMHjNPWI=; b=ZlqLEgMu03JIej +eC8bVrTptXIJkTQiHSWjeoYNHV7N8r10+qR4R5d0qylJ0JYWUV9kl+hYWmR70L4O0/Qgi138rwQc V+558mUhyrt3B5AcQZhB/+osUCoH6VYThoUxodQKnuW0ymDhdNwa3HaJ08NeBdrqf708hj/eXrsjX 8/1BM3Pe2K98XYKvosTDogtgsHE6FfEtQDMuvcEOBnTtBSKt4Rt0MkBhRFYmJjvLiUwulgsi5br5E otaRh5qvM0qBD0OCbfTBdZD9pntkKHrELl5/k0T3q+nQrOgoZY20OL5d0rLeRoWAPdGjSgpbQzDsA t60Fzqa7C2atBw4qmAZQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1iw6cS-0008C1-2v; Mon, 27 Jan 2020 15:48:08 +0000 Received: from relay9-d.mail.gandi.net ([217.70.183.199]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iw6cO-0008BP-TC for linux-mtd@lists.infradead.org; Mon, 27 Jan 2020 15:48:06 +0000 X-Originating-IP: 90.76.211.102 Received: from xps13 (lfbn-tou-1-1151-102.w90-76.abo.wanadoo.fr [90.76.211.102]) (Authenticated sender: miquel.raynal@bootlin.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 3CCC8FF803; Mon, 27 Jan 2020 15:47:55 +0000 (UTC) Date: Mon, 27 Jan 2020 16:47:55 +0100 From: Miquel Raynal To: Boris Brezillon Subject: Re: How to handle write-protect pin of NAND device ? Message-ID: <20200127164755.29183962@xps13> In-Reply-To: <20200127164554.34a21177@collabora.com> References: <20200127153559.60a83e76@xps13> <20200127164554.34a21177@collabora.com> Organization: Bootlin X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200127_074805_286476_8165BD47 X-CRM114-Status: GOOD ( 26.47 ) X-BeenThere: linux-mtd@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Masahiro Yamada , linux-mtd , Linux Kernel Mailing List , Boris Brezillon Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-mtd" Errors-To: linux-mtd-bounces+linux-mtd=archiver.kernel.org@lists.infradead.org Hi Hello, Boris Brezillon wrote on Mon, 27 Jan 2020 16:45:54 +0100: > On Mon, 27 Jan 2020 15:35:59 +0100 > Miquel Raynal wrote: > > > Hi Masahiro, > > > > Masahiro Yamada wrote on Mon, 27 Jan 2020 > > 21:55:25 +0900: > > > > > Hi. > > > > > > I have a question about the > > > WP_n pin of a NAND chip. > > > > > > > > > As far as I see, the NAND framework does not > > > handle it. > > > > There is a nand_check_wp() which reads the status of the pin before > > erasing/writing. > > > > > > > > Instead, it is handled in a driver level. > > > I see some DT-bindings that handle the WP_n pin. > > > > > > $ git grep wp -- Documentation/devicetree/bindings/mtd/ > > > Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt:- > > > brcm,nand-has-wp : Some versions of this IP include a > > > write-protect > > > > Just checked: brcmnand de-assert WP when writing/erasing and asserts it > > otherwise. IMHO this switching is useless. > > > > > Documentation/devicetree/bindings/mtd/ingenic,jz4780-nand.txt:- > > > wp-gpios: GPIO specifier for the write protect pin. > > > Documentation/devicetree/bindings/mtd/ingenic,jz4780-nand.txt: > > > wp-gpios = <&gpf 22 GPIO_ACTIVE_LOW>; > > > Documentation/devicetree/bindings/mtd/nvidia-tegra20-nand.txt:- > > > wp-gpios: GPIO specifier for the write protect pin. > > > Documentation/devicetree/bindings/mtd/nvidia-tegra20-nand.txt: > > > wp-gpios = <&gpio TEGRA_GPIO(S, 0) GPIO_ACTIVE_LOW>; > > > > In both cases, the WP GPIO is unused in the code, just de-asserted at > > boot time like what you do in the patch below. > > > > > > > > > > > > > > I wrote a patch to avoid read-only issue in some cases: > > > http://patchwork.ozlabs.org/patch/1229749/ > > > > > > Generally speaking, we expect NAND devices > > > are writable in Linux. So, I think my patch is OK. > > > > I think the patch is fine. > > > > > > > > > > > However, I asked this myself: > > > Is there a useful case to assert the write protect > > > pin in order to make the NAND chip really read-only? > > > For example, the system recovery image is stored in > > > a read-only device, and the write-protect pin is > > > kept asserted to assure nobody accidentally corrupts it. > > > > It is very likely that the same device is used for RO and RW storage so > > in most cases this is not possible. We already have squashfs which is > > actually read-only at filesystem level, I'm not sure it is needed to > > enforce this at a lower level... Anyway if there is actually a pin for > > that, one might want to handle the pin directly as a GPIO, what do you > > think? > > FWIW, I've always considered the WP pin as a way to protect against > spurious destructive command emission, which is most likely to happen > during transition phases (bootloader -> linux, linux -> kexeced-linux, > platform reset, ..., or any other transition where the pin state might > be undefined at some point). This being said, if you're worried about > other sources of spurious cmds (say your bus is shared between > different kind of memory devices, and the CS pin is unreliable), you > might want to leave the NAND in a write-protected state de-asserting WP > only when explicitly issuing a destructive command (program page, erase > block). Ok so with this in mind, only the brcmnand driver does a useful use of the WP output. ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/