From: David Brownell <david-b@pacbell.net>
To: Alessandro Rubini <rubini-list@gnudd.com>
Cc: linux-input@vger.kernel.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] ads7846: allocate separate cache lines for tx and rx data
Date: Wed, 15 Jul 2009 11:06:47 -0700 [thread overview]
Message-ID: <200907151106.47917.david-b@pacbell.net> (raw)
In-Reply-To: <20090715093313.GA2897@mail.gnudd.com>
On Wednesday 15 July 2009, Alessandro Rubini wrote:
> From: Alessandro Rubini <rubini@gnudd.com>
>
> Since the SPI master might use DMA, tx and rx buffers must live on
> different cache lines.
Not true. Full duplex tranfsers using a single buffer are
explicitly allowed.
> Here one cache line is used for all tx and
> another for all rx. This will work whether the SPI master maps/unmaps
> one buffer at a time or all together. The patch only fixes the analog
> inputs, as touch screen operation is not affected, although I didn't
> check why. I tested on at91sam9263, where buffers are all mapped
> initially and unmapped individually at irq time.
If that spi_master driver mis-handles this, it's a bug in that
driver. (And I hope you were using a version of the '9263 chip
which fixed its SPI bugs. Initial silicon had a SPI controller
which was essentially unusuable in a multitasking environment.)
> The issue was discussed with Russell King on linux-arm-kernel.
Gee, but not with the author of that driver or the maintainer of
the SPI framework. Who could have pointed out instantly where
the true bug resides.
>
> Signed-off-by: Alessandro Rubini <rubini@gnudd.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: David Brownell <dbrownell@users.sourceforge.net>
> ---
> drivers/input/touchscreen/ads7846.c | 53 +++++++++++++++++++++++++----------
> 1 files changed, 38 insertions(+), 15 deletions(-)
>
next prev parent reply other threads:[~2009-07-15 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 9:33 [PATCH] ads7846: allocate separate cache lines for tx and rx data Alessandro Rubini
2009-07-15 18:06 ` David Brownell [this message]
2009-07-15 19:33 ` Alessandro Rubini
2009-07-16 7:15 ` Russell King - ARM Linux
2009-07-16 7:22 ` Russell King - ARM Linux
2009-07-16 7:56 ` David Brownell
2009-07-16 7:28 ` David Brownell
2009-07-16 10:00 ` Marek Vasut
2009-07-16 15:35 ` David Brownell
2009-07-16 20:06 ` Russell King - ARM Linux
2009-07-16 7:51 ` David Brownell
2009-07-16 8:15 ` Alessandro Rubini
2009-07-16 8:35 ` 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=200907151106.47917.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rubini-list@gnudd.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;
as well as URLs for NNTP newsgroup(s).