Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Beisert <jbeisert@eurodsn.de>
To: linux-mtd@lists.infradead.org
Subject: Additional arguments to <struct nand_chip.hwcontrol> and .dev_ready functions
Date: Fri, 11 Jul 2003 16:49:26 +0200	[thread overview]
Message-ID: <200307111649.26591.jbeisert@eurodsn.de> (raw)

Hello all,

I have written a driver for my NAND flash chip application using the mtd 
framework. It works fine when there is only one chip in one memory area 
present.
But if there are more than one NAND chip, you need more than one function for
    struct nand_chip.hwcontrol,
because this function don't know which chips control lines it should change.
Same with
    struct nand_chip.dev_ready.
For which chip it should wait?

Is it possible to add arguments, like a pointer to the struct nand_chip, to 
these functions? Then one of this function could handle more than one chip.

--JB

             reply	other threads:[~2003-07-11 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 14:49 Juergen Beisert [this message]
2003-07-11 15:13 ` Additional arguments to <struct nand_chip.hwcontrol> and .dev_ready functions David Woodhouse
2003-07-11 15:47   ` Juergen Beisert

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=200307111649.26591.jbeisert@eurodsn.de \
    --to=jbeisert@eurodsn.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox