From: Rini van Zetten <rini@arvoo.nl>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: spi-devel-general@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH][POWERPC] mpc83xx : allow SPI without cs.
Date: Thu, 11 Jun 2009 17:11:50 +0200 [thread overview]
Message-ID: <4A311EB6.5060209@arvoo.nl> (raw)
In-Reply-To: <7071E2AF-65ED-41C2-AFE7-06E9336619CB@kernel.crashing.org>
excuse me for my ignorance, but which -mm tree do you mean and where can I find it.
Regards,
Rini
Kumar Gala schreef:
>
> On Jun 11, 2009, at 4:10 AM, Rini van Zetten wrote:
>
>> This patch adds the possibility to have a spi device without a cs.
>>
>> For example, the dts file should look something like this:
>>
>> spi-controller {
>> gpios = <&pio1 1 0 /* cs0 */
>> 0 /* cs1, no GPIO */
>> &pio2 2 0>; /* cs2 */
>>
>>
>>
>> Signed-off-by: Rini van Zetten <rini@arvoo.nl>
>> ---
>> drivers/spi/spi_mpc83xx.c | 44
>> +++++++++++++++++++++++---------------------
>> 1 files changed, 23 insertions(+), 21 deletions(-)
>
> This patch needs to be respun against the -mm tree as a lot of other spi
> patches are queued up there that will cause this patch to not merge
> correctly.
>
> - k
--
Rini van Zetten
Senior Software Engineer
-------------------------
ARVOO Engineering B.V.
Tasveld 13
3417 XS Montfoort
The Netherlands
E-mail : <mailto:rini@arvoo.com> Rini van Zetten
Web : www.arvoo.com
next prev parent reply other threads:[~2009-06-11 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 9:10 [PATCH][POWERPC] mpc83xx : allow SPI without cs Rini van Zetten
2009-06-11 13:29 ` Kumar Gala
2009-06-11 15:11 ` Rini van Zetten [this message]
2009-06-12 8:59 ` [PATCH -mm][POWERPC] mpc8xxx " Rini van Zetten
-- strict thread matches above, loose matches on Subject: below --
2009-05-13 7:50 [PATCH][POWERPC] mpc83xx " Rini van Zetten
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=4A311EB6.5060209@arvoo.nl \
--to=rini@arvoo.nl \
--cc=Linuxppc-dev@ozlabs.org \
--cc=akpm@linux-foundation.org \
--cc=galak@kernel.crashing.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).