public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] nand: add cmd_ctrl to platform_nand_chip
Date: Mon, 30 Apr 2007 11:35:14 +0200	[thread overview]
Message-ID: <1177925714.5791.192.camel@localhost.localdomain> (raw)
In-Reply-To: <4635B58D.9020709@gmail.com>

On Mon, 2007-04-30 at 13:23 +0400, Vitaly Wool wrote:
> Hello Thomas,
> 
> please find the patch that extends struct platform_nand_chip with 
> cmd_ctrl field.

Looks good. Can you please resend with a useful changelog ?

Thanks,

	tglx

>  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  9:33 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4635B58D.9020709@gmail.com>]

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=1177925714.5791.192.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vitalywool@gmail.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: link
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