All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Wool <vitalywool@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: [patch/resend] add cmd_ctrl field to platform_nand_chip
Date: Mon, 30 Apr 2007 20:17:38 +0400	[thread overview]
Message-ID: <463616A2.5010706@gmail.com> (raw)

This patch introduces cmd_ctrl field to the platform_nand_chip structure,
in order to enable supplying platform-specific ALE/CLE/nCE controlling
function.

 include/linux/mtd/nand.h |    4 ++++
 1 files changed, 4 insertions(+)

Signed-off-by: Vitaly Wool <vitalywool@gmail.com>

Index: linux-2.6/include/linux/mtd/nand.h
===================================================================
--- linux-2.6.orig/include/linux/mtd/nand.h
+++ linux-2.6/include/linux/mtd/nand.h
@@ -577,6 +577,8 @@ struct platform_nand_chip {
  * @hwcontrol:        platform specific hardware control structure
  * @dev_ready:        platform specific function to read ready/busy pin
  * @select_chip:    platform specific chip select function
+ * @cmd_ctrl:        platform specific function for controlling
+ *            ALE/CLE/nCE. Also used to write command and address
  * @priv:        private data to transport driver specific settings
  *
  * All fields are optional and depend on the hardware driver requirements
@@ -585,6 +587,8 @@ struct platform_nand_ctrl {
     void        (*hwcontrol)(struct mtd_info *mtd, int cmd);
     int        (*dev_ready)(struct mtd_info *mtd);
     void        (*select_chip)(struct mtd_info *mtd, int chip);
+    void        (*cmd_ctrl)(struct mtd_info *mtd, int dat,
+                    unsigned int ctrl);
     void        *priv;
 };
 

                 reply	other threads:[~2007-04-30 16:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=463616A2.5010706@gmail.com \
    --to=vitalywool@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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: link
Be 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.