mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Paul Fertser <fercerpav@gmail.com>
To: barebox@lists.infradead.org
Subject: [RFC][PATCH 3/3] spi: indicate in the docs that per-transfer bpw setting is not supported
Date: Tue, 30 Aug 2011 09:39:05 +0400	[thread overview]
Message-ID: <a1a671b84ae652cef9c8d8fd04f8893e4d906645.1314683390.git.fercerpav@gmail.com> (raw)
In-Reply-To: <3c2cf8578f00f7200d39dc396856cb8a63e48d4d.1314683390.git.fercerpav@gmail.com>

Currently it's not implemented by any driver so add a note to the
documentation.

Signed-off-by: Paul Fertser <fercerpav@gmail.com>
---
 include/spi/spi.h |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/include/spi/spi.h b/include/spi/spi.h
index 948e050..9d01d06 100644
--- a/include/spi/spi.h
+++ b/include/spi/spi.h
@@ -37,7 +37,8 @@ struct spi_board_info {
  *	powers of two bytes (e.g. 20 bit samples use 32 bits).
  *	This may be changed by the device's driver, or left at the
  *	default (0) indicating protocol words are eight bit bytes.
- *	The spi_transfer.bits_per_word can override this for each transfer.
+ *	The spi_transfer.bits_per_word can override this for each transfer
+ *	(FIXME: not currently implemented).
  * @irq: Negative, or the number passed to request_irq() to receive
  *	interrupts from this device.
  * @controller_state: Controller's runtime state
-- 
1.5.2.2


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2011-08-30  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 12:25 [RFC][PATCH 1/3] spi: let master a chance to setup device before registering it Paul Fertser
2011-08-29 12:39 ` [RFC][PATCH 2/3] spi: enfore default bits_per_word value Paul Fertser
2011-08-30  5:39 ` Paul Fertser [this message]

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=a1a671b84ae652cef9c8d8fd04f8893e4d906645.1314683390.git.fercerpav@gmail.com \
    --to=fercerpav@gmail.com \
    --cc=barebox@lists.infradead.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