From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd/mxc_nand: add support for multiple chips on V21 devices
Date: Thu, 31 Mar 2011 15:09:53 +0300 [thread overview]
Message-ID: <1301573393.2828.51.camel@localhost> (raw)
In-Reply-To: <2731521d2fd2224b7b28cc9ced044fc026d4fdb7.1300085993.git.baruch@tkos.co.il>
On Mon, 2011-03-14 at 09:01 +0200, Baruch Siach wrote:
> Do the following to add support for up to 4 chips on V21 devices (i.MX25 and
> i.MX35):
>
> * implement .select_chip for V21
> * adjust existing NFC_V1_V2_BUF_ADDR writes to take chip select into account
> * unlock all chip selects at preset_v1_v2()
> * scan up to 4 devices at .probe
>
> This has been tested on i.MX25 with two attached NAND chip (on one die).
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Pushed to l2-mtd-2.6.git, thank you.
--
Best Regards,
Artem Bityutskiy (????? ????????)
prev parent reply other threads:[~2011-03-31 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 7:01 [PATCH] mtd/mxc_nand: add support for multiple chips on V21 devices Baruch Siach
2011-03-17 5:09 ` Baruch Siach
2011-03-18 7:34 ` Sascha Hauer
2011-03-31 12:09 ` Artem Bityutskiy [this message]
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=1301573393.2828.51.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).