From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
spi-devel-general@lists.sourceforge.net,
lkml <linux-kernel@vger.kernel.org>,
Vernon Sauder <vernoninhand@gmail.com>
Subject: Re: [patch 2.6.28-rc9] spi: spi_write_then_read() regression fix
Date: Sun, 21 Dec 2008 15:46:10 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0812211545520.24883@localhost.localdomain> (raw)
In-Reply-To: <200812202332.36281.david-b@pacbell.net>
On Sat, 20 Dec 2008, David Brownell wrote:
>
> All SPI transfers are full duplex, and are packaged as half duplex
> by either discarding the data that's read ("write only"), or else
> by writing zeroes ("read only"). That patch wasn't ensuring that
> zeroes were getting written out during the "half duplex read" part
> of the transaction; instead, old RX bits were getting sent.
Hmm. In addition, isn't this broken (in that same function):
memcpy(local_buf, txbuf, n_tx);
x.tx_buf = local_buf;
x.rx_buf = local_buf;
/* do the i/o */
status = spi_sync(spi, &message);
if (status == 0)
memcpy(rxbuf, x.rx_buf + n_tx, n_rx);
shouldn't that 'rx_buf' setup be
x.rx_buf = local_buf + n_tx;
since the whole point was that we allocated a buffer that can hold _both_
the rx and tx parts? Especially as that final copy into the resulting
"rxbuf" thing uses that "+ n_tx" addition?
Linus
next prev parent reply other threads:[~2008-12-21 23:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 7:32 David Brownell
2008-12-21 23:46 ` Linus Torvalds [this message]
2008-12-22 0:48 ` David Brownell
2008-12-23 1:53 ` Ingo Oeser
2008-12-23 18:37 ` David Brownell
2008-12-23 18:45 ` Linus Torvalds
2008-12-23 20:54 ` 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=alpine.LFD.2.00.0812211545520.24883@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=vernoninhand@gmail.com \
/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®