From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linuxppc-dev@ozlabs.org, dbrownell@users.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Ang: Re: [PATCH 0/2] Setting GPIOs simultaneously
Date: Tue, 4 Aug 2009 18:22:50 +0400 [thread overview]
Message-ID: <20090804142250.GA17398@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <OF9A2BDEDE.DC0DE0D4-ONC1257608.004A7A59-C1257608.004AF3BF@transmode.se>
On Tue, Aug 04, 2009 at 03:38:40PM +0200, Joakim Tjernlund wrote:
> Anton Vorontsov <avorontsov@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>;
touchscreen@0 {
reg = <0>; /* using GPIO CS1 */
};
eeprom@1 {
reg = <1>; /* using GPIO CS2 */
};
};
};
localbus {
...
board_csm: chip-select-machine {
#address-cells = <1>;
#size-cells = <0>;
compatibe = "board-specific-csm";
light-sensor@0 {
reg = <0>; /* using board-specific "CS3" */
};
battery@1 {
reg = <1>; /* using board-specific "CS4" */
};
};
};
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-08-04 14:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 15:19 [PATCH 0/2] Setting GPIOs simultaneously Anton Vorontsov
2009-07-13 15:19 ` [PATCH 1/2] gpiolib: Implement gpio_set_values_sync() Anton Vorontsov
2009-07-13 15:19 ` [PATCH 2/2] powerpc/qe: Implement set_sync() callback for QE GPIOs Anton Vorontsov
2009-07-13 16:01 ` [PATCH 0/2] Setting GPIOs simultaneously Joakim Tjernlund
2009-07-13 17:34 ` Anton Vorontsov
2009-07-13 19:59 ` Joakim Tjernlund
2009-07-13 22:20 ` Anton Vorontsov
2009-07-14 21:20 ` Ang: " Joakim Tjernlund
2009-07-14 22:09 ` Anton Vorontsov
2009-08-04 13:38 ` Joakim Tjernlund
2009-08-04 14:22 ` Anton Vorontsov [this message]
2009-08-04 14:59 ` Joakim Tjernlund
2009-08-04 15:33 ` Anton Vorontsov
[not found] ` <OFF188389D.68E638A2-ONC12575F2.00568C5B-C12575F2.0057FC95@LocalDomain>
2009-07-13 17:17 ` Joakim Tjernlund
2009-11-05 14:49 ` Kumar Gala
2009-11-05 14:58 ` Anton Vorontsov
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=20090804142250.GA17398@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=dbrownell@users.sourceforge.net \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).