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: Wed, 15 Jul 2009 02:09:31 +0400 [thread overview]
Message-ID: <20090714220931.GA11378@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <OF613F53BF.1FD77EDB-ONC12575F3.00753535-C12575F3.00753537@transmode.se>
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.
[...]
> >http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg34738.html
> >^^^ I'm dreaming about this framework. I.e. true addressing
> > for chip-selects. :-)
>
> This is probably needed to support most SPI users out there, but until
> such framework is in place I think the native methods need to stay, right?
I'm not the right person to ask. I can only express my opinions.
The maintainer make final decision.
But if you ask for my opinion, I don't think that they should stay
unless we'll see a user in the mainline.
> As is now, SPI has regressed w.r.t earlier releases.
Yes and no. Yes, it has "regressed" for out-of-tree code, and no,
I don't feel sorry about that. :-)
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: dbrownell@users.sourceforge.net, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: Ang: Re: [PATCH 0/2] Setting GPIOs simultaneously
Date: Wed, 15 Jul 2009 02:09:31 +0400 [thread overview]
Message-ID: <20090714220931.GA11378@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <OF613F53BF.1FD77EDB-ONC12575F3.00753535-C12575F3.00753537@transmode.se>
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.
[...]
> >http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg34738.html
> >^^^ I'm dreaming about this framework. I.e. true addressing
> > for chip-selects. :-)
>
> This is probably needed to support most SPI users out there, but until
> such framework is in place I think the native methods need to stay, right?
I'm not the right person to ask. I can only express my opinions.
The maintainer make final decision.
But if you ask for my opinion, I don't think that they should stay
unless we'll see a user in the mainline.
> As is now, SPI has regressed w.r.t earlier releases.
Yes and no. Yes, it has "regressed" for out-of-tree code, and no,
I don't feel sorry about that. :-)
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-07-14 22:09 UTC|newest]
Thread overview: 32+ 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 ` Anton Vorontsov
2009-07-13 15:19 ` [PATCH 1/2] gpiolib: Implement gpio_set_values_sync() Anton Vorontsov
2009-07-13 15:19 ` Anton Vorontsov
2009-07-13 15:19 ` [PATCH 2/2] powerpc/qe: Implement set_sync() callback for QE GPIOs Anton Vorontsov
2009-07-13 15:19 ` Anton Vorontsov
2009-07-13 16:01 ` [PATCH 0/2] Setting GPIOs simultaneously Joakim Tjernlund
2009-07-13 16:01 ` Joakim Tjernlund
2009-07-13 17:34 ` Anton Vorontsov
2009-07-13 17:34 ` Anton Vorontsov
2009-07-13 19:59 ` Joakim Tjernlund
2009-07-13 19:59 ` Joakim Tjernlund
2009-07-13 22:20 ` Anton Vorontsov
2009-07-13 22:20 ` Anton Vorontsov
2009-07-14 21:20 ` Ang: " Joakim Tjernlund
2009-07-14 21:20 ` Joakim Tjernlund
2009-07-14 22:09 ` Anton Vorontsov [this message]
2009-07-14 22:09 ` Anton Vorontsov
2009-08-04 13:38 ` Joakim Tjernlund
2009-08-04 13:38 ` Joakim Tjernlund
2009-08-04 14:22 ` Anton Vorontsov
2009-08-04 14:22 ` Anton Vorontsov
2009-08-04 14:59 ` Joakim Tjernlund
2009-08-04 14:59 ` Joakim Tjernlund
2009-08-04 15:33 ` Anton Vorontsov
2009-08-04 15:33 ` Anton Vorontsov
[not found] ` <OFF188389D.68E638A2-ONC12575F2.00568C5B-C12575F2.0057FC95@LocalDomain>
2009-07-13 17:17 ` Joakim Tjernlund
2009-07-13 17:17 ` Joakim Tjernlund
2009-11-05 14:49 ` Kumar Gala
2009-11-05 14:49 ` Kumar Gala
2009-11-05 14:58 ` Anton Vorontsov
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=20090714220931.GA11378@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 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.