public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: dregan <dregan@broadcom•com>
To: dregan <dregan@broadcom•com>,
	Miquel Raynal <miquel.raynal@bootlin•com>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	Boris Brezillon <boris.brezillon@collabora•com>,
	Boris Brezillon <bbrezillon@kernel•org>,
	Richard Weinberger <richard@nod•at>,
	Vignesh Raghavendra <vigneshr@ti•com>,
	linux-mtd@lists•infradead.org, linux-kernel@vger•kernel.org,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: [PATCH v2 1/1] mtd: rawnand: Add deassert_wp comment
Date: Fri,  1 Dec 2023 13:24:46 -0800	[thread overview]
Message-ID: <20231201212446.189491-1-dregan@broadcom.com> (raw)

From: David Regan <dregan@broadcom•com>

Add deassert_wp description comment

Signed-off-by: David Regan <dregan@broadcom•com>
---
Changes in v2: removed Boris Brezillon as author and SOB
---
 include/linux/mtd/rawnand.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/mtd/rawnand.h b/include/linux/mtd/rawnand.h
index fcad94aa0515..3049b05d8a20 100644
--- a/include/linux/mtd/rawnand.h
+++ b/include/linux/mtd/rawnand.h
@@ -1001,6 +1001,8 @@ struct nand_op_parser {
 /**
  * struct nand_operation - NAND operation descriptor
  * @cs: the CS line to select for this NAND operation
+ * @deassert_wp: set to true when the operation requires the WP pin to be
+ *		 de-asserted (ERASE, PROG, ...)
  * @instrs: array of instructions to execute
  * @ninstrs: length of the @instrs array
  *
-- 
2.37.3


             reply	other threads:[~2023-12-01 21:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 21:24 dregan [this message]
2023-12-04  7:39 ` [PATCH v2 1/1] mtd: rawnand: Add deassert_wp comment Miquel Raynal
2023-12-04 10:52 ` 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=20231201212446.189491-1-dregan@broadcom.com \
    --to=dregan@broadcom$(echo .)com \
    --cc=bbrezillon@kernel$(echo .)org \
    --cc=boris.brezillon@collabora$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mtd@lists$(echo .)infradead.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=miquel.raynal@bootlin$(echo .)com \
    --cc=richard@nod$(echo .)at \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=vigneshr@ti$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox