From: "Luke Yang" <luke.adi@gmail.com>
To: linux-kernel@vger.kernel.org, dbrownell@users.sourceforge.net,
spi-devel-general@lists.sourceforge.net
Subject: [Patch] Add spi full duplex mode transfer support
Date: Wed, 30 Aug 2006 12:40:35 +0800 [thread overview]
Message-ID: <489ecd0c0608292140m483bba2fqa300b55c5f4acf26@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Hi all,
To enable full duplex mode spi transfer in Blackfin spi master
driver, I need an extra field in spi_transfer structure. Attached the
right format patch.
Signed-off-by: Luke Yang <luke.adi@gmail.com>
spi.h | 1 +
1 files changed, 1 insertion(+)
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index c8bb680..99816eb 100644
--- a/include/linux/spi/spi.h
+++ b/include/linux/spi/spi.h
@@ -331,6 +331,7 @@ struct spi_transfer {
dma_addr_t rx_dma;
unsigned cs_change:1;
+ unsigned is_duplex:1;
u8 bits_per_word;
u16 delay_usecs;
u32 speed_hz;
--
Best regards,
Luke Yang
luke.adi@gmail.com
[-- Attachment #2: spi_full_duplex.patch --]
[-- Type: text/x-patch, Size: 331 bytes --]
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index c8bb680..99816eb 100644
--- a/include/linux/spi/spi.h
+++ b/include/linux/spi/spi.h
@@ -331,6 +331,7 @@ struct spi_transfer {
dma_addr_t rx_dma;
unsigned cs_change:1;
+ unsigned is_duplex:1;
u8 bits_per_word;
u16 delay_usecs;
u32 speed_hz;
next reply other threads:[~2006-08-30 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 4:40 Luke Yang [this message]
2006-08-30 4:52 ` [spi-devel-general] " David Brownell
[not found] ` <2e2add590608300337h3e7e806bs69b63b24d73a104c@mail.gmail.com>
2006-08-30 15:35 ` David Brownell
2006-08-30 15:56 ` Stephen Street
2006-08-30 16:26 ` David Brownell
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=489ecd0c0608292140m483bba2fqa300b55c5f4acf26@mail.gmail.com \
--to=luke.adi@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®