On Tue, Aug 04, 2009 at 03:38:40PM +0200, Joakim Tjernlund wrote: > Anton Vorontsov <avoront...@ru.mvista.com> wrote on 15/07/2009 00:09:31: > > > > On Tue, Jul 14, 2009 at 11:20:13PM +0200, Joakim Tjernlund wrote: > > [...] > > > >But any users of the legacy bindings should be in-tree. > > > > > > ehh, it was working until you made it OF only. Why do call the native > > > way legacy? It is the method all non OF arch uses. > > > > It's legacy because there are no in-tree users anymore. Nowadays > > we're trying to pass all needed information via OF, and we're > > trying to avoid ugly platform-dependant hacks. Your SPI scheme > > can be easily described via OF, but sure, it's hard to implement > > it with the current SPI/OF subsystem. > > Sorry for the long delay, I have been on vaction and been busy with other > stuff. > > Tell me, how does this new OF SPI device scheme work out if you want > to use the bitbanged SPI driver?
spi-controller { ... compatible = "generic-bitbang-spi"; gpios = <GPIO_CLK GPIO_MOSI GPIO_MISO>; spi,chip-select-machines = <&gpio_csm &board_csm>; gpio_csm: chip-select-machine { #address-cells = <1>; #size-cells = <0>; compatible = "generic-gpio-csm"; gpios = <GPIO_CS1 GPIO_CS2>; touchscr...@0 { reg = <0>; /* using GPIO CS1 */ }; eep...@1 { reg = <1>; /* using GPIO CS2 */ }; }; }; localbus { ... board_csm: chip-select-machine { #address-cells = <1>; #size-cells = <0>; compatibe = "board-specific-csm"; light-sen...@0 { reg = <0>; /* using board-specific "CS3" */ }; batt...@1 { reg = <1>; /* using board-specific "CS4" */ }; }; }; -- Anton Vorontsov email: cbouatmai...@gmail.com irc://irc.freenode.net/bd2 _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev