Thread (7 messages) flat view 7 messages, 4 authors, 2007-09-06
  • OF NDFC · Valentine Barshak <hidden> · 2007-09-05
  • Re: OF NDFC · Josh Boyer <hidden> · 2007-09-05
  • Re: OF NDFC · Segher Boessenkool <hidden> · 2007-09-06
  • Re: OF NDFC · Josh Boyer <hidden> · 2007-09-06
  • Re: OF NDFC · Valentine Barshak <hidden> · 2007-09-06
  • Re: OF NDFC · Josh Boyer <hidden> · 2007-09-06
  • Re: OF NDFC · Segher Boessenkool <hidden> · 2007-09-06

Re: OF NDFC

From: Segher Boessenkool <hidden>
Date: 2007-09-06 14:12:37

quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help