All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: OF NDFC
Date: Thu, 6 Sep 2007 16:06:20 +0200	[thread overview]
Message-ID: <f6be8e61e378a9358eb60f2fb0042592@kernel.crashing.org> (raw)
In-Reply-To: <20070906084109.315544ea@zod.rchland.ibm.com>

>> AFAIK, NAND flash is autodetected by reading it's ID at runtime, so
>> there should be no need for flash bindings.
>
> Well, I'm not really sure.  CFI and JEDEC can both be probed as well,
> and we're working on a binding there.

JEDEC cannot be reliably probed.  CFI can be _almost_ probed,
you need to know the interleaving though, to handle some edge
cases.  Oh, and you need to know it _is_ CFI, of course.

> But if you think you can come up
> with a driver for NDFC that doesn't require some kind of device tree
> description of the devices it controls, then by all means go for it.

I don't know whether NAND can be reliably probed; most "standard"
NAND devices can be, but I don't know what standards are involved
here, if any.  We'll need some MTD people help here.

OTOH, it definitely is better to describe only the NAND controller
and not the devices, than to put nothing at all in the device tree.
We had this same situation with NOR flash before, already...


Segher

      reply	other threads:[~2007-09-06 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 18:17 OF NDFC Valentine Barshak
2007-09-05 21:00 ` Josh Boyer
2007-09-06 13:06   ` Segher Boessenkool
2007-09-06 13:17     ` Josh Boyer
2007-09-06 13:30       ` Valentine Barshak
2007-09-06 13:41         ` Josh Boyer
2007-09-06 14:06           ` Segher Boessenkool [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=f6be8e61e378a9358eb60f2fb0042592@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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.