public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] nand onfi 8bit/16bit bus support
Date: Mon, 06 May 2013 18:53:52 +0200	[thread overview]
Message-ID: <5187E020.5090103@monstr.eu> (raw)

Hi guys,

Zynq supports 8 and 16bit ONFI nand flashes.
We can count number of connected pins and from that
we know if 8bit or 16bit nand flash is used.

I have looked at the code and contains ONFI detection
with correct detection of bus width + checking later.
Why also not setup proper chip->options for NAND_BUSWIDTH_16?

Not sure how others but if driver expect just ONFI devices
and support 8 and 16bit options why not just to setup
chip options based on information from ONFI or
not check that (busw != (chip->options & NAND_BUSWIDTH_16))
for onfi case.

Just wanted to get input from you before I will try to
create patch to support this.
I just want to be sure that I am not doing something
what it is wrong for other platforms.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130506/dc2e5acc/attachment.pgp>

             reply	other threads:[~2013-05-06 16:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 16:53 Michal Simek [this message]
2013-05-09 21:37 ` [U-Boot] nand onfi 8bit/16bit bus support Scott Wood
2013-05-10  5:57   ` Michal Simek
2013-06-19 13:40   ` Michal Simek
2013-06-19 17:17     ` Scott Wood
2013-06-20  5:32       ` Michal Simek

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=5187E020.5090103@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=u-boot@lists.denx.de \
    /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