Hi Roger,
On 21 May 02:20 PM, Roger Quadros wrote:
>
> For DT boot:
> - The GPMC controller node should have a chip select (CS) node for each used
> chip select. The CS node must have a child device node for each device
> attached to that chip select. Properties for that child are GPMC agnostic.
>
> i.e.
> gpmc {
> cs0 {
> nand0 {
> }
> };
>
> cs1 {
> nor0 {
> }
> }
> ...
> };
>
While I agree that the GPMC driver is a bit messy, I'm not sure it's possible
to go through such a complete devicetree binding re-design (breaking backwards
compatibility) now that the binding is already in production.
AFAIK, TI's SDK 7.0 is released, with a v3.8.x kernel which uses this GPMC
binding. And then you have the ISEE board too, using this binding.
Also, what's the problem with the current devicetree binding (not that I'm fan
of it)?
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
